lesson-debugger

Use when triaging user feedback on a rendered lesson MP4 — symptom→wave mapping, minimal re-run flags, and the structural-change approval protocol. Not for use during waves 1–5 video production.

Jump to install

Repository: blueif16/animate-svg
Last source activity: May 29, 2026 at 19:49
Detected SKILL.md language: English
Stars: 1
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/blueif16/animate-svg --skill lesson-debugger

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

remotion-lesson-composer

Compose the Remotion lesson scene from approved upstream artifacts (Visual Contract, audio-captions intent, ASR-aligned cue boundaries, sketch-overlay schedule). Wave 4 of the lesson pipeline. NEVER hardcodes frame numbers; every timing derives from cue boundaries.

2026-07-16

piflow-inspect

Pi Flow · INSPECT — the instrument router for looking INTO a run or a node: performance, cost, timing, context composition, loop/stall anomalies, recurrence. LOAD THIS SKILL BEFORE debugging or analyzing ANY pi-flow run/node — it routes each question to the piflowctl verb that already answers it (status · telemetry · trace · logs · inspect · optimize · memory · understand), so you never hand-parse `.pi/` internals or write a throwaway analysis script for data an instrument already surfaces. Triggers — load on ANY of: "why is this node slow / expensive / looping / stalled", "where did the time/tokens go", "what did the model actually read / see / miss", "how many calls did it make", "dissect / profile / audit this run", "compare two runs of a node", "did this failure happen before", or any intent to open a `.pi/sessions/*.jsonl`, `run.json`, or node log by hand. To RUN a workflow use piflow-start; to judge/act mid-run use piflow-overlord.

2026-07-10

piflow-maintenance

Pi Flow · MAINTENANCE — the canonical STANDARDS reference for a node config + a run condition: the exact per-node lifecycle, the `op[]` action envelope, PRE/POST hooks, gates & policy, how a node FINISHES (fenced-JSON tail · `submit_result` · `returnMode` · verified-not-trusted), run PROFILES, and the token / contract vocabulary. The brother of piflow-init — init decides WHAT the DAG is (divide the purpose, assign the nodes); MAINTENANCE answers "what is our canonical way to DO this?" for an already-built or half-built loop. LOAD/FOLLOW when editing or extending an existing node.json / template and you need the standard: "where does a script go (which op, pre or post)", "how should this node end / return its result", "how do I add a gate / check / judge", "the exact node lifecycle", "how do promote / state channels work", "set up a profile", "inject vs readScope", "is this the right op syntax". REFERENCE, not a loop — carries the standards only, never the optimize loop and never the divide-and-assign creation

2026-07-10

View all from this repository

name	lesson-debugger
description	Use when triaging user feedback on a rendered lesson MP4 — symptom→wave mapping, minimal re-run flags, and the structural-change approval protocol. Not for use during waves 1–5 video production.

Lesson Debugger

Invoked only after the user reviews the rendered MP4 and reports an issue.

Symptom → Owner

Symptom	Owner
Concept / learning goal wrong	W1 storyboard
Confusing visuals / object choice	W2 visual-design (Visual Contract)
Script content or narration pacing	W2 audio/captions (script content) OR voice config
Caption timing off	W3 voice/ASR — re-check transcript before adjusting
Label overlaps art / element inside wrong region	W2 visual-design — zones not declared (kids-eye §1.5)
Comparison sides don't match (different vocab)	W2 visual-design — identity-preserved-transformation broken (kids-eye §4)
Teaching object doesn't read at glance	W3 primitive-gap-scan — finger-cover test was skipped
Teacher marks / pointer misaligned	W4 sketch-layer (cue-relative offsets) OR composer (frame literal bug)
Sketch marks render past video end / wrong cue	W4 composer — frame literals used instead of cue-relative
Two marks overlap, or a mark covers the glyph it annotates	W4 composer/sketch — anchor geometry wrong (park the mark in the clear gap; not a frame-literal issue)
Duplicate / "twin" components stacked (e.g. a migrated glyph and its destination both rendered)	W4 composer — handoff visibility window + landing position (source must fade before/as destination lands)

lesson-debugger

Install options

Review the source files

Lesson Debugger

Symptom → Owner

Lesson Debugger

Symptom → Owner

Pick the smallest fix

Re-run minimally

Audit the transcript (orchestrator check, not delegated)

Structural changes (need user approval)

Close

Recurring patterns observed (update as we learn)

lesson-debugger

Source facts

Install options

Review the source files

More from this repository

Lesson Debugger

Symptom → Owner

More from this repository

Lesson Debugger

Symptom → Owner

Pick the smallest fix

Re-run minimally

Audit the transcript (orchestrator check, not delegated)

Structural changes (need user approval)

Close

Recurring patterns observed (update as we learn)