Conventions for creating and organizing skills in this project. Use when creating, writing, updating, modifying, or changing a skill; renaming skills; or reviewing the skill directory structure. Prefer this skill over create-skill when the context is this project's skills.
Guidelines for creating, naming, and organizing skills in .cursor/skills/.
Trigger this skill when:
See .cursor/skills/README.md for the full naming guide, including the
three-layer naming system (prefix, area, specific), the object-action
pattern, and the complete skill catalog.
The key points for creating a new skill:
root-, act-, project-, meta-) classifies when the skill runs.
These rarely change.dev, repo, security) groups skills by domain. This
layer is optional -- only add it when there are enough skills that the
grouping helps.Skills are grouped by prefix into folders. Each skill lives in its own directory:
.cursor/skills/
act/ # act- prefix: reactive (dev, repo, etc.)
dev/
dev--scraper-write/
repo-pr-create/
...
role/ # role- prefix: agent personas (pm, architect, worker, etc.)
pm/
architect/
worker/
...
project/ # project- prefix: set-and-forget
setup/
setup-monorepo/
polish/
...
meta/ # meta- prefix: self-referential
skill-create/ # This skill (conventions)
agent-create/
...
root/ # root- prefix: root-repo management
project-setup/
...
SKILL.md -- the main skill file. This is what Cursor reads to understand the skill..md files -- detailed references, templates, or guides that SKILL.md links to. Keep them in the same directory.Every SKILL.md follows this structure:
---