I have 60+ prompt files. Most teams have a prompts.txt graveyard — 200 prompts nobody can find, all slightly different, none evaluated. The difference between a prompt collection and a prompt library is structure. I packaged the organized version into a $15 kit.
Flat prompt dumps fail because retrieval is the bottleneck. Organize by task type × cognitive mode:
extraction/ — pull structure from messy input (ticket→JSON, table→markdown)reasoning/ — think through a problem (pre-mortem, five-whys, assumption inventory)writing/ — produce prose (status update, release notes, exec summary)classification/ — sort into categories (triage, tagging, routing)code/ — generate or review codeanalysis/ — interpret data or text
A prompt belongs to exactly one category. If it does two things, it's two prompts.
Not just the prompt text — the context that makes it reproducible:
**When to use**: User pastes a bug report or feature request and wants
a structured ticket.
**Prompt**: Extract the following into JSON with fields: title,
description, severity, steps_to_reproduce, expected, actual.
Input: {{input}}
**Output contract**: Valid JSON only. No prose before/after.
If a field can't be determined, use null — never guess.
**Failure modes**: Model adds commentary → tighten "JSON only" to
first line. Model invents steps → add "if not stated, null".
**Version**: 1.2 — changed severity enum 2026-11
The When to use line is what makes a library navigable — it's the retrieval key. The failure-modes section is the institutional memory: every prompt encodes what broke last time.
A prompt library without evals is a folklore collection. For each critical prompt:
I don't ship evals for all 62 (honest scope — the kit has the structure,
you build the tests), but the format supports it: each prompt file has a
## Tests section placeholder.
Markdown files in folders beat a prompt-management SaaS for three reasons:
62 prompts cover maybe 20% of what you'll actually need — the other 80%
is prompts you'll write once and use twice. The library's value isn't
coverage, it's consistency: the prompts that DO get reused are the
ones written carefully, tested, and versioned.
The kit — 62 categorized prompts across 8 task types, each with when-to-use
Store (pay in BTC, no account, instant download): https://dev.to/nexusfoundry/nexus-store-live-link-auto-updated-1918