Workflow
Build something real. Show people → Get feedback → Improve. Advance toward production.
The delivery loop
Every Catalyst project follows the same basic rhythm, regardless of stage.
Brief
Capture what you're building and why. Use prompts to anchor intent.
Build
Ship working software fast. Pick the simplest stack that proves value.
Review
Show stakeholders. Capture feedback. Make decisions together.
Refine
Improve based on feedback. Loop back to Brief, or advance when ready.
How it works
Proof-led alignment
Working software surfaces assumptions faster than documents. Show people something real and let them react.
Durable decisions
Key decisions get captured in artefacts. Three months later, you still know why you built it this way.
Staged advancement
POC quality is not production quality. Harden deliberately as you advance through stages.
Project setup
Setup the project. Before you start building, set up your project foundation.
Clone the repo, configure your surfaces, clear default content, and establish your project specs. This is the "0th" stage — done once at the start of every project.
INIT setup guideThe stages
Once setup is complete, advance through these stages. Production is a choice, not an accident.
Proof of Concept
Validate the idea. Ship something stakeholders can see and steer on. Rough is fine.
POC workflowMinimum Viable Product
Test with users. Real feedback, core flows working. Auth and persistence added.
MVP workflowMinimum Marketable Product
Public launch. Ready for paying customers. Polished UI, proper error handling.
MMP workflowProduction
Stability & scale. Enterprise-ready, security hardened, monitored, documented.
PROD workflowRunning delivery cycles
One cycle = one pass through Brief → Build → Review → Refine. Each phase has a natural checkpoint to confirm you're ready to move on. Run many cycles, advance when the work is validated.
Brief
"Is intent clear enough to build?"
Build
"Is it ready to show people?"
Review
"Do we understand what to change?"
Refine
"Loop again, or advance?"
Who does what
Clear roles prevent confusion. Humans lead; AI assists.
Project Lead
Runs meetings, makes scope calls, approves phases. The human accountable for delivery.
Project Agent
Stress tests requirements, produces artefacts, challenges assumptions. AI that thinks about scope.
Coding Agent
Proposes phase plans, builds features, maintains quality. AI that writes code.
Client / Stakeholder
Provides context, reviews progress, makes decisions. The humans you're building for.
Key insight
Different AIs should own different responsibilities. A single agent trying to handle context, scope, code, and sequencing produces inconsistent results. Separate the Project Agent (scope and artefacts) from the Coding Agent (build and quality).
Make it yours
Catalyst ships with a flexible design system. Colors, typography, and spacing are all customizable through CSS variables. Change the primary color and the whole UI updates. Most customization takes minutes, not hours.
Explore the Design System