From 4fd76c6f00a786889213902f1f5b19badb27434b Mon Sep 17 00:00:00 2001 From: vam Date: Sat, 5 Sep 2026 11:39:33 +0800 Subject: [PATCH] docs: clarify setup for existing projects --- docs/getting-started.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/getting-started.md b/docs/getting-started.md index 8572898a..c8bc49dc 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -39,6 +39,18 @@ Copy the relevant `SKILL.md` content into your agent's system prompt, rules file Start with the `using-agent-skills` skill loaded. It contains a flowchart that maps task types to the appropriate skill. +### 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 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.