Spec-prompts that carry their own expertise.
Compose modular, forkable spec sections for your AI coding agent. Every section ships with the examples, pitfalls, and acceptance criteria that spare your agent the wrong turns someone already took — not just a description of what to build.
A Section is three layers, not a blob of text.
Most prompt libraries hand your agent a paragraph and hope. A SpecSpace Section separates the shape from the substance from the expertise — so each part can be reused, checked, and improved on its own.
The shape it must take
A typed contract for the section — fields, depth profile, and what it depends on. Composable and machine-checkable.
What to actually do
The concrete instruction your agent reads — written once, refined over time, reusable across every project that needs it.
Why it goes right
Worked examples, known pitfalls, and acceptance criteria for judging the result — expertise that travels with the section instead of living in someone's head.
More than a prompt library.
A prompt library hands your agent text. SpecSpace hands it structured, reusable expertise — and the composition tools to shape it into exactly the spec each build needs. Each capability below is labeled honestly: live now, or on the roadmap.
Fork, merge & split
Adapt a section without touching the original, reconcile two that overlap, or break up one that outgrew its scope — composition at section granularity.
Depth profiles
One section at three resolutions — lite · standard · rigorous. A quick prototype and a production build draw from the same source of truth.
Templates that stay current
Bundle sections into ordered templates. Improve a section once and every template built on it inherits the change — no copy-paste drift.
A marketplace, not a blank page
Start from community sections instead of an empty prompt. Publish your own, and let the guidance compound as others fork and refine it.
Export anywhere, no lock-in
Author here, build where you already do — export into Spec Kit, Kiro, OpenSpec, Claude Code, or Cursor. SpecSpace owns the authoring, never your workflow.
Security-pack modules
In development: drop-in sections for the parts that bite — auth, access control, session handling, input validation — with the known pitfalls written in before the agent starts.
From blank prompt to a spec your agent follows.
Pick or fork sections
Start from the marketplace or your own library. Fork anything to fit your stack and conventions — the guidance comes with it.
Compose a template
Order the sections, set the depth profile, and let each section's examples, pitfalls, and acceptance criteria travel along.
Export & build
Hand the result to Claude Code, Cursor, or Spec Kit. The agent gets the expertise, not just the ask.
Specspace, running inside Claude Code.
One install brings the catalog and the compose skill into the agent you already use. The MCP server is wired to the Specspace API, so sections, guidance, and saved specs flow without leaving the session.
$claude plugin install https://github.com/TAESTUDIOS/specspaceclaudecodeAdds the plugin and its MCP server. Sections stream from specspace.io — no local catalog to keep in sync.
>approve the sign-inThe first run opens a browser. Approve with your Specspace (GitHub) sign-in — you never paste a token.
>“compose a spec for a next.js auth module”The skill lists sections, reads each one's guidance, fills the fields, and saves the spec to your account.
Also runs in OpenAI Codex — the same MCP server, installed with a one-line ./install.sh. Early access: both plugin repos are private during pre-release, so request access from Specspace before installing.
Start solo. Scale to a shared canon.
One source of spec truth for the whole team.
When your team adopts it, shared workspaces keep everyone composing from the same sections — with roles deciding who can edit the canon.
Start free. Upgrade when it earns it.
- Public sections & templates
- Fork, merge & split
- Marketplace access
- Everything in Free
- Private sections & templates
- CLI / API & multi-format export
- Everything in Pro
- Shared team libraries
- Roles & access controls
Stop re-explaining the same thing to every agent.
Write the section once, with the guidance that makes it land — then compose it into everything you build.