ワンクリックで
brewdoc-guide
Interactive guide and tutorial for brewcode plugin suite. Triggers - guide, tutorial, getting started, learn brewcode.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Interactive guide and tutorial for brewcode plugin suite. Triggers - guide, tutorial, getting started, learn brewcode.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Optimizes text/docs for LLM token efficiency. Triggers - optimize, reduce tokens, compress, deep compress.
Optimizes text, prompts, and documentation for LLM token efficiency. Applies 52 research-backed rules across 8 categories: Claude behavior, token efficiency, structure, deduplication, reference integrity, perception, LLM comprehension, and aggressive lossy (deep only). Use when optimizing prompts, reducing tokens, compressing verbose docs, or improving LLM instruction quality.
Generator: deploys a file-based Kanban into ANY repo via multi-agent analysis, with an optional gated CLAUDE.md-optimization pass. Triggers: init task board, scaffold kanban, set up task tracker, generate task board, optimize CLAUDE.md, добавь канбан-доску, разверни трекер задач.
Creates and improves Codex subagents. Triggers: create agent, improve agent, scaffold agent, fix agent.
Extracts etalon classes, patterns, architecture into convention docs. Triggers: extract conventions, etalon classes.
Maintains project .codex/rules and the AGENTS.md rule index. Explicit user invocation only.
| name | brewdoc:guide |
| description | Interactive guide and tutorial for brewcode plugin suite. Triggers - guide, tutorial, getting started, learn brewcode. |
| user-invocable | true |
| disable-model-invocation | true |
| argument-hint | [topic] — no args = interactive menu. Topics: overview, installation, killer-flow, teams, skills-catalog, agents-catalog, customization, integration, advanced |
| allowed-tools | Read, Glob, Grep, Bash, WebSearch, AskUserQuestion |
| model | haiku |
Interactive teaching skill for the brewcode/brewdoc/brewtools/brewui plugin suite.
Read-only — never modifies user project files. Only writes progress JSON.
| ID | Topic | Reference File |
|---|---|---|
overview | Four Plugins Overview | topic-overview.md |
installation | Installation & Updates | topic-installation.md |
killer-flow | Spec → Plan → Start | topic-killer-flow.md |
teams | Dynamic Teams | topic-teams.md |
skills-catalog | All Skills Catalog | topic-skills-catalog.md |
agents-catalog | All Agents Catalog | topic-agents-catalog.md |
customization | Build Your Own | topic-customization.md |
integration | Project Configuration | topic-integration.md |
advanced | Power Features | topic-advanced.md |
EXECUTE using Bash tool:
bash "${CLAUDE_SKILL_DIR}/scripts/validate.sh" 2>/dev/null || echo "VALIDATE_SKIP"
If output is VALIDATE_SKIP — skip silently, continue to Phase 0.5.
Otherwise — show the health table to the user as-is.
Before teaching anything, make sure the user's plugin suite is current.
Invoke the brewtools:plugin-update skill with the check argument. This runs in non-interactive status mode — no prompts, no side effects, just a report of installed vs available versions for brewcode, brewdoc, brewtools, brewui.
Use the Skill tool if available:
Skill(skill="brewtools:plugin-update", args="check")
Otherwise instruct the main conversation to run /brewtools:plugin-update check and capture the result.
Parse the check output. A plugin is stale if:
If all four plugins are current → skip to Phase 1 silently.
If any plugin is stale or missing:
AskUserQuestion:
question: "Some brewcode plugins are outdated or missing. Update now before continuing the guide?"
options:
- "Update now"
- "Show me later"
- "Skip"
Handle the response:
Update now → invoke the skill again with the update argument:
Skill(skill="brewtools:plugin-update", args="update")
When it finishes, continue to Phase 1. Note that a Claude Code restart or /reload-plugins may be required before the new versions take effect.
Show me later → remember this (set an internal flag remind_update = true). Continue to Phase 1. At the end of the guide (Phase 4, final completion message), remind the user that plugins are still out of date and show the /brewtools:plugin-update command.
Skip → continue to Phase 1 without reminder.
EXECUTE using Bash tool:
bash "${CLAUDE_SKILL_DIR}/scripts/progress.sh" read
Store the JSON result as $PROGRESS.
If $PROGRESS.lang is empty:
AskUserQuestion:
question: "Which language do you prefer for the guide?"
options:
- "English"
- "Русский"
- "Português"
Map selection: English → en, Русский → ru, Português → pt.
EXECUTE using Bash tool:
bash "${CLAUDE_SKILL_DIR}/scripts/progress.sh" lang "<selected_code>"
If $PROGRESS.completed is non-empty array — greet:
Welcome back! You've completed X/9 topics.
Last session: {$PROGRESS.last_topic} on {$PROGRESS.last_ts}.
$ARGUMENTS is non-empty:$ARGUMENTS against Topic Map IDs (exact or fuzzy):
killer-flow, "agent" → agents-catalog) → go to Phase 3$ARGUMENTS is empty (Phase 2b — Menu):Read welcome template: ${CLAUDE_SKILL_DIR}/references/welcome.md
Build menu — replace {status} markers with:
✅ if topic ID is in $PROGRESS.completed⬜ if notShow the welcome banner + menu
Determine recommended next topic:
overview (topic 1)killer-flowagents-catalogAskUserQuestion:
question: "Recommended next: {topic_name}. Choose a topic or follow the recommendation:"
options:
- "Follow recommendation"
- "1 — Four Plugins Overview"
- "2 — Installation & Updates"
- "3 — Spec → Plan → Start"
- "4 — Dynamic Teams"
- "5 — Skills Catalog"
- "6 — Agents Catalog"
- "7 — Build Your Own"
- "8 — Project Configuration"
- "9 — Power Features"
- "Exit guide"
If "Exit guide" → stop with farewell message. Otherwise → map selection number to topic ID, go to Phase 3.
${CLAUDE_SKILL_DIR}/references/topic-{TOPIC_ID}.md${CLAUDE_SKILL_DIR}/references/ascii-diagrams.mdThe reference file has 3-4 sections (marked by ### Section N:). For each section:
Present the section content to the user
$PROGRESS.lang) — translate content if not enAfter each section, ask:
AskUserQuestion (for non-last sections):
question: "What would you like to do?"
options:
- "Continue to next section"
- "Show me an example"
- "Go deeper"
- "Skip to next topic"
- "Back to menu"
- "Exit guide"
AskUserQuestion (for the last section):
question: "You've finished this topic! What next?"
options:
- "Show me an example"
- "Go deeper"
- "Next topic"
- "Back to menu"
- "Exit guide"
Handle responses:
.claude/ structure). Base examples only on loaded reference files and project state.After "Next topic" or "Exit guide" from last section → go to Phase 4
EXECUTE using Bash tool:
bash "${CLAUDE_SKILL_DIR}/scripts/progress.sh" complete "{TOPIC_ID}"
Reload progress: EXECUTE using Bash tool:
bash "${CLAUDE_SKILL_DIR}/scripts/progress.sh" status
Show completion status to user
If all 9 topics completed:
Congratulations! You've completed the full guide.
You now know everything about the brewcode plugin suite.
Useful next steps:
- Index your project with /brewcode:grepai
- Create a team with /brewcode:teams create
- Start a task with /brewcode:spec "your task description"
Stop.
Otherwise — recommend next incomplete topic:
AskUserQuestion:
question: "Continue to the next topic?"
options:
- "Yes — {next_topic_name}"
- "Back to menu"
- "Exit guide"
When $PROGRESS.lang is not en: