Bootstrap Project

bootstrap-project

Invariants

• Use the canonical stack: Next.js 16 App Router, Sanity v5, Tailwind 4, shadcn/ui, TypeScript, npm. Do not offer alternatives.
• Source code comes from eljun/kt-monorepo-template via git clone --depth 1. Do not generate boilerplate inline as a fallback if the clone fails.
• Design tokens are an INPUT (file path or paste-in). Do not invent or generate them.
• Stop and confirm before each irreversible cloud action: GitHub repo creation, Vercel project link, git push. Never auto-create Sanity projects.
• Do not run npm run dev automatically — leave it for the user.
• Emit a one-line status message before each major step so the user sees progress.

Prerequisites

Run these checks first. If any fail, stop and report which one.

Inputs (ask the user, in order)

1. Project slug — kebab-case, used for directory name and repo names. Example: acme-wellness-spa.
2. Project display name — used in copy and package.json. Example: Acme Wellness Spa.
3. Project description — one-line tagline used in package.json description, CLAUDE.md, and <title> metadata. Example: Boutique wellness studio in Brooklyn.
4. Project directory — default: ~/Code/Personal/{slug}.
5. Design tokens source — one of:
   • Absolute path to a CSS file containing the @theme block to inject into app/globals.css
   • skip — keep the template's placeholder palette
6. GitHub visibility — private (default) or public.
7. Sanity project — one of:
   • existing — user provides project ID + dataset name
   • new — user creates a project at https://sanity.io/manage in a new tab, then provides the project ID + dataset name (skill never creates Sanity projects automatically)
8. Vercel project name — default: same as slug.

Workflow

1. Verify prerequisites. Run all checks. Stop on failure.
2. Confirm inputs. Echo answers back as a summary. Wait for explicit "go" before any side effects.
3. Clone template. Status: "Cloning kt-monorepo-template..."

   git clone --depth 1 https://github.com/eljun/kt-monorepo-template.git {target_dir}
   rm -rf {target_dir}/.git
   

4. Substitute placeholders. Status: "Substituting project placeholders..."
   • Find files containing placeholders: grep -rl '{{PROJECT_' {target_dir}
   • Replace {{PROJECT_SLUG}}, {{PROJECT_NAME}}, {{PROJECT_DESCRIPTION}} across all matches.
   • The template's README documents the expected substitution surface — verify the grep result is non-empty before continuing.
5. Inject design tokens. Status: "Injecting design tokens..." (skip if user chose skip)
   • Read user's tokens file.
   • Replace the @theme { ... } block in {target_dir}/app/globals.css with the user's contents. Preserve everything else in globals.css.
6. Wire Sanity config. Status: "Wiring Sanity config..."
   • Copy .env.example → .env.local in {target_dir}.
   • In .env.local, replace your-project-id with the user-provided Sanity project ID.
   • If the dataset name differs from production, update the NEXT_PUBLIC_SANITY_DATASET line accordingly.
   • No code edits required: sanity/sanity.config.ts and sanity.cli.ts read NEXT_PUBLIC_SANITY_PROJECT_ID and NEXT_PUBLIC_SANITY_DATASET from the environment at runtime.
7. Install dependencies. Status: "Installing dependencies (this may take a minute)..."

   cd {target_dir} && npm install
   

8. Initial commit. Status: "Creating initial commit..."

   cd {target_dir} && git init && git add . && git commit -m "feat: initial scaffold from kt-monorepo-template"
   

9. Confirm GitHub repo creation. Show user: "About to run gh repo create eljun/{slug} --{visibility} --source . --remote origin. OK?" Wait for explicit confirmation.
10. Create GitHub repo. Status: "Creating GitHub repo..." Run the confirmed command.
11. Confirm Vercel link. Show user: "About to run vercel link (interactive, may ask scope and project name). OK?" Wait for confirmation.
12. Link Vercel. Status: "Linking Vercel project..."

    cd {target_dir} && vercel link
    

    The CLI prompts the user for scope and project — do not try to script around it.
13. Pull Vercel env.

    cd {target_dir} && vercel env pull .env.local
    

    The file may be empty if no env vars are set yet — that is fine.
14. Confirm push. Show user: "About to push to GitHub. OK?" Wait for confirmation.
15. Push to GitHub. Status: "Pushing to GitHub..."

    cd {target_dir} && git push -u origin main
    

16. Final report. Print a structured summary with these fields:
    • Local directory
    • GitHub URL: https://github.com/eljun/{slug}
    • Vercel project URL (from vercel link output)
    • Sanity project ID + dataset
    • Sanity Studio URL: http://localhost:3000/studio (once dev runs)
    • Next steps: cd {target_dir} && npm run dev

Status messages (emit before each step)

Failure handling

Out of scope (v1)

• Stack alternatives (Svelte, Supabase, Material UI, Pages Router, etc.)
• Automatic Sanity project creation
• Automatic dev server startup
• CI/CD workflow configuration
• Custom domain setup on Vercel
• Sanity content seeding or migration

Handoff

End with the structured report from step 16, plus:

Project bootstrapped: {target_dir}
Status: ready for first dev session
Next: cd {target_dir} && npm run dev