gilles/claude-code-best-practice
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated

Browse Source
This commit is contained in:
Shayan Rais
2026-04-17 21:39:53 +05:00
parent 72f8aaff9e
commit db0efc8142
6 changed files with 939 additions and 588 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/rules/presentation.md
+13 -3
View File
@@ -2,12 +2,22 @@
## Delegation Rule
Any request to update, modify, or fix the presentation (`presentation/index.html`) MUST be handled by the `presentation-curator` agent. Always delegate presentation work to this agent via the Task tool — never edit the presentation directly.
Any request to update, modify, or fix a presentation MUST be handled by the matching per-presentation agent. **Never edit presentation HTML directly.** Route by which presentation the user is referring to:
| Presentation | Path | Agent |
|---|---|---|
| Vibe Coding → Agentic Engineering | `presentation/vibe-coding-to-agentic-engineering/index.html` | `presentation-vibe-coding` |
| Claude Code Learning Journey | `presentation/learning-journey/index.html` | `presentation-learning-journey` |
Invoke via the Agent tool:
```
Task(subagent_type="presentation-curator", description="...", prompt="...")
Agent(subagent_type="presentation-vibe-coding", description="...", prompt="...")
Agent(subagent_type="presentation-learning-journey", description="...", prompt="...")
```
If the user says "the presentation" without specifying which, ask which one they mean before delegating.
## Why
The presentation-curator agent has three preloaded skills that keep it in sync with the presentation's structure, styling, and conceptual framework. It also self-evolves after every execution, updating its own skills to prevent knowledge drift. Bypassing the agent risks breaking slide numbering, level transitions, or style consistency.
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 learning-journey agent targets a non-technical audience and uses its own 6-level (2-day) system.