Skip to main content

Organization Skills

Organization skills describe how your company wants software to be designed, built, tested, reviewed, and maintained. These are the most valuable skills because they can be reused across many products and teams.

In Copilot-assisted development, these skills become the shared rules that keep generated code consistent across teams instead of depending on individual prompts.

Example files:

engineering-skills/react/component-patterns.md
engineering-skills/architecture/domain-driven-frontend.md
engineering-skills/quality/accessibility.md
engineering-skills/workflows/pull-request-review.md

Short content:

# engineering-skills/react/component-patterns.md

Build components as small, typed React functions.
Keep data loading outside presentational components.
Add tests for visible behavior, not implementation details.

Store organization skills in a dedicated repository. Treat that repository like source code: version it, review changes, and keep examples close to the rules they explain.

Example files:

engineering-skills/
├── architecture/
│   ├── atomic-bomb.md
│   └── domain-modeling.md
├── react/
│   ├── atom.md
│   ├── molecule.md
│   └── page.md
├── quality/
│   ├── testing.md
│   └── accessibility.md
└── workflows/
    ├── feature-generation.md
    └── skill-extraction.md

Short content:

# engineering-skills/architecture/domain-modeling.md

Start from domain language before designing UI state.
Name models after business concepts.
Keep API DTOs separate from domain objects.

This repository becomes organizational memory. It is where teams capture decisions that should outlive a single application, sprint, or developer preference.

This makes Copilot more predictable because the same architectural and quality rules are available before every generated implementation.

Example files:

engineering-skills/SKILLS.md
engineering-skills/examples/customer-card/
engineering-skills/guidelines/naming.md

Short content:

# engineering-skills/guidelines/naming.md

Use business names for features and domain objects.
Use technical names only for infrastructure code.
Avoid abbreviations unless they are standard in the domain.

Mini exercise​

Apply Organization Skills to a feature or workflow you know. In ten minutes:

  1. Describe the current approach in one sentence.
  2. Identify one ambiguity, coupling risk, or missing constraint.
  3. Write one concrete rule or artifact that would improve predictability.
  4. Define how a reviewer or automated check could validate the improvement.

Compare your result with a teammate and revise the rule if two people could interpret it differently.

Example​

For Organization Skills, consider an accessibility-testing skill:

  • Current approach: The same guidance exists in user prompts, repository notes, and local agent configuration.
  • Risk: Teams cannot tell which version is authoritative.
  • Concrete rule: Store reusable accessibility policy at organization level, project exceptions in the repository, and runtime invocation details with the agent.
  • Validation: Trace one generated component to the exact policy, project rule, and runtime instruction it used.