Prompt Template Library

The Problem

Teams waste time reinventing prompts for the same recurring tasks. One developer writes great code review prompts; another struggles with the same task. Without shared templates, prompt quality depends on individual skill, and good techniques are lost when people switch projects or leave the team.

The Prompt

Help me create a reusable prompt template for: [TASK TYPE]

The template must include:
1. A clear TITLE and PURPOSE description
2. REQUIRED VARIABLES marked with {{double_braces}}
3. OPTIONAL VARIABLES marked with {{?optional_variable}}
4. DEFAULT VALUES for optional variables
5. OUTPUT FORMAT specification
6. VALIDATION RULES (what makes a good vs bad output)

TEMPLATE FORMAT:
---
Title: [template name]
Purpose: [one line description]
Variables:
  - {{variable}}: [description] (required)
  - {{?variable}}: [description] (optional, default: [value])
---
[The actual prompt template with {{variables}}]
---
Quality Check:
- [ ] [criterion 1]
- [ ] [criterion 2]
---

Make the template generic enough to reuse across projects but specific enough to produce consistent results.

Example Output

---
Title: Code Review Template
Purpose: Review code changes for quality, security, and maintainability
Variables:
  - {{code}}: The code diff or file to review (required)
  - {{language}}: Programming language (required)
  - {{?focus}}: Specific review focus (optional, default: "general quality")
  - {{?severity}}: Minimum severity to report (optional, default: "medium")
---
Review this {{language}} code with focus on {{?focus}}.

Report issues at {{?severity}} severity or higher.

For each issue:
- Location (file:line)
- Severity (critical/high/medium)
- Description (one sentence)
- Fix (code snippet)

Code:
{{code}}
---
Quality Check:
- [ ] Every issue has a concrete fix, not just a description
- [ ] No false positives for idiomatic patterns
- [ ] Security issues are flagged as critical
---

When to Use

Use this skill when your team performs the same AI-assisted tasks repeatedly — code reviews, documentation generation, data analysis, bug triage, or content creation. Building a template library standardizes quality across the team and onboards new members faster.

Pro Tips

• Version your templates — store them in your repo alongside your code so they evolve with your project conventions.
• Add a quality checklist — a validation section at the bottom helps users spot-check the output without expertise in prompt engineering.
• Start with your 5 most common tasks — do not try to template everything; focus on high-frequency, high-impact workflows first.
• Collect feedback from users — track which templates produce good results and which need iteration; build a feedback loop into your template library.