菜单
Initialize project-level Claude setup (gitignore entries, settings.local.json) without copying agent/skill files. Use this in projects where agents were installed globally (default setup.sh behavior).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Lightweight build: explore → plan → approve → implement in a single Opus context, no sub-agent fan-out. Verifies build + tests, optionally commits, and offers a separate /code-review pass at the end. Use by default for everyday features; reach for /build only when the work needs parallel fan-out or exceeds one context.
Full build pipeline: takes a PRD, breaks it into tasks, implements them in parallel, and reviews the result. Orchestrates prd-task-planner → parallel-task-orchestrator → code-reviewer.
Debug pipeline: investigates a bug, diagnoses root cause, writes failing tests, implements fix via TDD, and reviews the result. Orchestrates bug-investigator -> bug-fixer -> code-reviewer.
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /refactor only when the cleanup needs parallel fan-out or exceeds one context.
Refactoring pipeline: analyzes a target file or directory for code quality issues, plans safe incremental improvements, optionally writes tests first as a safety net, implements the changes, and reviews the result. Orchestrates refactor-planner → (test-writer) → parallel-task-orchestrator → code-reviewer.
Lightweight build: explore → plan → approve → implement in a single Opus context, no sub-agent fan-out. Verifies build + tests, optionally commits, and offers a separate /code-review pass at the end. Use by default for everyday features; reach for /claude-setup:build only when the work needs parallel fan-out or exceeds one context.
| name | init-claude-setup |
| description | Initialize project-level Claude setup (gitignore entries, settings.local.json) without copying agent/skill files. Use this in projects where agents were installed globally (default setup.sh behavior). |
| argument-hint |
You are initializing project-level Claude configuration for this repository. Follow the steps below strictly in order.
Check whether .claude/agents/ or .claude/settings.local.json exists in the current working directory.
.claude/agents/ exists: inform the user that this project already has a full local Claude install and no initialization is needed. Stop here..claude/settings.local.json exists: inform the user that this project already has project-level Claude setup and no initialization is needed. Stop here..gitignore in the project root. If it does not exist, treat it as empty.# .claude section comment if you are adding any:# .claude
.devcontainer/.env
.claude/settings.local.json
.claude/auth.local.md
.claude-worktrees/
.DS_Store
tasks/**
qa-output/**
debug-output/
.playwright-cli/
# .claude section)..claude/settings.local.json exists.{
"permissions": {
"allow": [],
"deny": []
}
}
Print a clear summary of what was done:
## Claude project setup complete
- .gitignore: [added N entries / already up to date]
- .claude/settings.local.json: [created / already existed]
### Next steps
- Run `claude login` if you haven't already
- Edit `.claude/settings.local.json` to configure per-project tool permissions
- Agents and skills are available through the installed `claude-setup` plugin
- The /claude-setup:qa skill uses `playwright-cli` for browser automation — run `playwright-cli install` to set it up