← ClaudeAtlas

my-claudelisted

Document your Claude Code installation - setup, architecture, web research. Triggers - my claude, installation docs.
kochetkov-ma/claude-brewcode · ★ 31 · AI & Automation · score 78
Install: claude install-skill kochetkov-ma/claude-brewcode
# My Claude Generates documentation about your Claude Code installation and environment. ## Mode Detection Detect mode from `$ARGUMENTS`: | `$ARGUMENTS` value | Mode | Sub-mode | |---|---|---| | empty | INTERNAL | — | | `ext` or `external` (alone) | EXTERNAL | default | | `ext context` or `external context` | EXTERNAL | context-schema | | starts with `r ` or `research ` | RESEARCH | query = rest of args | After detection, load the appropriate reference file: - INTERNAL: `references/internal-mode.md` - EXTERNAL: `references/external-mode.md` - RESEARCH: `references/research-mode.md` ## vs built-in `/team-onboarding` Built-in `/team-onboarding` (CC 2.1.101+) is enough for a quick teammate handoff doc from local config. Use this skill instead when the job needs web research, EXTERNAL architecture synthesis, RESEARCH mode, or the persistent `.claude/brewdoc/INDEX.jsonl` with citations. ## Delegation A big task handed to one agent = an agent gone for an hour: you cannot observe it, cannot correct it, and it usually drifts off-target. One subagent = ONE bounded unit — one source group, ~<=5 files, ~<=10 steps. Bigger MUST be split into N tasks, all spawned in ONE message. Every spawn prompt MUST carry: | Field | Content | |-------|---------| | GOAL | the overall task and why it exists — the point beyond the file edit | | ROLE | what this agent owns; what it must NOT touch | | SCOPE | exact paths/commands in bounds + explicit out-of-bounds | | CONTEXT | what is already do