add presentation-claude-code agent to delegation routing table
Updates the per-presentation delegation rule to route requests on the new "Claude Code Best Practice" deck to the new presentation-claude-code agent. Previously the table had only two decks (vibe-coding, claude-gemini); now all three are listed with explicit path → agent mapping and an invocation example. Adds clarification that "the main presentation" or "the best-practice deck" generally refers to the new claude-code agent. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -12,17 +12,19 @@ Any request to update, modify, or fix a presentation MUST be handled by the matc
|
||||
| Presentation | Path | Agent |
|
||||
|---|---|---|
|
||||
| Vibe Coding → Agentic Engineering | `presentation/vibe-coding-to-agentic-engineering/index.html` | `presentation-vibe-coding` |
|
||||
| Claude Code & Gemini CLI | `presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html` | `presentation-claude-gemini` |
|
||||
| Claude Code & Gemini CLI (GDG Kolachi event deck) | `presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html` | `presentation-claude-gemini` |
|
||||
| Claude Code Best Practice (canonical reusable deck) | `presentation/claude-code-best-practice/index.html` | `presentation-claude-code` |
|
||||
|
||||
Invoke via the Agent tool:
|
||||
|
||||
```
|
||||
Agent(subagent_type="presentation-vibe-coding", description="...", prompt="...")
|
||||
Agent(subagent_type="presentation-claude-gemini", description="...", prompt="...")
|
||||
Agent(subagent_type="presentation-claude-code", description="...", prompt="...")
|
||||
```
|
||||
|
||||
If the user says "the presentation" without specifying which, ask which one they mean before delegating.
|
||||
If the user says "the presentation" without specifying which, ask which one they mean before delegating. Note that "the main presentation" or "the best-practice deck" generally refers to `presentation-claude-code` — the canonical reusable deck — but confirm if ambiguous.
|
||||
|
||||
## Why
|
||||
|
||||
Each presentation has its own slide numbering, level system, journey-bar tick labels, and target audience. Per-presentation agents let each one keep a focused knowledge base and self-evolve without cross-contaminating the other. The vibe-coding agent preloads framework/structure/styling skills specific to that deck; the claude-gemini agent targets a non-technical audience and uses its own 6-level (2-day) system.
|
||||
Each presentation has its own slide numbering, level system, and target audience. Per-presentation agents let each one keep a focused knowledge base and self-evolve without cross-contaminating the others. The vibe-coding agent preloads framework/structure/styling skills specific to that deck. The claude-gemini agent targets a non-technical GDG event audience and uses a journey-bar with 6 levels. The claude-code agent owns the canonical reusable best-practices deck (forked from the GDG one on 2026-04-30) — same audience voice, simpler structure (level-badge only, no journey bar), event-agnostic identity.
|
||||
|
||||
Reference in New Issue
Block a user