codemap-claudemd
Use to generate or refresh a layered CLAUDE.md hierarchy (lean root + per-subdir) for a large codebase. "Set up CLAUDE.md files", "scaffold context files", "make this repo legible to Claude Code", "add directory-scoped conventions".
What this skill does
# codemap-claudemd Emit the layered CLAUDE.md hierarchy the Claude Code large-codebase playbook recommends. Reuses the `/codemap` walk; the output is CLAUDE.md files (loaded every session, additively as Claude traverses the tree), not standalone docs. ## Variants in the codemap family - **codemap** — full evidence-based map (standalone markdown) - **codemap-fast** — quick structural scan - **codemap-claudemd** (this skill) — emit the map AS a CLAUDE.md hierarchy ## Method 1. **Survey.** Run the `codemap` walk (or `codemap-fast` on a huge repo) to get modules, responsibilities, dependencies, and the per-directory build/test/lint commands. 2. **Root `CLAUDE.md` — keep it lean.** One-paragraph repo purpose, the highest-level structure, critical gotchas, and pointers to the subdirectory files. This is loaded every session, so resist detail (article: *"root contains pointers and critical gotchas only"*). If a SiftCoder `ARCHITECTURE.md` or design contract exists, point to it rather than duplicating it. 3. **Per-significant-subdir `CLAUDE.md`.** One file per service/module boundary (not per technical layer). Include: local conventions, the scoped test/build/lint command for that directory (so Claude runs the dir suite, not the whole monorepo), and module-specific gotchas. 4. **Idempotent merge.** If a CLAUDE.md already exists, diff the generated content against it and propose additions only. Never clobber hand-written guidance. 5. **Show every proposed file/diff. Write only on approval.** ## Choosing which subdirs get a file - Has its own build/test/lint command → yes. - Distinct domain or ownership → yes. - Non-obvious conventions a newcomer would trip on → yes. - Pure leaf with nothing local to say → skip (don't dilute with empty files). ## Output discipline - Root stays short; detail lives in subdir files. Hundreds-of-folders monorepos need hierarchy, not one giant root file. - Phrase conventions as durable, imperative rules — not a narration of recent work. - Pairs with `/siftcoder:knowledge` (folds session conventions into the right CLAUDE.md) and the Stop-hook convention hint. ## Value over native CC `/init` writes a single root CLAUDE.md. This skill produces the *layered* hierarchy large codebases need, scoped per module with per-directory commands, and merges into existing files instead of overwriting.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.