Menu

Individual skill

project-setup

Set up a new project from this Next.js + Sanity starter step by step, from `sanity init --template` or a plain `git clone` to a running site and go-live. Checks what is already done, then walks through Node and pnpm, `pnpm install`, the Sanity project and tokens, `web/.env.local` and `studio/.env(.local)`, linking `sanity.blueprint.ts` (CORS + revalidate webhook, `pnpm blueprints:plan` / `blueprints:deploy`), the first content (Studio, or `pnpm seed` when the project has it), checking `pnpm dev` and the Studio, the optional rename and brand files, and go-live on Vercel, stopping for confirmation after each step. Use when the user asks how to set up, bootstrap or start a project from the starter, to continue a half-done setup, which env vars to set, what the Next steps screen means, or why a fresh clone doesn't run.

base/.agents/skills/project-setup/SKILL.md

Read pinned source

Source commit d66f0fd9976e15ca51d6fcd5352482c5c66c281b

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
19
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Set up a new project, step by step

Walk the user through the steps below **in order, one at a time**:

- **Check first.** Each step starts with a check. If it shows the step is done, say so
  in one line and move on. The skill often starts on a half-set-up repo.
- **Done when.** Each step ends with a condition. Don't move on until it holds, or the
  user chooses to skip (then tell them what will break).
- **Stop between steps.** After each step, report in one or two lines what is done
  and what the next step is, and wait for the user to confirm before you start it.
- **Ask only for what you can't detect**, at the step that needs it.

The user runs the commands that need their accounts or change Sanity or hosting. In
this file a leading `!` marks such a command: give it to the user to run in their