intelligence-add-skilllisted

# Add Skill ## Steps 1. **Determine domain prefix** (the scope is required): - **Reuse the existing domain when one fits**: list `<content-dir>/skills/` and `<content-dir>/agents/`. If a domain prefix is already established for the target area (`backend-`, `frontend-`, `devops-`), use it. Introduce a new domain only when the scope is materially different from all existing ones. - **When no existing domain fits**, derive from repo structure: - Single / root project → use the project codename from `<manifest>` → `project.name` - Backend service / API component → `backend-` - Frontend / web / UI component → `frontend-` - Infrastructure, IaC, CI/CD, deployment → `devops-` - Shared library / common / cross-cutting code → `core-` - Test suites (e2e, integration) → `tests-` - Tool-internal (intelligence-sync itself) → `intelligence-` (only inside the intelligence-sync repo — downstream projects must not use this prefix) - If the repo is a monorepo with named components (e.g., `apps/billing`, `services/auth`), prefer the component name as the domain (`billing-`, `auth-`). - **Every skill needs a domain prefix.** If the scope is unclear, ask the user before proceeding. 2. **Determine naming**: Build full name as `<domain>-<verb>-<noun>` using convention: - `add-` — adds one new member to a set that already exists (a field on an existing type, a record among records) - `create-` — brings into existence the container nothing hosted