agentleFS
bradydwardaibradydwardai/claude-skills/skills/project-scaffold/SKILL.md

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

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
  1. Distinctive:

    When starting a brand new project from scratch.

    line 16
  2. Distinctive:

    Follow the steps below in order.

    line 20
  3. Very specific:

    Create src/middleware.ts for Supabase auth session refresh.

    line 60
  4. Very specific:

    Keep production secrets in your deployment platform's environment settings (e.g.

    line 78
  5. Distinctive:

    Ensure these are included:

    line 81
  6. Very specific:

    Update src/app/layout.tsx with proper metadata and font setup.

    line 90
  7. Very specific:

    Update src/app/page.tsx with a clean landing page.

    line 91
  8. Distinctive:

    Add the conventions your workflow expects, for example:

    line 113
  9. Very specific:

    Use --private instead if the project should not be public.

    line 122
  10. Distinctive:

    Start your dev environment with secrets loaded, per your local setup.

    line 134

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-tailwindcss

Step 3: Install shadcn/ui

pnpm dlx shadcn@latest init -d

Step 4: Add common shadcn components

pnpm dlx shadcn@latest add button card input label form toast sonner

Step 5: Initialize Supabase

supabase init

Step 6: Create Supabase client files

Create:

  • src/lib/supabase/client.ts — Browser client using createBrowserClient
  • src/lib/supabase/server.ts — Server client using createServerClient with cookies
  • src/lib/supabase/middleware.ts — Middleware helper for auth session refresh

Step 7: Create utility files

  • src/lib/utils.ts — cn() helper for Tailwind class merging
  • src/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:3000

Step 10: Set up local secrets

Copy .env.example to .env.local and fill in your real Supabase project values:

cp .env.example .env.local

Keep 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
.vercel

Step 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 .nvmrc pinning 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=. --push

Use --private instead if the project should not be public.

Step 17: Verify

pnpm dev

Open 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.