← ClaudeAtlas

prompt-creatorlisted

Create prompts that pass prompt-review's five gates by construction — intent capture, slash-command naming, single-workflow scope, draft as numbered steps, dogfood self-review. Use when authoring a new prompt, refactoring an existing one, or promoting a Mall prompt into the heir's brain.
fabioc-aloha/Alex_ACT_Edition · ★ 0 · AI & Automation · score 75
Install: claude install-skill fabioc-aloha/Alex_ACT_Edition
# Prompt Creator Author prompts that pass [`prompt-review`](../prompt-review/SKILL.md)'s five gates by construction. The gates are the quality bar; invert them, and you build to standard the first time. Mirrors [`skill-creator`](../skill-creator/SKILL.md)'s seven-phase structure with prompt-specific guidance. If a phase here disagrees with skill-creator on the shared scaffold, skill-creator wins; this file owns only the per-type guidance. ## When to Use - Authoring a new prompt in `.github/prompts/` - Refactoring an existing prompt (rename, scope tighten, step revision) - Promoting a Mall prompt into your heir's brain ## When **not** to use - Authoring a skill (the procedure body) → use [skill-creator](../skill-creator/SKILL.md). Prompts are entry-points; skills are bodies. - Authoring an instruction (always-on or pattern-applied rule) → use [instruction-creator](../instruction-creator/SKILL.md) - Authoring an agent (delegated sub-process role) → use [agent-creator](../agent-creator/SKILL.md) ## The Seven Phases Each phase inverts one of the five gates. Author against the phase, pass the gate. ### Phase 1 — Intent capture Answer in writing before any drafting: 1. **What workflow does this kick off?** One sentence. If it contains "and" / "+", you have two prompts — split. 2. **What slash-command does the user type?** The filename (minus `.prompt.md`) becomes `/<name>`. Pick something a user would intuitively type. `/review-instruction` good; `/v2-thing-do` bad. 3. *