Sample article — replace this content with the final version when it is ready.
Global is convenient until it is noisy
A global skill set is useful for habits that travel with you. But a project often has its own conventions, architecture, and quality bar. Loading every possible skill everywhere makes it harder to tell which instructions are relevant now.
Project-scoped skills solve that by traveling with the repository. A new contributor, a new machine, or a new agent can start from the same baseline.
A useful split
Keep a skill global when it describes how you generally work. Keep it in the project when it describes how this project works.
| Scope | Best for | Example |
|---|---|---|
| Global | Personal defaults | Your preferred review style |
| Project | Shared conventions | The repository’s UI patterns |
The repository becomes part of the memory
The most valuable project documentation is the documentation that is close enough to be updated with the code. Project-scoped skills make that relationship explicit.