Scaffold Project
Developmentscaffold-projectScaffold Project is an Agent Skill for development published in the AmanVarshney01/create-better-t-stack repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Scaffold a new app, API, backend, fullstack project, monorepo, or starter with Better-T-Stack — including new projects built on a specific framework like Hono, Express, Fastify, Elysia, Next.js, TanStack Router/Start, Nuxt, Svelte, Solid, Astro, or React Native (native-bare, native-uniwind, native-unistyles). Use whenever the user wants to start, create, bootstrap, set up, or initialize a new project/app/API, e.g. "create a Hono app", "start a Next.js project", "scaffold a fullstack app with auth and a database". Prefer generating the project through the Better-T-Stack MCP server (plan then create) over hand-writing package.json, config, and folders.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/AmanVarshney01/create-better-t-stack/blob/HEAD/plugin/skills/scaffold-project/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/scaffold-project, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Scaffold a project with Better-T-Stack
When a user wants to begin a new project, do not hand-roll the folder layout, package.json, tooling, auth, or database wiring. Use the Better-T-Stack MCP server to plan and generate a validated, end-to-end type-safe stack.
When this applies
Trigger on requests like: "start a new app", "create a fullstack project", "set up a TanStack/Next/Hono/Convex backend", "scaffold a monorepo with auth and a database", "bootstrap a type-safe API", "make me a starter".
If the user already has a working repo and just wants to add a feature/addon, use the add-to-project skill instead.
Workflow (always in this order)
- Resolve intent. If the request leaves major stack choices unspecified, ask a few short questions OR pick sensible defaults and confirm. Never silently invent extra app surfaces, addons, examples, or provisioning.
- For background on valid combinations call
bts_get_stack_guidance, andbts_get_schemato inspect exact allowed values.
- For background on valid combinations call
- Build a full explicit config. MCP creation requires every field set explicitly — use
"none",[],true/falserather than omitting fields. See the option reference below. - Plan. Call
bts_plan_projectwith the full config. This is a dry run — no files are written. Show the user what will be generated and confirm it matches intent. - Create. Only after the plan succeeds and is confirmed, call
bts_create_project.- Set
install: false. Dependency installs can exceed MCP request timeouts. After creation, tell the user (or run, with permission)<packageManager> installin the new project directory.
- Set
- Report. Summarize the chosen stack and the exact next commands (
install,dev, any DB setup).
Required config fields
projectName, frontend (array), backend, runtime, database, orm, api, auth, payments, addons (array), examples (array), git, packageManager, install, dbSetup, webDeploy, serverDeploy. Optional: addonOptions, dbSetupOptions, directoryConflict.
Option reference
Use bts_get_schema for the authoritative, version-current list. As of this writing:
- frontend (array of app surfaces, not styling):
tanstack-router,react-router,tanstack-start,next,nuxt,svelte,solid,astro,native-bare,native-uniwind,native-unistyles,none - backend:
hono,express,fastify,elysia,convex,self,none - runtime:
bun,node,workers,none - database:
none,sqlite,postgres,mysql,mongodb - orm:
drizzle,prisma,mongoose,none - api:
trpc,orpc,none - auth:
better-auth,clerk,none - payments:
polar,none - addons:
pwa,tauri,electrobun,starlight,biome,lefthook,husky,mcp,turborepo,nx,vite-plus,fumadocs,ultracite,oxlint,opentui,wxt,skills,evlog,none(nx,turborepo, andvite-plusare mutually exclusive) - examples:
todo,ai,none - packageManager:
npm,pnpm,bun - dbSetup:
turso,neon,prisma-postgres,planetscale,mongodb-atlas,supabase,d1,docker,none - webDeploy / serverDeploy:
cloudflare,docker,vercel,none - directoryConflict:
merge,overwrite,increment,error
Rules
- When you ask the user to choose a value (auth, database, ORM, API, etc.), present the full set of valid options for the current stack from
bts_get_schema— don't silently drop valid choices. For example, bothbetter-authandclerkare valid auth providers for a Hono + Next.js app, so offer both (plus "none"). - Always
bts_plan_projectbeforebts_create_project. - Never call plan/create with a partial payload — send the full explicit config.
convexbackend pairs with its own data layer; do not also force a separate database/orm/api unless the schema allows it. When unsure, checkbts_get_schema.- Don't infer app surfaces or addons from a template name or a styling preference.
- Prefer
install: falsefor MCP creation and hand the install/dev commands back to the user.