メニュー
[Documentation] Use when you need initialize, update, or refactor CLAUDE markdown from project-config JSON and codebase scan results.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/duc01226/EasyPlatform --skill claude-md-initコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
[Architecture] Use when designing solution architecture across backend, frontend, deployment, monitoring, testing, and code quality.
[Utilities] Use when you need to answer technical and architectural questions.
[Content] Use when you need to brainstorm as a PO/BA — structured ideation for problem-solving, new product creation, or feature enhancement.
| name | claude-md-init |
| version | 1.0.0 |
| description | [Documentation] Use when you need initialize, update, or refactor CLAUDE markdown from project-config JSON and codebase scan results. |
Goal: Automate CLAUDE.md lifecycle — generate from project-config.json + template, incrementally update marked sections, or refactor for token efficiency.
Workflow:
--mode init), update (--mode update), refactor (--mode refactor)node .claude/skills/claude-md-init/scripts/generate-claude-md.cjs --mode <mode>/sync-codex to regenerate the stale AGENTS.md + Codex mirror surfaces from the new CLAUDE.mdKey Rules:
docs/project-config.json<!-- SECTION:key -->) enable incremental updates without overwriting user contentThis skill is the AI-runnable route the agent-files bootstrap gate offers when a portable
.claude install lands in a project without a root CLAUDE.md — or with one that carries only
project-specific knowledge and is missing the universal portable guides. A single hook detects the gap
and routes here (shared detection lib: .claude/hooks/lib/agent-files-state.cjs):
init-prompt-gate.cjs (UserPromptSubmit) — blocks the first prompt once project-config.json
is populated but CLAUDE.md / AGENTS.md is missing or incomplete. This UserPromptSubmit
gate is the sole agent-files bootstrap router.Three-state detection per root file: missing → routes to --mode init (fresh from template);
incomplete → routes to --mode update (smart-merge — preserves your project content, injects the
guides); ok → no block. Completeness is decided by hasUniversalGuides(): a current-or-newer
sentinel (<!-- CK:UNIVERSAL-GUIDES v1 -->) → complete; an older sentinel → flag for update; no
sentinel → fall back to scanning required anchors (First Action Decision, Workflow Step Advancement,
Task Planning Rules, Code Responsibility Hierarchy, Evidence-Based Reasoning) so legacy/hand-written
complete files still pass.
Run /claude-md-init (or the generator directly) to produce CLAUDE.md from
docs/project-config.json + template. The generated file ships the universal session-start guides
(workflow ask-confirm gate, workflow step-advancement + parallel-phase barrier, task-planning rules,
code hierarchy, naming, evidence/confidence rules) and stamps the sentinel at the top so the gate
recognizes it as complete. It also stamps the hook-independent Workflow-First Gate (from
.claude/skills/shared/workflow-first-gate.md, via stampHeader()) immediately after the sentinel —
the primacy-anchor routing rule (bug→workflow-bugfix workflow, feature/enhancement→workflow-feature workflow) that
mirrors into AGENTS.md and survives with no hooks.
Opt-out — to keep a project-only CLAUDE.md/AGENTS.md (your custom knowledge, none of the
universal guides), set portability.requireUniversalGuides: false in docs/project-config.json
(persistent; default true). The gate then checks only existence, never completeness. The transient
skip init escape still dismisses both hooks for 24h. The gate is dormant in empty/greenfield folders
and before config is populated. AGENTS.md is generated separately by /sync-codex (user-invoke-only).
| Mode | When | Behavior |
|---|---|---|
init | No CLAUDE.md exists, or first-time setup | Generate fresh CLAUDE.md from template + config. Populates all markers. |
update | CLAUDE.md exists with markers | Replace only content between markers. Preserve everything else. |
refactor | CLAUDE.md exists, needs optimization | AI reads entire CLAUDE.md, optimizes for token efficiency, removes redundancy, improves structure. No script — pure AI. |
docs/project-config.json — primary data source (run /project-config first if missing)# Check CLAUDE.md state
node .claude/skills/claude-md-init/scripts/generate-claude-md.cjs --detect
Decision logic:
initupdatesmart-merge (see below)--mode flag → override detection# Init mode: generate fresh CLAUDE.md
node .claude/skills/claude-md-init/scripts/generate-claude-md.cjs --mode init
# Update mode: sync marked sections only
node .claude/skills/claude-md-init/scripts/generate-claude-md.cjs --mode update
Script behavior:
docs/project-config.jsonreferences/claude-md-template.md) for init, or existing CLAUDE.md for updateCLAUDE.md (creates backup .claude-md.backup first)When running update on an existing CLAUDE.md that has NO section markers:
## heading text against known section keys (see references/section-registry.md)After the script generates the mechanical parts, AI reviews and fills:
contextGroups[].rules in config, but rewrite as human-readable rulesmodules[] + framework config, add project-specific patterns{project-name}, TODO).claude/skills/claude-md-init/ references leak into output (self-reference)Writing/updating CLAUDE.md leaves the generated mirror surfaces stale — AGENTS.md (Codex), the
.codex/ mirrors, and other downstream surfaces are derived FROM CLAUDE.md and
do not update on their own.
MUST add a final todo task — "Sync Codex mirrors from updated CLAUDE.md" — and run it after
init/update/refactor completes, by invoking the /sync-codex skill (the full cross-surface
migrate → hooks → context → verify pipeline, which regenerates AGENTS.md). Create this as
the LAST TaskCreate item so it always follows the verify step:
TaskCreate: "Sync Codex mirrors from updated CLAUDE.md → invoke /sync-codex"
Skip only when no CLAUDE.md content actually changed (e.g. generator reported all sections preserved / no diff). Otherwise the AGENTS.md mirror drifts from CLAUDE.md and Codex runs against stale guidance.
When --mode refactor or user asks to optimize CLAUDE.md:
<!-- SECTION:tldr -->
Auto-generated content here...
<!-- /SECTION:tldr -->
Rules:
See references/section-registry.md for full mapping. Summary:
| Key | Source | Conditional? |
|---|---|---|
tldr | project.*, modules[], framework.* | No — always generated |
golden-rules | contextGroups[].rules | Yes — skip if no rules |
decision-quick-ref | modules[], framework.* | Yes — skip if no modules |
key-locations | modules[].pathRegex | Yes — skip if no modules |
dev-commands | testing.commands, infrastructure.* | Yes — skip if no commands |
infra-ports | modules[].meta.port (infra) | Yes — skip if no ports |
api-ports | modules[].meta.port (services) | Yes — skip if no ports |
integration-testing | framework.integrationTestDoc | Yes — skip if no doc |
e2e-testing | framework.e2eTestDoc or scan | Yes — skip if no tests |
doc-index | Scan docs/ directory | Yes — skip if no docs/ |
doc-lookup | modules[] + business features | Yes — skip if no modules |
Generator + bootstrap-gate coverage lives in the hooks test suite:
node .claude/hooks/tests/run-all-tests.cjs --filter=agent-files
[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.
Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.
Output Quality — Token efficiency without sacrificing quality.
- No inventories/counts — AI can
grep | wc -l. Counts go stale instantly- No directory trees — AI can
glob/ls. Use 1-line path conventions- No TOCs — AI reads linearly. TOC wastes tokens
- No examples that repeat what rules say — one example only if non-obvious
- Lead with answer, not reasoning. Skip filler words and preamble
- Sacrifice grammar for concision in reports
- Unresolved questions at end, if any
AI Mistake Prevention — Failure modes to avoid on every task:
Re-read files after context changes. Context compaction, resume, or long-running work can make memory stale; verify current files before acting. Verify generated content against source evidence. AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing. Check downstream references before deleting or renaming. Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first. Trace the full impact chain after edits. Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done. Verify ALL affected outputs, not just the first. One green check is not all green checks; validate every output surface the change can affect. Assume existing values are intentional — ask WHY before changing. Before changing a constant, limit, flag, wording, or pattern, read nearby context and history. Surface ambiguity before acting — don't pick silently. Multiple valid interpretations require an explicit question or stated assumption with risk. Keep shared guidance role-relevant. Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols.
IMPORTANT MUST ATTENTION maintain >=8 rules per 100 lines. Critical rules in first+last 5 lines. Tables over prose.
MUST ATTENTION apply critical + sequential thinking — every claim needs appropriate traced evidence (file:line for repo/code claims; source URL or artifact section for research, product, content, and docs claims); confidence >80% to act, <60% DO NOT recommend. Anti-hallucination: never present guess as fact, admit uncertainty freely, cross-reference independently, stay skeptical of own confidence.
MUST ATTENTION apply AI mistake prevention — verify generated content against evidence, trace downstream references before deleting or renaming, verify all affected outputs, re-read files after context loss, and surface ambiguity before acting.
Protocols in force (concise digest of the SYNC/shared blocks this skill carries): MUST ATTENTION honor every protocol below.
IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
IMPORTANT MUST ATTENTION add a final review todo task to verify work quality
[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.