A prompt-native workflow engine
for Claude Code.
Structured sessions. Swappable cartridges. No tooling overhead.
Defined stages of work: shape the problem, break it down, design the solution, build, review. Each phase has a specific job and a specific role doing it.
SHAPE → BREAKDOWN → DESIGN → BUILD → CHECK Claude adopts the right role at each phase — Requirements Engineer, Architect, Developer, Code Reviewer. Role-switching is functional, not theatrical.
Requirements Engineer · Architect · Developer · Reviewer Explicit checkpoints between every phase. Three responses: y to advance, adjust to stay, pause to stop safely. Nothing advances without your confirmation.
→ Advance to DESIGN? (y / adjust / pause) Domain-specific phase sequences and role rosters, swappable without touching the engine. Software development, blog writing, code audits — each gets the right workflow.
/frame load sw-development
FRAME is the platform. Cartridges are the product.
Load any cartridge to start a structured session for that domain.
APIs, services, features, full-stack
Canon TDD — red → green → refactor until the test list is empty
Claude Design prototype → reviewed → production implementation
Essays, tutorials, long-form content
Architecture review, vulnerability scan, or both
Understand what a codebase does and how
Backlog generation and milestone structuring
Turn audit or analysis output into tickets
Profile authorship from a CV
Document changes made outside of FRAME
Design and author a new Claude Code skill
Deploy, verify the result, roll back on failure
Design and author a new FRAME cartridge
Clone the repo and run the installer. It copies the engine and cartridge library to your home directory. Prompts before overwriting — safe to re-run.
Open a Claude Code session in your project directory. Pick a cartridge that matches your task. FRAME reads your project and adopts the first phase role immediately.
The Requirements Engineer role opens with focused questions about goal, stack, constraints, and acceptance criteria — one at a time. Confirm the gate to advance to the next phase.
→ Advance to BREAKDOWN? (y / adjust / pause)
Cartridges chain together. Each workflow is a sequence of
/frame load <cartridge> runs — output of one feeds the next.
From idea to a structured, prioritised backlog ready for implementation.
Run a quality and security audit before a release and turn every finding into a tracked task.
Structural analysis of an existing codebase, turned into actionable work items.
Write a blog post, article, or essay from idea to publishable draft.