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

.claude/agents/presentation-learning-journey: record slide-3 insertion methodology and sed/Edit sequencing rule

Browse Source 
Self-evolve log entries from the Apr 18 "What is Claude Code?" slide
insertion: descending-sed renumber method, three-column inline-grid layout
choice, post-insertion section-divider positions (Agents=8 ... Workflow=34),
and the sequencing rule that Edit must run after sed completes — parallel
execution causes "file modified since read" errors.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Shayan Rais
2026-04-18 22:07:54 +05:00
parent c3952d8e41
commit c86880a227
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/agents/presentation-learning-journey.md
+3
View File
@@ -140,6 +140,9 @@ _Findings from previous executions are recorded here. Add new entries as bullet
- **2026-04-18 Write-tool full-rewrite is safer than sed for large restructures**: when reordering sections that account for 80%+ of file content, use the Write tool to write the complete new file in one atomic operation rather than chaining 30+ sed/Edit calls. One Write call either succeeds completely or fails completely — no partial-application bugs. The risk of silent partial-application from a long sed chain (missing a step, wrong order) outweighs the risk of a single Write failure. Verified: Write with correct content + post-write integrity checks (data-slide count, data-level values, goToSlide targets) is the correct approach for whole-file restructures.
- **2026-04-18 weather-reporter rebuild (complete — 37 slides)**: full deck rebuilt from the plan doc at `reports/learning-journey-weather-reporter-redesign.md` using a single Write-tool operation. Final structure: Slides 1-5 (opening arc: no-correct-way → Boris GIF → vibe-vs-agentic → what-is-vibe-coding → good/bad-prompts), Slide 6 (Meet the Person TOC, 5 vertical rows), Slides 7-12 (Agents — weather reporter), Slides 13-18 (Skills — weather-fetcher + weather-svg-creator), Slides 19-23 (Context — reporter's brain), Slides 24-29 (CLAUDE.md — pocket rulebook), Slides 30-32 (Commands — the trigger), Slides 33-36 (Workflow — all five pieces), Slide 37 (Closing — "Five concepts, one running example"). LEVELS map heights updated to match new arc order: agents=17%, skills=33%, context=50%, claude-md=67%, commands=83%, workflow=100%. Journey ticks updated top→bottom: Workflow, Commands, CLAUDE.md, Context, Skills, Agents. TOC goToSlide targets: Agents=7, Skills=13, Context=19, CLAUDE.md=24, Workflow-trigger=30. Both context diagrams preserved: context-window.jpeg on slide 20, context.jpg on slide 21. All real repo file paths verified against actual files before writing (weather-agent.md, weather-orchestrator.md, weather-fetcher/SKILL.md, weather-svg-creator/SKILL.md).
- **2026-04-18 single-slide insertion at position 3 (vocabulary slide "What is Claude Code?")**: inserted one slide between old slide 2 (Boris GIF) and old slide 3 (Vibe Coding vs Agentic Engineering, now slide 4). Method: sed descending renumber for data-slide="3" through data-slide="37" (35 expressions), then separate sed for TOC goToSlide targets (7→8, 13→14, 19→20, 24→25, 30→31), then sed for all banner comments, then Edit to insert the new slide div. New slide has no `data-level` — journey bar shows 0%/empty for slides 3-7 (pre-arc vocabulary slides), which is correct. Three-column layout uses inline `grid-template-columns: 1fr 1fr 1fr` grid (not `.two-col`) since no three-column class exists in the deck. Icons used: 🧠 Model (purple), 💪 Harness (blue), 🤜 Tools (green). Color-coded with existing deck border-left convention: purple=#9c27b0, blue=#2196f3, green=#4caf50. New section-divider positions after insertion: **Agents=8, Skills=14, Context=20, CLAUDE.md=25, Commands=31, Workflow=34**. TOC goToSlide targets updated to match. Total slide count: **38**.
- **2026-04-18 sed-vs-Edit sequencing rule confirmed**: after the sed renumber pass, waited for each sed to fully complete before running the Edit for the new slide. Running sed and Edit in parallel on the same file causes Edit to fail with "file modified since read" — confirmed this is the safe sequencing order.
## Critical Requirements
1. **Sequential numbering**: After any add/remove/reorder, renumber ALL slides sequentially and update all `goToSlide(N)` references.