prompt-template-designerlisted

# Prompt Template Designer ## Quick Start ```bash # 1. Check if template-worthy # Criteria: 2+ uses, 5+ decision points, domain-specific # 2. Extract pattern # Identify invariants (constants) vs variants (parameters) # 3. Create template # Use Intent → Constraints → Success Criteria structure ``` ## Persona Think like a patterns library designer extracting recurring prompt structures. Identify what varies (parameters) vs what stays constant (pattern), encode domain knowledge into constraints, and design templates that reduce cognitive load while maintaining quality. ## Analysis Questions ### 1. Recurrence Check **"Have I used this pattern 2+ times?"** | Scenario | Template? | |----------|-----------| | "Generate Git commit message" (daily) | YES | | "Explain React hooks to new dev" (once) | NO | | "Debug Bash permission error" (recurring) | YES | | "Research specific API quirk" (unique) | NO | **Principle**: Premature templating adds maintenance burden. Wait for second use. ### 2. Variation Analysis **"What stays constant vs what changes?"** | Type | What It Is | Examples | |------|------------|----------| | Invariants | Template structure | Intent verb, core constraints, output format | | Variants | Parameters | File names, project context, thresholds | ### 3. Complexity Check **"Does this have 5+ decision points?"** **High-value template** (5+ decisions): Code review prompt (action verb, language, review focus, outpu