project-scaffold
Skill0 starsChanged 3 months agoMITView on GitHub
When the user wants to scaffold a brand-new full-stack project from scratch with an opinionated, production-ready stack — Next.js 15 + TypeScript + Tailwind + shadcn/ui + Supabase + Vercel. Also use when the user says 'start a new project,' 'scaffold an app,' 'set up a Next.js project,' 'bootstrap a full-stack app,' or 'new project with Supabase.' Walks through the full setup in order: app creation, dependencies, shadcn, Supabase client/middleware, env, git, and deploy.
- Reads credentials
- Installs packages
18 other projects use a version of this.
Adopted by
Most recently taken up by
- ekajaya740/skillstheir own version, first seen Nov 1, 2026
- Hadi99K/AGENT_SKILLStheir own version, first seen Nov 1, 2026
- okfriansyah-moh/agentic-workflowtheir own version, first seen Oct 25, 2026
- kenming/project-scaffold-skilltheir own version, first seen Oct 20, 2026
- BojanKocijan/design-forgetheir own version, first seen Oct 19, 2026
- noahcostakes/claudebrain-templatetheir own version, first seen Oct 15, 2026
Other versions18 projects use a version of this.
Word for word · 1
- bradywardai/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 17
- RandallLiuXin/GodotMaker★ 555same name
- ojiudezue/productmind-skills★ 81same name
- kenming/project-scaffold-skill★ 18same name
- BojanKocijan/bk-charterline★ 4same name
- BojanKocijan/design-forge★ 4same name
- Hadi99K/AGENT_SKILLS★ 3same name
- GaryFigno/Dr.WangAgent★ 2same name
- jarxunlai/My-skills★ 2same name
- abdullah1854/ClaudeSuperSkills★ 1same name
- carlosedm10/skills★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- ai-seoSkill
- churn-preventionSkill
- copy-editingSkill
- explain-codeSkill
- free-tool-strategySkill
- marketing-psychologySkill
- popup-croSkill
- pricing-strategySkill
- programmatic-seoSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 16
When starting a brand new project from scratch.
- Distinctive: line 20
Follow the steps below in order.
- Very specific: line 60
Create src/middleware.ts for Supabase auth session refresh.
- Very specific: line 78
Keep production secrets in your deployment platform's environment settings (e.g.
- Distinctive: line 81
Ensure these are included:
- Very specific: line 90
Update src/app/layout.tsx with proper metadata and font setup.
- Very specific: line 91
Update src/app/page.tsx with a clean landing page.
- Distinctive: line 113
Add the conventions your workflow expects, for example:
- Very specific: line 122
Use --private instead if the project should not be public.
- Distinctive: line 134
Start your dev environment with secrets loaded, per your local setup.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Scaffold
Scaffold a full-stack project with Next.js 15 + TypeScript + Tailwind + shadcn/ui + Supabase + Vercel.
Description
Creates a complete, production-ready project from scratch with an opinionated, conventional tech stack.
When to Use
When starting a brand new project from scratch.
Instructions
Follow the steps below in order. Stop and report if any step fails.
Step 1: Create Next.js app
pnpm create next-app@latest <project-name> --typescript --tailwind --eslint --app --src-dir --import-alias "@/*"
cd <project-name>Step 2: Install core dependencies
pnpm add @supabase/supabase-js @supabase/ssr zod
pnpm add -D @types/node prettier prettier-plugin-tailwindcssStep 3: Install shadcn/ui
pnpm dlx shadcn@latest init -dStep 4: Add common shadcn components
pnpm dlx shadcn@latest add button card input label form toast sonnerStep 5: Initialize Supabase
supabase initStep 6: Create Supabase client files
Create:
src/lib/supabase/client.ts— Browser client usingcreateBrowserClientsrc/lib/supabase/server.ts— Server client usingcreateServerClientwith cookiessrc/lib/supabase/middleware.ts— Middleware helper for auth session refresh
Step 7: Create utility files
src/lib/utils.ts— cn() helper for Tailwind class mergingsrc/lib/types.ts— Shared TypeScript types
Step 8: Set up middleware
Create src/middleware.ts for Supabase auth session refresh.
Step 9: Create .env.example
# Supabase
NEXT_PUBLIC_SUPABASE_URL=your-project-url
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
# App
NEXT_PUBLIC_APP_URL=http://localhost:3000Step 10: Set up local secrets
Copy .env.example to .env.local and fill in your real Supabase project values:
cp .env.example .env.localKeep production secrets in your deployment platform's environment settings (e.g. Vercel) or a secrets manager — never commit .env.local.
Step 11: Update .gitignore
Ensure these are included:
.env.local
.env
node_modules
.vercelStep 12: Create initial layout
Update src/app/layout.tsx with proper metadata and font setup.
Update src/app/page.tsx with a clean landing page.
Step 13: Add Prettier config
Create .prettierrc:
{
"semi": false,
"singleQuote": true,
"tabWidth": 2,
"trailingComma": "es5",
"plugins": ["prettier-plugin-tailwindcss"]
}Step 14: Git init and first commit
git init
git add -A
git commit -m "feat: initial scaffold with Next.js 15, Supabase, shadcn/ui"Step 15: Add project conventions
Add the conventions your workflow expects, for example:
- An agent instruction file (e.g.
CLAUDE.md,AGENTS.md) documenting the stack and conventions. - An
.nvmrcpinning the Node version. - Any slash-command or editor instruction files your team uses.
Step 16: Create the GitHub repo and push
gh repo create <project-name> --public --source=. --pushUse --private instead if the project should not be public.
Step 17: Verify
pnpm devOpen http://localhost:3000 and confirm it loads.
Post-Scaffold
- Link Vercel:
vercel link - Link Supabase:
supabase link --project-ref <ref> - Store your Supabase keys in your deployment platform's environment settings or a secrets manager.
- Start your dev environment with secrets loaded, per your local setup.
Output
Print a summary of everything created:
- Files created
- Dependencies installed
- Next steps for the developer
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

