The copy-paste that lost the lock
New features start by copying the last one. Each copy drops a permission check here, a version column there, until the pattern isn't a pattern anymore. Here, features are generated complete, every time.
Ship every weekShipping systemdeveloper-experience
One-command features
Start a full feature with one command. Half-built code can't sneak into production.
One command generates a complete new feature: checks, permissions, live updates, and tests, all wired in. Nothing you scaffold can reach production until its checks pass for real. Copy-paste drift and sneaky shortcuts fail the build instead of piling up.
- 1 command to start a full feature
- 0 unfinished features that can reach production
- 1 paved check to run before you ship
1 of 6 in Ship every week
How it works
The mechanism end to end, as implemented in the repository.
- 1
Scaffold the slice
One command generates the whole feature: input contracts, permission-checked server services, client wiring, a tenant-scoped live-sync shape, and its tests. It refuses to overwrite existing code.
- 2
Build with fast feedback
Test commands run only what your changes touch, and a doctor command reports config and service health without printing secrets.
- 3
Certify to promote
A certification run is the only way a draft feature becomes production-ready. CI rejects anything that skipped it.
- 4
Verify before release
One verify pass runs the architecture, registry, migration, and bundle-size gates, so drift shows up as a failed check with evidence, not a surprise in production.
Interactive example
See it working
This walkthrough demonstrates the implemented backend contract without using an account, credentials, or provider calls.
Interactive example
Walk the paved development path
- $ bun run scaffold resource · passed
Showing 1 of 4 checks
Deterministic sample data only. No account, provider, or network connection is used by the interaction.
The problem this solves
Without a shared foundation, every team rebuilds these edge cases — differently.
The prototype that went live
A half-finished experiment gets registered, deployed, and depended on before anyone decided it was ready. Here, draft code is locked out of production until it passes certification.
Rules that live only in a wiki
Your conventions sit in a markdown file nobody reads under deadline. They get re-argued in every review and quietly broken between reviews. Here, breaking them fails a check.
Highlights
Why it matters
Whole features, not snippets
One command generates the full slice: input checks, permission-checked server code, client wiring, live sync, and tests, already connected.
Unfinished stays unshipped
New scaffolds are marked immature and locked out of production until a certification run proves they work.
Shortcuts turn red
A pattern check catches known footguns, like unscoped caches or server secrets imported in the browser, and fails the build instead of letting them spread.
Engineering guarantees
What this does and does not promise
Safety boundary
Checks are honest about where they ran. A pass on your laptop or a disposable stack is never dressed up as hosted or production proof.
Implementation evidence
The boundary above is code, not a claim. These files carry the contract:
scripts/scaffold.tsscripts/certify-resource.tsscripts/check-patterns.tsdocs/DEVELOPER-EXPERIENCE.mddocs/RELEASE-CERTIFICATION.md
Questions
Frequently asked questions
Related capabilities
These capabilities share contracts and boundaries with this one.
Build on the one-command features foundation
The docs describe the same contracts this page demonstrates.