diff --git a/.claude/agents/presentation-learning-journey.md b/.claude/agents/presentation-learning-journey.md index d87ba09..2814250 100644 --- a/.claude/agents/presentation-learning-journey.md +++ b/.claude/agents/presentation-learning-journey.md @@ -171,4 +171,5 @@ After completing changes, report to the user: - **2026-04-22 deck relocated + GDG Kolachi re-topic of slide 1**: deck moved from `presentation/learning-journey/` to `presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/`. This agent's `description` frontmatter already reflects the new path. Slide 1 was replaced with a conference title slide for GDG Kolachi (Apr 25, 2026). New elements: (1) pill-shaped event badge using `linear-gradient(90deg, #1a73e8 0%, #4285f4 55%, #ea4335 100%)` — GDG blue-to-red — with `border-radius: 999px` and a blue drop-shadow; (2) h1 "Agentic Engineering in the CLI" at 3.2rem with tight letter-spacing; (3) `.subtitle` with inline `Claude Code` and `Gemini CLI` brand tints; (4) two 140px round avatar cards side-by-side (gap: 72px) for Shayan Rais and Syed Umaid Ahmed — avatar hover uses blue glow for Shayan and red glow for Umaid to mirror the GDG gradient. Umaid's photo resolves at `../assets/introduction/Umaid/umaid.png` (verified). The `../../!/claude-jumping.svg` mascot path resolves correctly from the new deck folder (the `!/` dir is at repo root, two levels up from `presentation//`) — but the mascot was deliberately dropped because the GDG title slide doesn't need it. Slide count: 40. `data-slide="1"` wrapper unchanged. Slides 2-40 untouched. TOC goToSlide targets: Agents=9, Skills=15, Context=21, CLAUDE.md=26, Commands=32. **Color convention for GDG-brand elements**: use `#1a73e8` (Google blue) and `#ea4335` (Google red) consistently — these are the two poles of the event-badge gradient and the subtitle tints. Do not substitute `#4285f4` (the midpoint blue) for either named role. - **2026-04-23 slide deletion + renumber (51 → 49)**: deleted old slides 3 ("Umaid on Shark Tank Pakistan") and 5 ("#1 Repository Of The Day"), then renumbered to fill gaps. The correct tool for renumbering after a deletion of non-consecutive slides is a Python sentinel-replacement script, NOT a descending-order sed chain. Sed applies all expressions in a single pass per line, so a value can be transformed by multiple expressions (e.g. `data-slide="9"` → `"7"` → `"5"` → `"3"`) — the result is catastrophic collision. The safe pattern: (1) replace each `data-slide="N"` with `data-slide="##N##"` for all N to be changed (in any order), (2) replace each sentinel `data-slide="##N##"` with the final value. Because sentinel strings are unique and never match final-value strings, there are zero collisions. After sentinel replacement, check `grep '##'` but be aware that legitimate `## Section` headings in code blocks will trigger false-positive matches — use `grep 'data-slide="##'` instead. The `goToSlide` function is defined but never called with hardcoded slide numbers in this deck — no TOC updates were needed. `totalSlides` is auto-computed from DOM, also no update needed. Section-divider positions after deletion: Agents=19, Skills=25, Context=31, CLAUDE.md=36, Commands=42, Workflow=45. - **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 `