project-init

SKILL: Project Init

Initialize a project so future sessions and handoffs work consistently in both Cursor and Claude Code. Default to the minimum: three docs plus git. A project earns more files by outgrowing these, not on day 0.

MISSION

Create the minimum durable scaffolding a project needs on day 0:

• Git repo initialized with a .gitignore, and an MIT LICENSE whenever the project uses git
• CLAUDE.md for project-facing AI guidance, including a short "What this is" and "Key decisions" section
• docs/WORKLOG.md with the task checklist (Now / Next) up top and rolling session notes below
• README.md baseline sections so agents and humans can pick up the repo quickly
• .cursor/rules/context-router.md for Cursor startup routing

Do NOT create SPEC.md, DECISIONS.md, ROADMAP.md, or PROJECT.md. Spec and decision content starts as sections inside CLAUDE.md; the escalation path (below) covers projects that outgrow that.

PROTOCOL (run in this exact order)

Invoking this skill is the user's confirmation for its standard outputs: create the files for the chosen scope without per-file approval. Only two questions need answers at either scope: the scope question and the git question. This overrides any general "state proposed changes and wait for confirmation" habit for files this skill is defined to create.

Step 1: Determine project scope

Ask the user:

"Is this a simple, smaller project (a script, a one-off page, a config, a quick artifact), or an in-depth build (an app or tool you'll develop over time)?"

Do not infer the answer from file types or folder contents, only the user knows how deep this project goes. Exception: if the user already described the project's depth earlier in the conversation, state the scope you inferred and ask them to confirm instead of asking from scratch.

Simple project:

1. Ask one setup question: "Will this live on git?"
   • Yes: run git init if not already a repo, create a minimal .gitignore (.DS_Store, .env, CLAUDE.local.md, plus stack-specific entries if detected), and create an MIT LICENSE, all automatically, no further questions. Use a different license only if the user names one. Do NOT ask where it will be pushed or create a remote; the completion report covers connecting to GitHub later. After all files are created, make an initial commit (Initial scaffold) so the folder is push-ready.
   • No: skip git, .gitignore, and LICENSE entirely.
2. Create or patch README.md with just: What this is, How to install/use it, and any key configuration. Skip "How to run it" / "How to test or preview" if they don't apply.
3. Create a minimal CLAUDE.md so return sessions start oriented (it's the file AI tools auto-load), using the template in assets/claude-md-simple.md.