GitHub Copilot prompt to build a SaaS starter app
Run this in agent mode and GitHub Copilot scaffolds the unglamorous half of a SaaS product: auth, organizations with roles, migrations, and config that fails loudly when a key is missing. You get a bootable {{language}} project backed by {{database}}, with {{addon}} wired at a marked integration point instead of faked.
Last updated
Scaffold a SaaS starter in a new project: {{language}} on the backend, {{database}} for data, and {{addon}} integrated for billing or email as appropriate. Set up auth with signup, login, password reset, and session middleware. Model organizations with a members table and an owner, admin, member role enum, and enforce roles in middleware, not in individual handlers. Ship three pages: a public landing page, an app shell behind auth, and a settings page for profile and org management. Add environment variable handling with a checked-in .env.example and a config module that fails fast on missing keys. Include seed and migration scripts wired to package scripts. Do not stub payments with fake success responses; leave a clearly marked integration point if keys are absent. Verify by booting the app, running migrations against a fresh database, and summarizing the directory structure.Customize it
Runs in your browser. Nothing you type here is sent anywhere.
Scaffold a SaaS starter in a new project: TypeScript on the backend, PostgreSQL for data, and input validation integrated for billing or email as appropriate. Set up auth with signup, login, password reset, and session middleware. Model organizations with a members table and an owner, admin, member role enum, and enforce roles in middleware, not in individual handlers. Ship three pages: a public landing page, an app shell behind auth, and a settings page for profile and org management. Add environment variable handling with a checked-in .env.example and a config module that fails fast on missing keys. Include seed and migration scripts wired to package scripts. Do not stub payments with fake success responses; leave a clearly marked integration point if keys are absent. Verify by booting the app, running migrations against a fresh database, and summarizing the directory structure.
Same task in other tools
Questions about this prompt
Agent mode stalls partway through a scaffold this big. What helps?
Split it at the natural seam: run the auth and data model half first, let it verify, then send the pages and {{addon}} wiring as a second prompt. Copilot keeps the session context, so the second half builds on the first.
How does Copilot handle the multi-tenancy model here?
It will scope queries by organization id if you keep the role-enforcement-in-middleware line, but audit the repository layer yourself. Missing an org filter on one query is the classic leak in generated SaaS code.
Can I make this single-tenant instead?
Delete the organizations and roles sentences and say "single user accounts only". Also drop the members table from the model so Copilot does not reintroduce it when generating the settings page.