メニュー
Scan project and generate a customized CLAUDE.md. Detects stack, test commands, and conventions. Use when onboarding to a new project or user says 'init', 'setup claude', 'generate CLAUDE.md'.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | init |
| description | Scan project and generate a customized CLAUDE.md. Detects stack, test commands, and conventions. Use when onboarding to a new project or user says 'init', 'setup claude', 'generate CLAUDE.md'. |
| argument-hint | [project path] |
| allowed-tools | Read, Write, Glob, Grep, Bash(ls *), Bash(git log *) |
Scan the current project and generate a CLAUDE.md tailored to its stack and conventions.
Check for these files (in order):
package.json → Node.js (check for next, react, vue, angular, etc.)pyproject.toml or requirements.txt → Pythongo.mod → GoCargo.toml → RustGemfile → Rubypom.xml or build.gradle → Java/KotlinPackage.swift → SwiftRead the detected config file to identify:
Run ls at project root. Identify:
git log --oneline -10 — commit message styleRead the template from the neural-claude-code install directory. Replace placeholders:
{{PROJECT_NAME}} — from package.json name or directory name{{STACK_DESCRIPTION}} — detected stack summary{{LANGUAGE}} — primary language{{TEST_COMMAND}} — detected test command or "npm test"{{LINT_COMMAND}} — detected lint command or "npm run lint"{{DIRECTORY_MAP}} — key directories foundWrite to CLAUDE.md in project root.
Generated CLAUDE.md for [project name]
Stack: [detected stack]
Tests: [test command]
Lint: [lint command]
Review CLAUDE.md and adjust as needed.
Render a Claude Code plan (PlanViewer), a task result, or a recap of a branch/commit/PR diff (ResultViewer) as a single-file HTML artifact with anti-fatigue UX. Use when the user asks for an HTML artifact, a plan/result/recap view, or to "show this as HTML". Not for plain markdown/text or one-liners.
Build a planned change: take an approved /spec plan, capture a baseline, execute the subtasks, review with /vet and /exercise in a clean context, measure the delta, and stop for ship. If no approved plan exists, runs /spec first. Don't use for trivial changes (<25 LOC); edit directly.
Behavioral verification gate: run the test suite, then drive the running software as a real user (CLI/HTTP by default; browser or computer-use if those MCP tools are available) to confirm a feature works end to end. Reports PASS/FAIL per scenario with evidence. Use after a build, before ship, or as /craft's behavioral gate alongside /vet. Don't use for static code review (that is /vet).
Stage and commit code changes with Conventional Commits format. Use when: code changes are complete and ready to commit, after review approval, user says 'save', 'commit', 'ship it'. Don't use when: tests are failing or work is still in progress.
Scan a codebase for accumulated slop, technical debt, dead code, and refactor opportunities. Use when user says 'scan for slop', 'find tech debt', 'what needs cleanup', or before a refactor sprint.
Plan a non-trivial change BEFORE any code: research the context, decompose into testable subtasks, lock signatures, note CWE invariants, write executable acceptance, and surface contradictions. Produces an approvable plan artifact and STOPS for review. Does not write code. Pairs with /craft, which executes the plan. Don't use for trivial changes (<25 LOC) or pure conversation.