Build a Prompt Library That You'll Actually Use

{
  "name": "Code review — security focus",
  "category": "Development",
  "task": "Review code for security vulnerabilities before shipping",
  "variables": ["{{code}}", "{{language}}", "{{context}}"],
  "prompt": "You are a security-focused code reviewer. Review the {{language}} code below for vulnerabilities. Focus on: SQL injection, authentication issues, input validation, data exposure. For each issue give: the line, the severity (Critical/High/Medium), and the exact fix.\n\nContext: {{context}}\n\nCode:\n{{code}}",
  "notes": "Best with specific context about what the code does. Works well for auth endpoints, API routes, database queries.",
  "last_used": "2026-05-20",
  "quality": "high"
}

# Prompt Library

## Development

### Code Review — Security Focus
**Task:** Review code for security issues before shipping
**Variables:** {{code}}, {{language}}, {{context}}

```
You are a security-focused code reviewer. Review the {{language}} code below...
[full prompt text]
```

**Notes:** Best for auth endpoints and API routes. Overpowered for simple utility functions.
**Last used:** 2026-05-20

---

### Explain This Error
**Task:** Get a clear explanation of an error + fix
**Variables:** {{error}}, {{code}}, {{expected}}, {{actual}}

```
Error: {{error}}
Code: {{code}}
Expected: {{expected}}
Actual: {{actual}}

Explain the cause step by step, then give the fix.
```

---

## Writing

### Client Email — Professional Tone
...

{
  "version": "1.0",
  "prompts": [
    {
      "id": "code-review-security",
      "name": "Code Review — Security Focus",
      "category": "development",
      "tags": ["code-review", "security", "production"],
      "task": "Review code for security vulnerabilities",
      "variables": ["code", "language", "context"],
      "prompt": "You are a security-focused code reviewer...",
      "notes": "Best for auth endpoints and API routes",
      "quality": "high",
      "last_used": "2026-05-20"
    }
  ]
}

── EXPLAIN THIS ERROR ──────────────────────────────────────────────────
Error: {{error}}
Code: {{code}}
Expected: {{expected_behaviour}}
Actual: {{actual_behaviour}}

Explain what is causing this error step by step. Then give the exact fix.

── CODE REVIEW ─────────────────────────────────────────────────────────
Review this {{language}} code. Flag: bugs, edge cases not handled, security issues,
and readability problems. Give severity (Critical/Major/Minor) for each.
Do not suggest style changes as if they are bugs.

Code: {{code}}

── REFACTOR REQUEST ────────────────────────────────────────────────────
Refactor this function. Constraints: do not change the function signature,
do not introduce new dependencies, optimise for readability.
Show BEFORE and AFTER. List every change with a one-line explanation.

Function: {{code}}

── MATCH MY TONE ──────────────────────────────────────────────────────
Here are 3 examples of my writing: {{writing_samples}}

Now write {{deliverable}} in exactly my style. Mirror: sentence length,
vocabulary level, tone, and punctuation habits. Do not "improve" my writing.

── EMAIL: FIRM BUT PROFESSIONAL ───────────────────────────────────────
Write an email about {{situation}}. The message needs to be firm and direct
without being aggressive. Tone: professional peer, not subordinate.
Under 150 words. Subject line included.

── FIRST DRAFT FROM NOTES ─────────────────────────────────────────────
Turn these rough notes into a coherent first draft. Preserve all the ideas
but fix structure and flow. Notes: {{notes}}
Output: prose paragraphs, no bullet points. ~{{word_count}} words.

── STRUCTURED ANALYSIS ────────────────────────────────────────────────
Analyse {{topic}} for {{purpose}}. Cover:
1. Key facts (verified, no speculation)
2. Key unknowns (what we don't know yet)
3. Implications for {{context}}
4. Recommended next step

── STEELMAN + COUNTER ─────────────────────────────────────────────────
Give me the strongest possible argument FOR {{position}}, then the strongest
argument AGAINST it. I want both sides at their best, not straw-manned.
Do not give me your opinion.

── DECISION FRAMEWORK ─────────────────────────────────────────────────
I need to decide between: {{option_a}} and {{option_b}}.
My priorities in order: {{priorities}}.
Compare both options against each priority. Give a recommendation with
the one most important tradeoff I should accept.

── EXECUTIVE SUMMARY ──────────────────────────────────────────────────
Summarise this for a senior decision-maker who has 2 minutes.
Format: 3-sentence summary, then 3 key takeaways as bullet points.
No filler. No "this document discusses..." openers.

Content: {{content}}

── MEETING NOTES → ACTION ITEMS ───────────────────────────────────────
From these meeting notes, extract:
1. Decisions made (with who decided)
2. Action items (owner, deadline if mentioned)
3. Open questions (unresolved issues)
4. Any explicit blockers

Notes: {{meeting_notes}}

── LONG THREAD SUMMARY ────────────────────────────────────────────────
Summarise this email/Slack thread. I need: what the current situation is,
what decision or action is being requested of me, and the deadline if any.
One paragraph. Thread: {{thread}}

── EXPLAIN TO ME ──────────────────────────────────────────────────────
Explain {{concept}} to someone who knows {{existing_knowledge}} but has not
encountered {{concept}} before. Use an analogy first, then the technical detail.
No jargon unless you immediately define it.

── QUIZ ME ────────────────────────────────────────────────────────────
Quiz me on {{topic}}. 8 questions, increasing difficulty.
Ask one at a time. After my answer: tell me if I'm right, explain the correct
answer, then ask the next question. Begin.

── COMPARE AND CONTRAST ─────────────────────────────────────────────
Compare {{thing_a}} and {{thing_b}} for someone deciding between them.
Cover: use cases each is best for, key differences, and a clear recommendation
for {{my_situation}}. Include a concrete example of each in action.