Scaffold a working Next.js product with backend, auth, i18n, and an operations CLI in one command. Give your agent a structure it can understand, extend, deploy, and operate.
Next.js, the SPFN backend, database wiring, auth, i18n, and ops commands arrive as one working full-stack foundation.
Add the OAuth, storage, and infrastructure credentials your product needs. Spend the first session on the idea, not login plumbing.
Entity, Repository, Route, Router — the same vertical slice for every feature. Your agent knows where to read and where to write.
Runtime validation, generated migrations, explicit boundaries, and end-to-end types keep fast changes reviewable.
Start with the foundation most products need, already arranged for an agent to continue building.
Start with the core full-stack pattern and choose every additional function yourself.
Write the operations you allow as routes under /_ops and run them with spfn ops, in the same terminal your coding agent already works in. Each command has its own input schema and authorization rule. No admin dashboard to build first. When operators work outside a terminal, write the same operations as MCP tools with @spfn/mcp, over the same services.
Ops routes call the same repositories and services as the product instead of duplicating business rules.
Every command answers only to a scoped, revocable ops token from @spfn/auth. A command the app marks destructive needs --yes.
spfn ops list reads what the deployed app exposes, and --describe prints each command's usage from the app's own schemas.
Server, routing, database, codegen — the framework kernel.
Sessions, OAuth, RBAC, invitations.
Object storage — S3-compatible, GCS, and local disk.
Email and messaging, pluggable providers.
Error tracking, logs, and a ready-made admin dashboard.
Content models and admin endpoints.
Pipelines of background jobs, with resume and rollback.
Serve a website from a repo — this site runs on it.
One MCP contract over authenticated HTTP or local stdio.
Translation catalogs and React context, application-owned.
Data migrations in TypeScript that run exactly once.
One signer over local keys, GCP KMS, and AWS KMS.