From 908691bf0bf67183590f11c41a1fdcc8de5f0f00 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Wed, 18 Feb 2026 02:22:35 +0100 Subject: [PATCH] chore(skills): add domain-action naming convention to create-skill Documents the {domain}-{action} naming pattern for new skills so future skills follow the convention established in the kit. Co-Authored-By: Claude Opus 4.6 --- .claude/skills/create-skill/SKILL.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.claude/skills/create-skill/SKILL.md b/.claude/skills/create-skill/SKILL.md index ac94cbc14..6341428af 100644 --- a/.claude/skills/create-skill/SKILL.md +++ b/.claude/skills/create-skill/SKILL.md @@ -178,7 +178,11 @@ For design patterns, consult: **Writing guidelines:** Always use imperative/infinitive form. **Frontmatter:** -- `name`: The skill name +- `name`: The skill name — use **domain-action** naming: `{domain}-{action}`. + The domain is the system/area the skill operates on, the action is what it does. + Examples: `pr-review`, `sprint-plan`, `docs-search`, `git-commit`, `debt-scan`. + Multi-action wrappers (like `ticket`) can use the domain name alone. + The directory name must match the `name` field. - `description`: Primary triggering mechanism. Include what the skill does AND specific triggers/contexts. All "when to use" info goes here (not in body).