Guide / Claude Code
Working method
Claude Code by tier
The MVP skill can be used at any tier to move faster. Which connection method you use depends on where the build sits.
Supabase MCP
Connect Claude Code directly to Supabase through the MCP server for fast iteration against a live schema.
- Use the MVP skill to scaffold quickly and keep scope inside the tier's boundary
- Good for solo technical proofs and early business proofs still on a personal Supabase account
- Skip Docker overhead while the project is small enough to iterate directly
Docker + CLI, or MCP
As a build approaches integration and production concerns, move to a Dockerised workflow driven from the CLI, or continue with MCP where it still fits.
- Use once the project has transferred to the Statera Pro Supabase account
- Appropriate once non functional requirements (security, load, multi tenancy) enter scope
- Coordinate with devops once the target is the Statera server
MVP skill
Applies regardless of which tier a build sits in.
- Encodes what is explicitly out of scope for the current tier, so Claude Code does not gold plate a one day proof with error handling nobody asked for
- Keeps a running spec as the build progresses, so context is not trapped with one engineer
- Use it from day one of any build, not only once a project is already underway
Cursor Composer is fine to use for general editing. When using Cursor, do not use Claude models inside it. Claude models are used only through Claude Code, either in the console or in the app. This keeps usage and behaviour consistent across the team rather than split across two different runtimes of the same model.