skills added
This commit is contained in:
Shayan Rais
@@ -173,7 +173,9 @@ After completing changes, report to the user:
|
||||
- **2026-04-22 global dual-mascot pattern (Claude top-left, Gemini top-right)**: the deck now renders two persistent corner mascots on every slide via a pair of fixed-position `<div class="header-logo">` elements just before the `.navigation` block. CSS: `.header-logo` is `position: fixed; top: 20px; left: 40px; width: 100px; height: 65px; z-index: 50` (Claude, top-left). `.header-logo.right` adds `left: auto; right: 40px` to flip it to top-right (Gemini). Assets: `../../!/claude-jumping.svg` and `../../!/gemini-jumping.svg` — both verified present at repo root `!/`. The Gemini jumping mascot pairs with the Claude one for the GDG dual-CLI deck. Per-slide mascot `<img>` tags that were hardcoded on slide 1 (with `position: absolute`) are now deleted — use global divs only. The `style="position: relative;"` that was on the slide 1 wrapper was removed because it only existed to anchor those absolute-positioned per-slide mascots. **z-index safety**: mascots at z-index 50 sit below `.journey-bar` (99) and `.navigation` / `.progress` (100) — no overlap. The journey bar is at `right: 62px; top: 95px`, which is far enough below `top: 20px` that the right mascot and the bar track do not visually collide. **Rule**: for any GDG dual-CLI deck, always use this two-div global pattern rather than per-slide mascots — it guarantees consistent placement across all 40 slides without per-slide maintenance.
|
||||
- **2026-04-24 slide 6 jargon-cloud tier reshuffle**: `vibe coding` demoted from hero-blue to small-orange (top: 91% / left: 22%); `harness` and `compaction` promoted from purple to hero-blue (kept positions, upgraded padding/font/shadow); `context window` added as new hero-blue pill (top: 32% / left: 5%); `context engineering` deleted (pill + legend row both removed). Legend rebalanced: left column = 8 blue + 2 purple (10 rows), right column = 4 green + 5 orange (9 rows) — slight asymmetry because green dropped from 5 to 4 after context-engineering removal; acceptable. Key verification method: Python script extracting all `background: #HEX` pill texts and all `color: #HEX; font-weight: 700` legend texts per color — confirmed exact match for all 4 tiers. Total slides and data-level dividers unchanged (51 / 21,27,33,38,44,47).
|
||||
- **2026-04-24 restore-original + keep-new insert at slot 9 (50 → 51 slides)**: the "Can answer / Can't answer" grid (commit `61a847c`) was restored at slot 9 and the Stochastic Parrots slide (authored in `fa1b499`) was shifted to slot 10. Recovery method: `git show 61a847c:...index.html | sed -n 'LINE,LINEp'` to extract the exact pre-edit markup, then Edit tool to insert it before the current slot-9 comment block, then a Python sentinel-replacement script to renumber old slides 10-50 → 11-51. The sentinel approach is mandatory here because Python `str.replace` applies all substitutions, so descending-order alone is insufficient for a multi-value renumber (unlike sed's single-expression-per-call mode). No `goToSlide` hardcoded calls exist in this deck — only the function definition — so no TOC update was needed. `totalSlides` is DOM-computed, no hardcoded bump. New section-divider positions: **Agents=21, Skills=27, Context=33, CLAUDE.md=38, Commands=44, Workflow=47**. Total slides: **51**. git ref for the original slide 9 content: `61a847c`.
|
||||
- **2026-04-24 insert 4 CLAUDE.md teaching slides at positions 33-36 (59 → 63 slides)**: new slides inserted between slide 32 (CLAUDE.md concept-intro section divider) and old slide 33 (Skills section divider). All four carry `data-level="claude-md"` so the level-badge fires at slide 33 and stays on through the CLAUDE.md arc. New slides: 33 ("Create your first CLAUDE.md — `/init`", mirrors slide-24 agent-creation template with purple accent `#9c27b0`), 34 (screenshot `../assets/concepts/claudemd/claudemd.png`), 35 (tips image `../assets/concepts/claudemd/claudemd-tips.png`), 36 (problem image `../assets/concepts/claudemd/claudemd-problem.png`). All images verified present before writing. Old slides 33-59 shifted to 37-63 using Python sentinel replacement (second-occurrence targeting for 33-36, single-occurrence for 37-59). No `goToSlide` hardcoded calls exist — no TOC update needed. Final section-divider positions: **Agents=23, Skills=39, Context=45, CLAUDE.md=33+50, Commands=56, Workflow=59**. Total slides: **63**. **Redundancy flag on slide 50**: old CLAUDE.md section opener "Topic 4 — The Reporter's Pocket Rulebook" (`data-level="claude-md"`, `section-slide` class) at slide 50 is now downstream of the new teaching slides 33-36 which already fire `→ CLAUDE.md` at slide 33. The badge will NOT re-fire at 50 (same level = no change). The slide is visually a full-screen section divider with a weather-reporter metaphor description — it still serves as a breathing-space divider between the "how to use CLAUDE.md" block (33-36) and the "deep dive" block (51-55). Recommended: keep for now, flag for user to decide whether to promote it into the new cluster or demote to a regular slide. **Dual-CLAUDE.md level pattern**: when a topic has a concept-intro (slide 32 section divider) plus early how-to slides (33-36) plus a deeper narrative arc (50-55), the level fires twice in the deck — at 33 (shallow intro cluster) and again via the section opener at 50 (deep dive). This is working-as-designed for the journey bar. **Double-sentinel rule for same-number collisions**: when inserting N new slides at position P and those new slides use data-slide values P through P+N-1, the old slides at those same values become "second occurrences." Replace second occurrences (not first) with sentinels before resolving — Python `str.find(target, first_pos+1)` pattern is the correct approach.
|
||||
- **2026-04-24 three concept-intro slides inserted at 27-29 (51 → 54 slides)**: new slides 27 (CLAUDE.md), 28 (Skills), 29 (Context) inserted immediately before the old Skills section opener (now at 30). All three use `class="slide section-slide"` with NO `data-level` — they are concept intros, not arc-level openers, so the journey bar should not advance on them. Pill choices: CLAUDE.md uses `CLAUDE.md` as the filename (monospace yellow pill — no slash command exists); Skills uses `.claude/skills/` as the filesystem path (no `/skills` slash command exists — verified against CLAUDE.md which shows skills are file-based, not command-invoked); Context uses `/context` — this IS a real Claude Code command (shows current token usage breakdown). Slide 29 (Context) intentionally has NO file-tree because context is a runtime concept, not a filesystem artifact. Renumber method: sentinel technique with 3-phase Python script — (1) replace all `data-slide="27"` through `"51"` with `##SEN27##` through `##SEN51##`, (2) restore the FIRST occurrence of sentinels 27/28/29 (the new slides) back to their correct values using `str.replace(..., 1)`, (3) resolve remaining sentinels N→N+3. Section-divider positions after insert: **Agents=23, Skills=30, Context=36, CLAUDE.md=41, Commands=47, Workflow=50**. Total slides: **54**.
|
||||
- **2026-04-24 pillar-footer strip added to slides 23-29**: compact 5-card reference bar added below the viewport fold on slides 23-29. Implementation uses Option A: each slide's existing content is wrapped in a `.slide-viewport-content` div (`min-height: 100vh; display: flex; flex-direction: column; align-items: center; justify-content: center; width: 100%`) and a `.pillar-footer` sibling div (flex row, `gap: 10px; justify-content: center; max-width: 1000px; margin: 60px auto 40px auto`) is appended after the wrapper. Each footer contains 5 `.pillar-mini-card` divs (flex row, `padding: 10px 14px`, `border-radius: 8px`, `box-shadow: 0 2px 6px rgba(0,0,0,0.08)`) with emoji + title only — no body text. Active-pillar highlighting is implemented: the current topic's card has `border-left: 5px solid <color>` and no `.inactive` class; the other four have `border-left: 3px solid <color>` and class `pillar-mini-card inactive` (`opacity: 0.45`). Active assignments: slides 23-26 → Agents, slide 27 → CLAUDE.md, slide 28 → Skills, slide 29 → Context. Section-dividers (slides 23, 27, 28, 29) kept `justify-content: center` for `.slide-viewport-content`; content slides (24, 25, 26) use `justify-content: flex-start; padding-top: 60px` on `.slide-viewport-content` to keep the h1 near top. Scroll reset (`window.scrollTo(0, 0)` in `showSlide()`) was already present from a prior session — no JS change needed. The 5 pillar colors exactly match slide 14's card borders: Agents `#009688`, Skills `#4caf50`, Workflows `#ef6c00`, CLAUDE.md `#9c27b0`, Context `#3f51b5`. Total slide count (54) and all data-level positions unchanged. **At 1024px width**: each mini-card is `~18%` of 1000px = ~180px. With `flex: 1` and `min-width: 0`, cards compress gracefully — the 12-char "CLAUDE.md" title at `font-size: 0.82rem` is ~96px, well within 180px. No wrapping expected at standard presentation viewports.
|
||||
- **2026-04-24 content-slide heading centering fix (slides 24/25/26)**: the `.slide-viewport-content` wrapper (`min-height: 100vh; display: flex; align-items: center`) was centering headings vertically even with `justify-content: flex-start` inline override — `align-items: center` acts on the cross-axis (horizontal in a column flex), but the real problem is that the full-viewport-height flex container pushes content away from the top edge. Fix: removed `.slide-viewport-content` entirely from slides 24 and 26 (plain content slides with substantial content), letting them flow exactly like slide 22 — h1 at top, content below, no wrapper at all. Slide 25 (Demo — nearly empty body) uses a plain `<div style="min-height: calc(100vh - 120px);">` spacer wrapping only the h1, so the footer is pushed below the fold without any flex centering. Section-divider slides 23/27/28/29 keep their `.slide-viewport-content` wrapper unchanged — they are supposed to be viewport-centered. **Rule**: for content slides with a pillar-footer, do NOT wrap in `.slide-viewport-content`. Use a bare spacer div only on near-empty content slides (less than ~3 elements of body content) to push the footer below the fold.
|
||||
- **2026-04-24 image-only tips slides inserted at 31 and 32 (57 → 59 slides)**: two new slides inserted after slide 29 (the last agents-section content slide) before slide 30 (the CLAUDE.md section intro). Both slides are plain content slides with `data-level="agents"` so the journey bar stays on the agents level without re-firing. Layout: bare `<h1>` (no wrapper) + flex-centered `<div style="min-height: calc(100vh - 200px);">` containing the `<img>`. The `-200px` calculation (h1 ~100px + pillar-footer ~100px gap) matches slide 26's pattern for full-bleed image slides. Pillar-footer is included with Agents as the active card (matching the active pattern on slides 26-29). Renumber method: Python sentinel script — each `data-slide="N"` for N=31-57 replaced via `##SENTINELN##` intermediates, then resolved to N+2. No `goToSlide` hardcoded calls exist in this deck; `totalSlides` is DOM-computed. Section-divider positions after insertion: **agents=23 (unchanged), skills=35, context=41, claude-md=46, commands=52, workflow=55**. Total slides: **59**. Images at `../assets/concepts/agents/agent-tips-1.png` and `agent-tips-2.png` — both verified present before insertion.
|
||||
- **2026-04-24 Skills emoji updated + 2 new slides inserted at 38-39 (63 → 65 slides)**: Edit 1 — slide 37's h1 emoji changed from `🎓` (graduation cap) to `🎯` (target) to match the Skills pillar-footer card emoji established on slide 14 and used across all 12 pillar footers. Edit 2 — new slide 38 ("Create your first skill", `data-level="skills"`) inserted with a `.two-col` layout: two `.col-card` divs (both green `#4caf50` border-left) for Method 1 (write by prompting) and Method 2 (use Anthropic's `skill-creator`), followed by an inline amber warning box (`background: #fff3e0; border-left: 4px solid #ff9800`) flagging the wrong-structure gotcha of Method 1. Edit 3 — new slide 39 ("Skill config fields with frontmatter", `data-level="skills"`) mirrors slide 29's agent field-table pattern exactly: 8 field rows using `.field-row` / `.field-name` / `.field-desc` / `.field-enforced` / `.pill-harness` / `.pill-prompt` CSS classes, italic intro sentence, and a centered `.fafafa` footnote callout for `description`. Old slides 38-63 renumbered to 40-65 via Python sentinel replacement (descending-order sentinel phase + resolve phase). **Redundancy flag**: old Skills section opener (was slide 39, now slide 41 — `data-level="skills"`, `section-slide` class, "Topic 2 — What the Weather Reporter Knows") is now downstream of the new teaching slides 38-39 which already fire `→ skills` earlier. Same pattern as the CLAUDE.md dual-fire situation at slides 33 and 52. Recommended: keep slide 41 as a breathing-space divider into the weather-reporter narrative arc; the journey bar will not re-fire (same level). Final section-divider positions: **Agents=23, Skills=38 (first skills data-level), Context=47, CLAUDE.md=52, Commands=58, Workflow=61**. Total slides: **65**.
|
||||
|
||||
@@ -1544,14 +1544,207 @@ todoapp/
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Slide 33: Create your first CLAUDE.md — /init -->
|
||||
<div class="slide" data-slide="33" data-level="claude-md">
|
||||
<div style="min-height: calc(100vh - 120px);">
|
||||
<h1>Create your first CLAUDE.md — <code>/init</code></h1>
|
||||
<div style="max-width: 600px;">
|
||||
<div class="col-card" style="border-left: 4px solid #9c27b0;">
|
||||
<div class="how-to-trigger" style="margin: 16px 0 12px 0;">
|
||||
<h4>The Command</h4>
|
||||
<p>Type <code>/init</code> in Claude Code.</p>
|
||||
</div>
|
||||
<p style="font-size: 1rem; color: #444;">Claude scans your codebase and drafts a starter CLAUDE.md for you — project conventions, key patterns, common commands.</p>
|
||||
<p style="margin-top: 12px; font-size: 0.9rem; color: #666;">Creates <code>CLAUDE.md</code> in your repo root — a plain markdown file you edit and commit.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="pillar-footer">
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #009688;">
|
||||
<span class="pmc-emoji">🧑‍💼</span>
|
||||
<span class="pmc-title">Agents</span>
|
||||
<span class="pmc-subtitle">— the specialists</span>
|
||||
<span class="pmc-body">A dedicated Claude worker — own context, own tools, own focus. Each runs in isolation.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ fresh working memory per run</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card" style="border-left: 4px solid #9c27b0;">
|
||||
<span class="pmc-emoji">📝</span>
|
||||
<span class="pmc-title">CLAUDE.md</span>
|
||||
<span class="pmc-subtitle">— your memory</span>
|
||||
<span class="pmc-body">Knowledge <em>you</em> provide to the model. Read every session. Keep it under 200 lines.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ 200-line problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #4caf50;">
|
||||
<span class="pmc-emoji">🎯</span>
|
||||
<span class="pmc-title">Skills</span>
|
||||
<span class="pmc-subtitle">— the know-how</span>
|
||||
<span class="pmc-body">What the specialist (or Claude) can actually do. Loaded on demand — only when needed.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ progressive disclosure</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #3f51b5;">
|
||||
<span class="pmc-emoji">💭</span>
|
||||
<span class="pmc-title">Context</span>
|
||||
<span class="pmc-subtitle">— the working memory</span>
|
||||
<span class="pmc-body">What Claude holds in his head now — fresh every new chat. Finite budget; compact at ~50%.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ dumb-zone problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #ef6c00;">
|
||||
<span class="pmc-emoji">📘</span>
|
||||
<span class="pmc-title">Workflows</span>
|
||||
<span class="pmc-subtitle">— the instruction manual</span>
|
||||
<span class="pmc-body">Repeatable step-by-step recipes — like an AC install guide. Deterministic, reproducible.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ reproducible recipes</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Slide 34: CLAUDE.md — the real thing (screenshot) -->
|
||||
<div class="slide" data-slide="34" data-level="claude-md">
|
||||
<div style="min-height: calc(100vh - 120px);">
|
||||
<h1>📝 CLAUDE.md — the real thing</h1>
|
||||
<div style="display: flex; align-items: center; justify-content: center;">
|
||||
<img src="../assets/concepts/claudemd/claudemd.png" alt="A real CLAUDE.md file showing project rules and agent invocation instructions" style="max-width: 1200px; max-height: 80vh; width: auto; height: auto; display: block; margin: 20px auto 0 auto; border-radius: 8px; box-shadow: 0 4px 16px rgba(0,0,0,0.1); object-fit: contain;" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="pillar-footer">
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #009688;">
|
||||
<span class="pmc-emoji">🧑‍💼</span>
|
||||
<span class="pmc-title">Agents</span>
|
||||
<span class="pmc-subtitle">— the specialists</span>
|
||||
<span class="pmc-body">A dedicated Claude worker — own context, own tools, own focus. Each runs in isolation.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ fresh working memory per run</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card" style="border-left: 4px solid #9c27b0;">
|
||||
<span class="pmc-emoji">📝</span>
|
||||
<span class="pmc-title">CLAUDE.md</span>
|
||||
<span class="pmc-subtitle">— your memory</span>
|
||||
<span class="pmc-body">Knowledge <em>you</em> provide to the model. Read every session. Keep it under 200 lines.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ 200-line problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #4caf50;">
|
||||
<span class="pmc-emoji">🎯</span>
|
||||
<span class="pmc-title">Skills</span>
|
||||
<span class="pmc-subtitle">— the know-how</span>
|
||||
<span class="pmc-body">What the specialist (or Claude) can actually do. Loaded on demand — only when needed.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ progressive disclosure</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #3f51b5;">
|
||||
<span class="pmc-emoji">💭</span>
|
||||
<span class="pmc-title">Context</span>
|
||||
<span class="pmc-subtitle">— the working memory</span>
|
||||
<span class="pmc-body">What Claude holds in his head now — fresh every new chat. Finite budget; compact at ~50%.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ dumb-zone problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #ef6c00;">
|
||||
<span class="pmc-emoji">📘</span>
|
||||
<span class="pmc-title">Workflows</span>
|
||||
<span class="pmc-subtitle">— the instruction manual</span>
|
||||
<span class="pmc-body">Repeatable step-by-step recipes — like an AC install guide. Deterministic, reproducible.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ reproducible recipes</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Slide 35: claude-code-best-practice Tips & Tricks (CLAUDE.md) -->
|
||||
<div class="slide" data-slide="35" data-level="claude-md">
|
||||
<h1><code>claude-code-best-practice</code> Tips & Tricks</h1>
|
||||
<div style="min-height: calc(100vh - 200px); display: flex; align-items: center; justify-content: center;">
|
||||
<img src="../assets/concepts/claudemd/claudemd-tips.png" alt="Claude Code tips and tricks for CLAUDE.md" style="max-width: 1200px; max-height: 80vh; width: auto; height: auto; display: block; margin: 20px auto 0 auto; border-radius: 8px; box-shadow: 0 4px 16px rgba(0,0,0,0.1); object-fit: contain;" />
|
||||
</div>
|
||||
<div class="pillar-footer">
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #009688;">
|
||||
<span class="pmc-emoji">🧑‍💼</span>
|
||||
<span class="pmc-title">Agents</span>
|
||||
<span class="pmc-subtitle">— the specialists</span>
|
||||
<span class="pmc-body">A dedicated Claude worker — own context, own tools, own focus. Each runs in isolation.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ fresh working memory per run</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card" style="border-left: 4px solid #9c27b0;">
|
||||
<span class="pmc-emoji">📝</span>
|
||||
<span class="pmc-title">CLAUDE.md</span>
|
||||
<span class="pmc-subtitle">— your memory</span>
|
||||
<span class="pmc-body">Knowledge <em>you</em> provide to the model. Read every session. Keep it under 200 lines.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ 200-line problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #4caf50;">
|
||||
<span class="pmc-emoji">🎯</span>
|
||||
<span class="pmc-title">Skills</span>
|
||||
<span class="pmc-subtitle">— the know-how</span>
|
||||
<span class="pmc-body">What the specialist (or Claude) can actually do. Loaded on demand — only when needed.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ progressive disclosure</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #3f51b5;">
|
||||
<span class="pmc-emoji">💭</span>
|
||||
<span class="pmc-title">Context</span>
|
||||
<span class="pmc-subtitle">— the working memory</span>
|
||||
<span class="pmc-body">What Claude holds in his head now — fresh every new chat. Finite budget; compact at ~50%.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ dumb-zone problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #ef6c00;">
|
||||
<span class="pmc-emoji">📘</span>
|
||||
<span class="pmc-title">Workflows</span>
|
||||
<span class="pmc-subtitle">— the instruction manual</span>
|
||||
<span class="pmc-body">Repeatable step-by-step recipes — like an AC install guide. Deterministic, reproducible.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ reproducible recipes</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Slide 36: CLAUDE.md problem — keep it under 200 lines -->
|
||||
<div class="slide" data-slide="36" data-level="claude-md">
|
||||
<div style="min-height: calc(100vh - 120px);">
|
||||
<h1>⚠️ CLAUDE.md problem — keep it under 200 lines</h1>
|
||||
<div style="min-height: calc(100vh - 200px); display: flex; align-items: center; justify-content: center;">
|
||||
<img src="../assets/concepts/claudemd/claudemd-problem.png" alt="Illustration of the CLAUDE.md 200-line adherence problem" style="max-width: 1200px; max-height: 80vh; width: auto; height: auto; display: block; margin: 20px auto 0 auto; border-radius: 8px; box-shadow: 0 4px 16px rgba(0,0,0,0.1); object-fit: contain;" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="pillar-footer">
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #009688;">
|
||||
<span class="pmc-emoji">🧑‍💼</span>
|
||||
<span class="pmc-title">Agents</span>
|
||||
<span class="pmc-subtitle">— the specialists</span>
|
||||
<span class="pmc-body">A dedicated Claude worker — own context, own tools, own focus. Each runs in isolation.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ fresh working memory per run</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card" style="border-left: 4px solid #9c27b0;">
|
||||
<span class="pmc-emoji">📝</span>
|
||||
<span class="pmc-title">CLAUDE.md</span>
|
||||
<span class="pmc-subtitle">— your memory</span>
|
||||
<span class="pmc-body">Knowledge <em>you</em> provide to the model. Read every session. Keep it under 200 lines.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ 200-line problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #4caf50;">
|
||||
<span class="pmc-emoji">🎯</span>
|
||||
<span class="pmc-title">Skills</span>
|
||||
<span class="pmc-subtitle">— the know-how</span>
|
||||
<span class="pmc-body">What the specialist (or Claude) can actually do. Loaded on demand — only when needed.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ progressive disclosure</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #3f51b5;">
|
||||
<span class="pmc-emoji">💭</span>
|
||||
<span class="pmc-title">Context</span>
|
||||
<span class="pmc-subtitle">— the working memory</span>
|
||||
<span class="pmc-body">What Claude holds in his head now — fresh every new chat. Finite budget; compact at ~50%.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ dumb-zone problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #ef6c00;">
|
||||
<span class="pmc-emoji">📘</span>
|
||||
<span class="pmc-title">Workflows</span>
|
||||
<span class="pmc-subtitle">— the instruction manual</span>
|
||||
<span class="pmc-body">Repeatable step-by-step recipes — like an AC install guide. Deterministic, reproducible.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ reproducible recipes</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- ============================================================ -->
|
||||
<!-- NEW SLIDE 28: Skills concept intro -->
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide: Skills -->
|
||||
<div class="slide section-slide" data-slide="33">
|
||||
<div class="slide section-slide" data-slide="37">
|
||||
<div class="slide-viewport-content">
|
||||
<h1>🎓 Skills</h1>
|
||||
<h1>🎯 Skills</h1>
|
||||
<div style="text-align: center; margin: 12px auto 20px auto;">
|
||||
<span style="background: #fff3cd; color: #7a5c00; padding: 8px 20px; border-radius: 999px; font-size: 1rem; font-weight: 600; white-space: nowrap; font-family: 'SF Mono', Monaco, 'Courier New', monospace; box-shadow: 0 2px 8px rgba(122,92,0,0.18);">.claude/skills/</span>
|
||||
</div>
|
||||
@@ -1606,12 +1799,169 @@ todoapp/
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- ============================================================ -->
|
||||
<!-- NEW SLIDE 38: Create your first skill -->
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<div class="slide" data-slide="38" data-level="skills">
|
||||
<div style="min-height: calc(100vh - 120px);">
|
||||
<h1>Create your first skill</h1>
|
||||
<div class="two-col" style="margin-top: 28px;">
|
||||
<div class="col-card" style="border-left: 4px solid #4caf50;">
|
||||
<h4>Write it by prompting</h4>
|
||||
<p>Just describe what you want Claude to do. It drafts the skill file for you.</p>
|
||||
<p style="font-size: 0.92rem; color: #555; margin-top: 12px; font-style: italic;">"Create a skill that fetches weather from Open-Meteo for a given city."</p>
|
||||
</div>
|
||||
<div class="col-card" style="border-left: 4px solid #4caf50;">
|
||||
<h4>Use Anthropic's skill-creator</h4>
|
||||
<p>Anthropic ships an official <code>skill-creator</code> skill. Invoke it and it walks you through generating a properly-structured skill.</p>
|
||||
<p style="font-size: 0.9rem; color: #2e7d32; font-weight: 600; margin-top: 12px;">Recommended — always produces the correct SKILL.md format.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div style="background: #fff3e0; border-left: 4px solid #ff9800; padding: 20px 28px; border-radius: 8px; max-width: 900px; margin: 32px auto 0 auto;">
|
||||
<p style="font-weight: 700; margin: 0 0 8px 0;">⚠️ Watch out (method 1)</p>
|
||||
<p style="margin: 0; font-size: 0.95rem; color: #444;">The prompting method sometimes creates the wrong structure. Instead of generating a folder with <code>SKILL.md</code> inside (e.g. <code>weather-fetcher/SKILL.md</code>), it creates a plain <code>weather-fetcher.md</code> file. The wrong form isn’t recognized as a skill by Claude Code.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="pillar-footer">
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #009688;">
|
||||
<span class="pmc-emoji">🧑‍💼</span>
|
||||
<span class="pmc-title">Agents</span>
|
||||
<span class="pmc-subtitle">— the specialists</span>
|
||||
<span class="pmc-body">A dedicated Claude worker — own context, own tools, own focus. Each runs in isolation.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ fresh working memory per run</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #9c27b0;">
|
||||
<span class="pmc-emoji">📝</span>
|
||||
<span class="pmc-title">CLAUDE.md</span>
|
||||
<span class="pmc-subtitle">— your memory</span>
|
||||
<span class="pmc-body">Knowledge <em>you</em> provide to the model. Read every session. Keep it under 200 lines.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ 200-line problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card" style="border-left: 4px solid #4caf50;">
|
||||
<span class="pmc-emoji">🎯</span>
|
||||
<span class="pmc-title">Skills</span>
|
||||
<span class="pmc-subtitle">— the know-how</span>
|
||||
<span class="pmc-body">What the specialist (or Claude) can actually do. Loaded on demand — only when needed.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ progressive disclosure</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #3f51b5;">
|
||||
<span class="pmc-emoji">💭</span>
|
||||
<span class="pmc-title">Context</span>
|
||||
<span class="pmc-subtitle">— the working memory</span>
|
||||
<span class="pmc-body">What Claude holds in his head now — fresh every new chat. Finite budget; compact at ~50%.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ dumb-zone problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #ef6c00;">
|
||||
<span class="pmc-emoji">📘</span>
|
||||
<span class="pmc-title">Workflows</span>
|
||||
<span class="pmc-subtitle">— the instruction manual</span>
|
||||
<span class="pmc-body">Repeatable step-by-step recipes — like an AC install guide. Deterministic, reproducible.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ reproducible recipes</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- ============================================================ -->
|
||||
<!-- NEW SLIDE 39: Skill config fields with frontmatter -->
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<div class="slide" data-slide="39" data-level="skills">
|
||||
<h1>Skill config fields with frontmatter</h1>
|
||||
<p style="font-style: italic; color: #666; margin: 8px 0 20px 0;">Most fields control how and when the skill loads — enforced by the harness. Only <code>description</code> lives in prompt-land.</p>
|
||||
<div style="margin: 0 0 24px 0;">
|
||||
<div class="field-row" style="padding-bottom: 6px; border-bottom: 2px solid #ddd;">
|
||||
<span class="field-name" style="color: #999; font-size: 0.75rem; text-transform: uppercase; letter-spacing: 1px;">Field</span>
|
||||
<span class="field-desc" style="color: #999; font-size: 0.75rem; text-transform: uppercase; letter-spacing: 1px;">Description</span>
|
||||
<span class="field-enforced" style="color: #999; font-size: 0.75rem; text-transform: uppercase; letter-spacing: 1px; min-width: 110px; text-align: right;">Enforced by</span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">name <span class="field-recommended">Recommended</span></span>
|
||||
<span class="field-desc">Display name and <code>/slash-command</code> (defaults to directory name)</span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">description <span class="field-required">Required</span></span>
|
||||
<span class="field-desc">When to invoke — used for auto-discovery. Write it clearly.</span>
|
||||
<span class="field-enforced"><span class="pill-prompt">prompt</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">argument-hint</span>
|
||||
<span class="field-desc">Autocomplete hint shown in the <code>/</code> menu (e.g. <code>[city-name]</code>)</span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">disable-model-invocation</span>
|
||||
<span class="field-desc">Set <code>true</code> to prevent Claude from invoking this skill automatically</span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">user-invocable</span>
|
||||
<span class="field-desc">Set <code>false</code> to hide from <code>/</code> menu — background knowledge only</span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">allowed-tools</span>
|
||||
<span class="field-desc">Tools allowed without permission prompts when this skill is active</span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">model</span>
|
||||
<span class="field-desc">Model to use when skill is active: <code>haiku</code>, <code>sonnet</code>, <code>opus</code></span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
<div class="field-row">
|
||||
<span class="field-name">context</span>
|
||||
<span class="field-desc">Set to <code>fork</code> to run skill in an isolated subagent context</span>
|
||||
<span class="field-enforced"><span class="pill-harness">harness</span></span>
|
||||
</div>
|
||||
</div>
|
||||
<p style="font-style: italic; color: #444; text-align: center; max-width: 900px; margin: 16px auto 0 auto; background: #fafafa; padding: 16px 24px; border-radius: 8px;">The <code>description</code> field is the single prompt-land field — it’s what makes Claude decide when to invoke your skill. Write it well.</p>
|
||||
<div class="pillar-footer">
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #009688;">
|
||||
<span class="pmc-emoji">🧑‍💼</span>
|
||||
<span class="pmc-title">Agents</span>
|
||||
<span class="pmc-subtitle">— the specialists</span>
|
||||
<span class="pmc-body">A dedicated Claude worker — own context, own tools, own focus. Each runs in isolation.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ fresh working memory per run</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #9c27b0;">
|
||||
<span class="pmc-emoji">📝</span>
|
||||
<span class="pmc-title">CLAUDE.md</span>
|
||||
<span class="pmc-subtitle">— your memory</span>
|
||||
<span class="pmc-body">Knowledge <em>you</em> provide to the model. Read every session. Keep it under 200 lines.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ 200-line problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card" style="border-left: 4px solid #4caf50;">
|
||||
<span class="pmc-emoji">🎯</span>
|
||||
<span class="pmc-title">Skills</span>
|
||||
<span class="pmc-subtitle">— the know-how</span>
|
||||
<span class="pmc-body">What the specialist (or Claude) can actually do. Loaded on demand — only when needed.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ progressive disclosure</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #3f51b5;">
|
||||
<span class="pmc-emoji">💭</span>
|
||||
<span class="pmc-title">Context</span>
|
||||
<span class="pmc-subtitle">— the working memory</span>
|
||||
<span class="pmc-body">What Claude holds in his head now — fresh every new chat. Finite budget; compact at ~50%.</span>
|
||||
<span class="pmc-badge" style="background: #fce4ec; color: #c62828;">⚠️ dumb-zone problem</span>
|
||||
</div>
|
||||
<div class="pillar-mini-card inactive" style="border-left: 3px solid #ef6c00;">
|
||||
<span class="pmc-emoji">📘</span>
|
||||
<span class="pmc-title">Workflows</span>
|
||||
<span class="pmc-subtitle">— the instruction manual</span>
|
||||
<span class="pmc-body">Repeatable step-by-step recipes — like an AC install guide. Deterministic, reproducible.</span>
|
||||
<span class="pmc-badge" style="background: #e8f5e9; color: #2e7d32;">✅ reproducible recipes</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- ============================================================ -->
|
||||
<!-- NEW SLIDE 29: Context concept intro -->
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide: Context -->
|
||||
<div class="slide section-slide" data-slide="34">
|
||||
<div class="slide section-slide" data-slide="40">
|
||||
<div class="slide-viewport-content">
|
||||
<h1>🧠 Context</h1>
|
||||
<div style="text-align: center; margin: 12px auto 20px auto;">
|
||||
@@ -1668,14 +2018,14 @@ todoapp/
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide 14: Skills Section Divider -->
|
||||
<div class="slide section-slide" data-slide="35" data-level="skills">
|
||||
<div class="slide section-slide" data-slide="41" data-level="skills">
|
||||
<div class="section-number">Topic 2</div>
|
||||
<h1>🎓 Skills — What the Weather Reporter Knows</h1>
|
||||
<p class="section-desc">Skills are the specific things the reporter has been trained to do. Our reporter has two: <strong>fetch the data</strong>, and <strong>render it as a card</strong>.</p>
|
||||
</div>
|
||||
|
||||
<!-- Slide 15: The Training Manual -->
|
||||
<div class="slide" data-slide="36">
|
||||
<div class="slide" data-slide="42">
|
||||
<h1>The Training Manual</h1>
|
||||
<div class="analogy-box">
|
||||
<h4>Think of it like this</h4>
|
||||
@@ -1702,7 +2052,7 @@ todoapp/
|
||||
</div>
|
||||
|
||||
<!-- Slide 16: When to Turn Something Into a Skill -->
|
||||
<div class="slide" data-slide="37">
|
||||
<div class="slide" data-slide="43">
|
||||
<h1>When to Turn Something Into a Skill</h1>
|
||||
<div class="info-box">
|
||||
<h4>Tip from Boris Cherny (creator of Claude Code) — Feb 1, 2026</h4>
|
||||
@@ -1739,7 +2089,7 @@ todoapp/
|
||||
</div>
|
||||
|
||||
<!-- Slide 17: Why Separate Agents and Skills? -->
|
||||
<div class="slide" data-slide="38">
|
||||
<div class="slide" data-slide="44">
|
||||
<h1>Why Separate Agents and Skills?</h1>
|
||||
<div class="two-col">
|
||||
<div>
|
||||
@@ -1765,7 +2115,7 @@ todoapp/
|
||||
</div>
|
||||
|
||||
<!-- Slide 18: How to Create Your Own Skill -->
|
||||
<div class="slide" data-slide="39">
|
||||
<div class="slide" data-slide="45">
|
||||
<h1>How to Create Your Own Skill</h1>
|
||||
<p>Skills are plain markdown files. If you can write a recipe, you can write a skill.</p>
|
||||
<div class="how-to-trigger">
|
||||
@@ -1818,7 +2168,7 @@ Fetch the current temperature for Dubai, UAE.
|
||||
</div>
|
||||
|
||||
<!-- Slide 19: Skill Config Fields -->
|
||||
<div class="slide" data-slide="40">
|
||||
<div class="slide" data-slide="46">
|
||||
<h1>Skill Config Fields</h1>
|
||||
<p>The small config block at the top of a SKILL.md (the "frontmatter") controls how the skill behaves:</p>
|
||||
<div style="margin: 24px 0;">
|
||||
@@ -1858,14 +2208,14 @@ Fetch the current temperature for Dubai, UAE.
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide 20: Context Section Divider -->
|
||||
<div class="slide section-slide" data-slide="41" data-level="context">
|
||||
<div class="slide section-slide" data-slide="47" data-level="context">
|
||||
<div class="section-number">Topic 3</div>
|
||||
<h1>🧠 Context — The Reporter's Brain</h1>
|
||||
<p class="section-desc">Now that you've met the reporter and know their skills, let's understand what they can actually hold in mind at once. Every agent — including the weather reporter — gets its own fresh brain.</p>
|
||||
</div>
|
||||
|
||||
<!-- Slide 21: Claude's Brain -->
|
||||
<div class="slide" data-slide="42">
|
||||
<div class="slide" data-slide="48">
|
||||
<h1>Claude's Brain</h1>
|
||||
<div class="analogy-box">
|
||||
<h4>Think of it like this</h4>
|
||||
@@ -1903,7 +2253,7 @@ Fetch the current temperature for Dubai, UAE.
|
||||
</div>
|
||||
|
||||
<!-- Slide 22: What Loads at Session Start -->
|
||||
<div class="slide" data-slide="43">
|
||||
<div class="slide" data-slide="49">
|
||||
<h1>What Loads at Session Start</h1>
|
||||
<p>The moment you open Claude Code, certain things land in Claude's brain <strong>before you've typed a word</strong>. The rest waits in the wings — only loaded when you actually need it. This is called <strong>progressive disclosure</strong>.</p>
|
||||
<img src="../assets/concepts/context.jpg" alt="Diagram showing what loads into Claude's context window at session start" style="width: 100%; max-width: 800px; margin: 24px auto; display: block; border-radius: 8px;" />
|
||||
@@ -1937,7 +2287,7 @@ Fetch the current temperature for Dubai, UAE.
|
||||
</div>
|
||||
|
||||
<!-- Slide 23: Keep the Brain Clear -->
|
||||
<div class="slide" data-slide="44">
|
||||
<div class="slide" data-slide="50">
|
||||
<h1>Keep the Brain Clear</h1>
|
||||
<p>The more stuff crammed into Claude's brain, the harder it is to focus on what matters. This is called <strong>context rot</strong> — performance drops as the brain gets crowded.</p>
|
||||
<div class="info-box">
|
||||
@@ -1981,7 +2331,7 @@ Fetch the current temperature for Dubai, UAE.
|
||||
</div>
|
||||
|
||||
<!-- Slide 24: How to Manage Your Context -->
|
||||
<div class="slide" data-slide="45">
|
||||
<div class="slide" data-slide="51">
|
||||
<h1>How to Manage Your Context</h1>
|
||||
<p>You can't <em>create</em> the context — it's just there, the moment you open a chat. But you can <strong>see</strong> how full it is, <strong>trim</strong> it down, or <strong>wipe</strong> it clean. Three commands give you full control.</p>
|
||||
<div class="how-to-trigger">
|
||||
@@ -2026,14 +2376,14 @@ Fetch the current temperature for Dubai, UAE.
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide 25: CLAUDE.md Section Divider -->
|
||||
<div class="slide section-slide" data-slide="46" data-level="claude-md">
|
||||
<div class="slide section-slide" data-slide="52" data-level="claude-md">
|
||||
<div class="section-number">Topic 4</div>
|
||||
<h1>📋 CLAUDE.md — The Reporter's Pocket Rulebook</h1>
|
||||
<p class="section-desc">The weather reporter consults this at the start of every shift — even though their brain resets overnight. It's the standing instructions pinned in that brain before you've said a word.</p>
|
||||
</div>
|
||||
|
||||
<!-- Slide 26: The Employee Handbook -->
|
||||
<div class="slide" data-slide="47">
|
||||
<div class="slide" data-slide="53">
|
||||
<h1>The Employee Handbook</h1>
|
||||
<div class="analogy-box">
|
||||
<h4>Think of it like this</h4>
|
||||
@@ -2061,7 +2411,7 @@ This is the Q2 marketing campaign brief — targeting small business owners.
|
||||
</div>
|
||||
|
||||
<!-- Slide 27: How to Create CLAUDE.md -->
|
||||
<div class="slide" data-slide="48">
|
||||
<div class="slide" data-slide="54">
|
||||
<h1>How to Create Your CLAUDE.md</h1>
|
||||
<p>You don't need to write CLAUDE.md by hand. Claude can look at your project and draft one for you.</p>
|
||||
<div class="how-to-trigger">
|
||||
@@ -2106,7 +2456,7 @@ open, edit, save <span class="comment"># Tweak it like any doc</span><
|
||||
</div>
|
||||
|
||||
<!-- Slide 28: Grow CLAUDE.md With Every Mistake -->
|
||||
<div class="slide" data-slide="49">
|
||||
<div class="slide" data-slide="55">
|
||||
<h1>Grow CLAUDE.md With Every Mistake</h1>
|
||||
<div class="info-box">
|
||||
<h4>Tip from Boris Cherny (creator of Claude Code) — Feb 1, 2026</h4>
|
||||
@@ -2143,7 +2493,7 @@ open, edit, save <span class="comment"># Tweak it like any doc</span><
|
||||
</div>
|
||||
|
||||
<!-- Slide 29: What Goes in CLAUDE.md -->
|
||||
<div class="slide" data-slide="50">
|
||||
<div class="slide" data-slide="56">
|
||||
<h1>What Goes in CLAUDE.md</h1>
|
||||
<div class="code-block"><span class="comment"># CLAUDE.md</span>
|
||||
|
||||
@@ -2171,7 +2521,7 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
</div>
|
||||
|
||||
<!-- Slide 30: How CLAUDE.md Loads -->
|
||||
<div class="slide" data-slide="51">
|
||||
<div class="slide" data-slide="57">
|
||||
<h1>How CLAUDE.md Loads</h1>
|
||||
<p>Claude Code uses two mechanisms to find CLAUDE.md files:</p>
|
||||
<div class="two-col">
|
||||
@@ -2204,14 +2554,14 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide 31: Commands Section Divider -->
|
||||
<div class="slide section-slide" data-slide="52" data-level="commands">
|
||||
<div class="slide section-slide" data-slide="58" data-level="commands">
|
||||
<div class="section-number">Topic 5</div>
|
||||
<h1>⚡ Commands — The Trigger</h1>
|
||||
<p class="section-desc">One word kicks off the whole chain. <code>/weather-orchestrator</code> → agent → skill → SVG card. Commands are the entry point into any workflow.</p>
|
||||
</div>
|
||||
|
||||
<!-- Slide 32: Commands — The Entry Point -->
|
||||
<div class="slide" data-slide="53">
|
||||
<div class="slide" data-slide="59">
|
||||
<h1>Commands — The Entry Point</h1>
|
||||
<div class="analogy-box">
|
||||
<h4>Think of it like this</h4>
|
||||
@@ -2255,7 +2605,7 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
</div>
|
||||
|
||||
<!-- Slide 33: How to Create Your Own Command -->
|
||||
<div class="slide" data-slide="54">
|
||||
<div class="slide" data-slide="60">
|
||||
<h1>How to Create Your Own Command</h1>
|
||||
<p>Commands are markdown files too. If you can write a recipe, you can write a command.</p>
|
||||
<div class="how-to-trigger">
|
||||
@@ -2310,14 +2660,14 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
<!-- ============================================================ -->
|
||||
|
||||
<!-- Slide 34: Workflow Sub-Section (Putting It All Together) -->
|
||||
<div class="slide section-slide" data-slide="55" data-level="workflow">
|
||||
<div class="slide section-slide" data-slide="61" data-level="workflow">
|
||||
<div class="section-number">Putting It All Together</div>
|
||||
<h1>🎼 Workflow — All Five Pieces Together</h1>
|
||||
<p class="section-desc">Watch the weather reporter example run from one keystroke to SVG card output. Five concepts, one orchestrated flow.</p>
|
||||
</div>
|
||||
|
||||
<!-- Slide 35: Command → Agent → Skill -->
|
||||
<div class="slide" data-slide="56">
|
||||
<div class="slide" data-slide="62">
|
||||
<h1>Command → Agent → Skill</h1>
|
||||
<p>This is the <strong>core architecture pattern</strong> of Claude Code workflows — demonstrated in this very repo by the weather example:</p>
|
||||
<div class="code-block"><span class="comment">The Orchestration Flow</span>
|
||||
@@ -2344,7 +2694,7 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
</div>
|
||||
|
||||
<!-- Slide 36: Two Ways Skills Are Used -->
|
||||
<div class="slide" data-slide="57">
|
||||
<div class="slide" data-slide="63">
|
||||
<h1>Two Ways Skills Are Used</h1>
|
||||
<p>The weather workflow demonstrates both skill patterns in a single flow:</p>
|
||||
<div class="two-col">
|
||||
@@ -2367,7 +2717,7 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
</div>
|
||||
|
||||
<!-- Slide 37: How to Wire Your Own Workflow -->
|
||||
<div class="slide" data-slide="58">
|
||||
<div class="slide" data-slide="64">
|
||||
<h1>How to Wire Your Own Workflow</h1>
|
||||
<p>A workflow isn't a separate file type. It <em>emerges</em> when one command calls agents and skills in sequence.</p>
|
||||
<div class="how-to-trigger">
|
||||
@@ -2418,7 +2768,7 @@ This is a TodoApp with a FastAPI backend and React frontend.
|
||||
<!-- ============================================================ -->
|
||||
<!-- SLIDE 40: Closing -->
|
||||
<!-- ============================================================ -->
|
||||
<div class="slide title-slide" data-slide="59">
|
||||
<div class="slide title-slide" data-slide="65">
|
||||
<h1>Journey So Far</h1>
|
||||
<p class="subtitle">Five concepts, one running example</p>
|
||||
<p style="margin-top: 20px; font-size: 1.1rem; color: #666; max-width: 640px;">From meeting the weather reporter to wiring the full <strong>Command → Agent → Skill</strong> chain. The same five pieces compose every workflow you'll ever build.</p>
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 124 KiB |
Reference in New Issue
Block a user