# skills/

One subdirectory per skill, each containing a `SKILL.md` plus
any skill-local resources.

The skeleton commit ships this directory empty. The actual
skill bodies are migrated from AILang's in-tree
`~/dev/ailang/skills/` and generalised against the profile
schema (`../docs/profile-schema.md`) in **iteration 1**.

Expected layout after migration:

```
skills/
├── brainstorm/
│   └── SKILL.md
├── planner/
│   └── SKILL.md
├── implement/
│   └── SKILL.md
├── audit/
│   └── SKILL.md
├── debug/
│   └── SKILL.md
├── fieldtest/
│   └── SKILL.md
└── docwriter/
    └── SKILL.md
```

Migration checklist per skill:

1. Strip project-specific paths (`docs/specs`, `docs/plans`,
   `design/INDEX.md`, `crates/`, `bench/`).
2. Strip project-specific commands (`cargo build`,
   `bench/check.py`).
3. Replace literals with profile-slot references in prose.
4. Strip project vocabulary (`AILang`, `Form A`, `.ail.json`,
   `Boss`); use the profile's vocabulary slots.
5. Strip project-specific contracts (honesty-rule,
   feature-acceptance). These belong in the project's own
   `CLAUDE.md`, not the plugin.
6. Verify the body still reads coherently for a generic
   project — would it make sense in a Python web service?
   A TypeScript library?