メニュー
Use when creating new skills, restructuring existing skills, or improving skill documentation. Generates SKILL.md + references/ structure with proper patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Systematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation. Modes: --auto (default), --manual, --skip-elicit
Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD. Use when: an expert agent needs to self-review and self-correct code after the Execute phase, before sniper validation.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing. Do NOT use for: lint/type/code-quality validation (use code-quality / sniper AFTER functional verification passes).
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use when committing changes, saving work, staging and committing, or choosing a conventional commit message.
Use when committing, branching, opening PRs, or deciding merge strategy. Covers GitHub Flow (default), trunk-based, branch naming conventions, squash vs rebase, branch lifecycle, and protected branch enforcement.
Universal post-commit actions. CHANGELOG update for all repos (git tag is created POST-MERGE, not here — see `commit` command Step 8). Plugin version bumping for marketplace repos. Triggered after any code commit (except wip/amend/undo).
| name | skill-creator |
| description | Use when creating new skills, restructuring existing skills, or improving skill documentation. Generates SKILL.md + references/ structure with proper patterns. |
Before ANY skill creation, spawn 3 subagents in parallel (one dispatch, spawn_agent / MultiAgentV2):
After creation, run sniper for validation.
| Action | When to Use |
|---|---|
| New Skill | Library/framework not yet documented |
| Restructure | Existing skill doesn't follow pattern |
| Improve | Missing references or outdated content |
| Adapt | Copy from similar skill (Next.js → React) |
skills/<skill-name>/
├── SKILL.md # Entry point (guides agent)
└── references/ # All documentation
├── installation.md # Setup, configuration (conceptual)
├── patterns.md # Core patterns (conceptual)
├── ... # Other references
└── templates/ # Complete code examples
├── basic-setup.md # Full project setup
└── feature-example.md # Feature implementation
→ See architecture.md for details
| Topic | Reference | When to Consult |
|---|---|---|
| Workflow | workflow.md | Creating/improving skills |
| Architecture | architecture.md | Understanding skill structure |
| Content Rules | content-rules.md | Writing references/templates |
| Registration | registration.md | Making the skill available |
| Adaptation | adaptation.md | Converting between frameworks |
| Template | When to Use |
|---|---|
| SKILL-template.md | Creating new SKILL.md |
| reference-template.md | Creating reference files |
| template-template.md | Creating code templates |
# 1. Research documentation
→ research-expert + context7/exa
# 2. Create structure
mkdir -p plugins/<plugin>/skills/<name>/references/templates
# 3. Create files
→ SKILL.md (from template, frontmatter = name + description)
→ references/*.md (conceptual)
→ references/templates/*.md (code)
# 4. Register the plugin in the marketplace manifest
# 5. Validate
→ sniper
# 1. Analyze
→ explore-codebase
# 2. Research updates
→ research-expert (latest docs)
# 3. Add missing files
→ references + templates
# 4. Validate
→ sniper