32 lines
2.9 KiB
Markdown
32 lines
2.9 KiB
Markdown
# Skills
|
|
|
|
Skills are reusable workflows. Rules are persistent constraints and agents are specialized roles. Each skill has a readable `SKILL.md` with YAML frontmatter; detailed guidance may live in that file or its `references/` directory.
|
|
|
|
The current structure is organized by purpose:
|
|
|
|
- `planning/`: impact analysis and work-item definition
|
|
- `research/`: technical and repository research, plus `semantic-search`, which is installed only while semantic retrieval is enabled
|
|
- `reviews/`: security, performance, WPF, UI/UX, business, API, and EF Core reviews
|
|
- `implementation/`: SQL, unit-test, and integration-test writing
|
|
- `verification/`: facts and work-item verification
|
|
- `git/`: pull request reviews
|
|
- `content-strategy/`, `copy-editing/`, `copywriting/`: planning, editing, and writing text
|
|
- `image/`, `site-architecture/`: visuals and website structure
|
|
- `marketing-psychology/`, `offers/`, `product-marketing/`, `cro/`: audience understanding, value framing, and conversion
|
|
|
|
General planning, debugging, code review, and completion verification workflows come from Superpowers, so the catalog does not duplicate their triggers. The remaining skills cover focused domains Superpowers does not.
|
|
|
|
Each skill defines a focused workflow with the investigation, decision points, and output expected for that task. Keep guidance specific to the skill; shared repository constraints belong in the rules.
|
|
|
|
The single catalog in `shared/skills/` includes development skills and focused skills for writing, images, content and site structure, positioning, psychology, and conversion. Builds include every retained skill for both clients. Updating a managed installation backs up and removes unchanged setup-owned skills deleted from the catalog; local changes are backed up and retained.
|
|
|
|
Claude discovers only `skills/<name>/SKILL.md`, so its generated package flattens the categorized catalog to one directory per skill name, together with the skill's `references/`; the build fails on duplicate names or a `name` that differs from its directory. Claude's package additionally has a `rules-*` skill for each focused rule file or directory in
|
|
`shared/rules/`. The rule-to-skill loading conditions live in `shared/global-instructions.md`, so full rule text loads
|
|
only when Claude invokes a matching skill instead of sitting permanently in context. Codex reads the matching rule
|
|
files directly. Both clients embed the general rules in their global instructions.
|
|
Language, framework, library, and security rules use directory indexes plus focused topic files. Their generated Claude skills expose each focused rule separately; the index skills also include the references for contextual lookup. See [Configuration](configuration.md).
|
|
|
|
Skills guide a task when needed; their availability does not require a full review, build, or test suite after every
|
|
change. The shared Verification rules govern proportional checking, including when generic skill workflows call
|
|
for more work than the change needs.
|