The engine returns a prepared prompt plus the phase instructions for the selected framework, and the calling model carries those phases out itself — read that way this is a library and a chain runner rather than an extra reasoning layer, which is the right expectation to have before installing it. The gates are where the value concentrates: a criterion with a retry configuration, or a shell command that has to pass, turns "and then check it" into part of the chain. Whether it feels native or mediated depends on your client, since the shorthand operators only work where the plugin's hooks are installed.
A prompt-library server with three tools: an engine that runs stored prompts and chains, one resource tool that is CRUD over the prompts, gates and frameworks themselves, and a control tool for switching frameworks and reading state.
- Stored prompts invoked by id with named arguments, versioned in YAML with hot reload and rollback, and a starting library of 39 prompts across 8 categories
- Chains where one step feeds the next, resumable by id or restarted outright, with validation running between steps rather than only at the end
- Gates as a first-class primitive: a criterion the model checks its own output against, blocking or advisory, and able to verify by running a shell command such as a test suite
- Verification loops with try-and-timeout presets, so "implement, run the tests, read the failures, fix" is a configuration rather than a habit
- Reasoning frameworks switched per run or persisted — CAGEERF, ReACT, 5W1H and SCAMPER, or one you author
- Prompts, gates and frameworks created, updated, listed and rolled back through a single resource tool, with the model authoring new ones as it works
- Templates exported as client-native skills, so a stored prompt becomes a slash command in your client with no MCP call at runtime
- Server status, metrics and history for what is currently loaded
Node and nothing to authenticate: no environment variables and no account. The bundled library gives you something to run on day one; your own resources live in a workspace the server scaffolds for you, or an existing one named by MCP_RESOURCES_PATH. Client plugins add hooks — so the shorthand operators work in conversation and chain state survives context compaction — on Claude Code and OpenCode, partly on Gemini CLI, and experimentally on Codex; any other MCP client gets the three tools without them. MIT.
One command — npx -y claude-prompts@latest --client claude-code