|
| 1 | +--- |
| 2 | +name: project-onboard |
| 3 | +description: Set up a project for smooth work with Claude Code — generate/update CLAUDE.md, propose an allowlist of permissions so it stops asking on repetitive commands, and suggest relevant MCP servers. Use when you first open a new repo with Claude Code. |
| 4 | +--- |
| 5 | + |
| 6 | +# project-onboard |
| 7 | + |
| 8 | +Goal: after `setup.sh` has prepared the *environment* (Ghostty + Claude Code |
| 9 | +installed), this skill prepares the *current project* so work is smooth from the |
| 10 | +first message. |
| 11 | + |
| 12 | +Run the steps in order. Be concise with the user; show what you did, don't explain |
| 13 | +the theory. |
| 14 | + |
| 15 | +## 1. Understand the repo |
| 16 | + |
| 17 | +- Detect the stack: look for `package.json`, `pyproject.toml`, `go.mod`, |
| 18 | + `Cargo.toml`, `Makefile`, `*.csproj`, etc. |
| 19 | +- Identify the build / test / lint / run commands (from scripts, Makefile, CI). |
| 20 | +- Note obvious conventions (formatter, folder structure, test framework). |
| 21 | + |
| 22 | +## 2. CLAUDE.md |
| 23 | + |
| 24 | +- If `CLAUDE.md` does **not** exist: run the equivalent of `/init` — generate a |
| 25 | + short one with: the key commands (build/test/lint/run), a brief structure |
| 26 | + overview, code conventions, and non-obvious things to know. Keep it tight (not |
| 27 | + an essay). |
| 28 | +- If it **exists**: read it, propose additions only for what's missing and useful. |
| 29 | +- Ask for confirmation before writing/committing. |
| 30 | + |
| 31 | +## 3. Permissions (fewer prompts) |
| 32 | + |
| 33 | +- From the commands found in step 1, propose an allowlist in `.claude/settings.json` |
| 34 | + for the safe & repetitive ones (e.g. `Bash(npm run test:*)`, `Bash(npm run build)`, |
| 35 | + `Bash(git status)`, `Bash(git diff:*)`). |
| 36 | +- Do NOT add destructive commands (deploy, push --force, rm). Read/test/build only. |
| 37 | +- Write to `.claude/settings.json` (project), not the global settings. |
| 38 | + |
| 39 | +## 4. Relevant MCP servers (optional) |
| 40 | + |
| 41 | +- If the project uses GitHub and `gh` is authenticated, suggest the GitHub MCP. |
| 42 | +- If it's a web/UI project, mention a browser MCP for visual verification. |
| 43 | +- Only suggest + show the command; don't install without an OK. |
| 44 | + |
| 45 | +## 5. Final summary |
| 46 | +Show a short list: |
| 47 | +- what was created/changed (CLAUDE.md, settings.json), |
| 48 | +- the detected test/build commands, |
| 49 | +- the recommended next step (e.g. "run /code-review after your first changes"). |
| 50 | + |
| 51 | +Rules: confirm before writing to versioned files; don't touch the user's global |
| 52 | +settings; don't invent commands — verify they exist in the repo. |
0 commit comments