OpenSource/agent-skills
1
0 Fork 0
mirror of https://github.com/addyosmani/agent-skills.git synced 2026-10-26 15:05:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge #553: clarify setup for existing projects

Browse Source 
docs: clarify setup for existing projects
This commit is contained in:
Addy Osmani authored and GitHub committed 2026-09-11 20:14:58 -07:00
2 parents fd00a70f8a 4fd76c6f00
commit be4e44a9fb
1 file changed
+12
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started.md
+12
View File
@@ -46,6 +46,18 @@ If your agent does not route skills natively, start with the `using-agent-skills
If your host already discovers and activates skills from their descriptions, do not also paste `using-agent-skills` into an always-on system prompt or rules file. That creates two routers for the same task. Install the individual skills and let the host activate them on demand instead. If your host already discovers and activates skills from their descriptions, do not also paste `using-agent-skills` into an always-on system prompt or rules file. That creates two routers for the same task. Install the individual skills and let the host activate them on demand instead.
### Existing projects need no migration
Install the pack from the existing project's root using the normal setup path
for your agent, then keep working in that project. Skills activate for matching
tasks; they do not require a new repository layout or a one-time conversion of
existing code.
Do not copy this repository's root `AGENTS.md` or `CLAUDE.md` into the project.
Those files configure contributors to agent-skills itself. Add only the skills
and any project-specific instructions your agent normally reads. For a gradual
rollout in an established codebase, follow the [Adoption Guide](adoption-guide.md).
## Recommended Setup ## Recommended Setup
Rolling out to a real project? The **[Adoption Guide](adoption-guide.md)** covers two end-to-end paths: the full lifecycle from day one for a greenfield project, and an incremental, verification-first rollout for an established codebase. The setup below is the quick version. Rolling out to a real project? The **[Adoption Guide](adoption-guide.md)** covers two end-to-end paths: the full lifecycle from day one for a greenfield project, and an incremental, verification-first rollout for an established codebase. The setup below is the quick version.