From better-t-stack
Scaffolds new apps, APIs, backends, fullstack projects, monorepos, or starters using Better-T-Stack with type-safe stacks across frameworks like Hono, Next.js, TanStack, and more.
How this skill is triggered — by the user, by Claude, or both
Slash command
/better-t-stack:scaffold-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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 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.
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.
bts_get_stack_guidance, and bts_get_schema to inspect exact allowed values."none", [], true/false rather than omitting fields. See the option reference below.bts_plan_project with the full config. This is a dry run — no files are written. Show the user what will be generated and confirm it matches intent.bts_create_project.
install: false. Dependency installs can exceed MCP request timeouts. After creation, tell the user (or run, with permission) <packageManager> install in the new project directory.install, dev, any DB setup).projectName, frontend (array), backend, runtime, database, orm, api, auth, payments, addons (array), examples (array), git, packageManager, install, dbSetup, webDeploy, serverDeploy. Optional: addonOptions, dbSetupOptions, directoryConflict.
Use bts_get_schema for the authoritative, version-current list. As of this writing:
tanstack-router, react-router, tanstack-start, next, nuxt, svelte, solid, astro, native-bare, native-uniwind, native-unistyles, nonehono, express, fastify, elysia, convex, self, nonebun, node, workers, nonenone, sqlite, postgres, mysql, mongodbdrizzle, prisma, mongoose, nonetrpc, orpc, nonebetter-auth, clerk, nonepolar, nonepwa, tauri, electrobun, starlight, biome, lefthook, husky, mcp, turborepo, nx, vite-plus, fumadocs, ultracite, oxlint, opentui, wxt, skills, evlog, none (nx, turborepo, and vite-plus are mutually exclusive)todo, ai, nonenpm, pnpm, bunturso, neon, prisma-postgres, planetscale, mongodb-atlas, supabase, d1, docker, nonecloudflare, docker, nonemerge, overwrite, increment, errorbts_get_schema — don't silently drop valid choices. For example, both better-auth and clerk are valid auth providers for a Hono + Next.js app, so offer both (plus "none").bts_plan_project before bts_create_project.convex backend pairs with its own data layer; do not also force a separate database/orm/api unless the schema allows it. When unsure, check bts_get_schema.install: false for MCP creation and hand the install/dev commands back to the user.npx claudepluginhub amanvarshney01/create-better-t-stack --plugin better-t-stackScaffolds boilerplate for APIs (FastAPI, Express), web apps (Next.js, Nuxt, SvelteKit), CLI tools, libraries, monorepos with best-practice stacks and directory structures.
Scaffolds projects with directory structures, configs, dependencies, linting, testing, CI/CD basics, and docs for frontend, backend, mobile, CLI, libraries, and monorepos.
Scaffolds full-stack applications from natural language requests. Selects tech stack, coordinates specialized agents, and applies project templates.