Cavalry MCP, the Stallion bridge, 89 reference demos, and seven visual grammar primitives — packaged into one trigger-rich skill so the next agent that hears "ShurIQ motion graphics" picks up where the last one left off.
Session 124 spent hours wiring up Cavalry MCP, mapping the live API by debugging it against the JS console, building 88 demos, and codifying the seven visual grammar primitives. None of that knowledge survives a context flush. Session 125 would start by asking "what's a Stallion bridge?"
The next agent reads a stale MCP package's source, hallucinates an API surface, runs into the sandbox render block, and rebuilds the dark-canvas constellation that was already migrated to editorial-tan. It re-makes the same mistakes a senior engineer just fixed.
The agent reads a trigger-rich SKILL.md, loads three reference docs (catalog, visual grammar, integration patterns), and inherits the validated Cavalry API surface, the canonical editorial-tan canvas, the three-layer update rule, and 89 working demos to point at.
Every demo runs live in Cavalry through the Stallion HTTP bridge, or embeds as inline animated SVG anywhere the report ships. No one has to install anything to see what a primitive looks like.
bc-definition) for teaching betweenness centrality without jargon.Static spec lives in the visual grammar reference. Motion vocabulary lives in this skill. Both render on the editorial-tan canvas — the same warm baseline as the surrounding report, so the constellation reads continuously with the rest of the deliverable.
Every primitive renders on #FAF8F5 for Cavalry comps and #EFE9DD for embedded gallery cards. The seven-color musical-theory palette retains its identity on tan; edges flip to ink-on-tan in the 4–15 opacity band; the three-tier glow ratios (14/36/92) carry across canvases unchanged.
This is the rule that turned a quick "swap dark for tan" request into a session-spanning canon migration. If only the artifact source files change, the next agent reads a stale catalog and rebuilds the dark variant. The skill carries this rule explicitly so the migration sticks.
The Cavalry script files that define the runtime truth.
scenes/grammar/*.js
What humans browse — the gallery site that demonstrates each demo. Redeploy after every change.
techniques-site/site/index.html
What future agents read. If you skip this layer, the next agent reproduces what you just fixed.
~/.dotfiles/ai/skills/shuriq-motion/references/*.md
Sed batch substitution across every script file in one pass — three patterns updated nine grammar files when the dark canvas became editorial-tan.
# dark → editorial-tan canvas migration (Session 125) sed -i '' 's/#0A0A0A/#FAF8F5/g' scenes/grammar/*.js # bg sed -i '' 's/#F5F5F5/#1A1A1A/g' scenes/grammar/*.js # text/edges sed -i '' 's/#888/#7A7468/g' scenes/grammar/*.js # text-faint
Editorial sites, intelligence briefs, dashboards. Self-contained, browser-renders, no Cavalry needed. Each card on the techniques gallery is the recipe — copy a <svg> block, adapt the data, deploy.
Trade: lower fidelity than Cavalry, limited to what CSS/SVG animation expresses.
Investor presentations, video reports, social-media-ready hero panels. Run the demo via ./run-tech.sh <name>, scrub in Cavalry, export through Render Manager or screen-record.
Trade: sandbox blocks programmatic export — needs the user's hands.
Per-report personalization, recurring weekly artifacts, multi-language batches. Bind a Google Sheet to scene attributes, emit one MP4 per row through Cavalry's Dynamic Rendering.
max-age=immutable on a file that's still moving.During the dark→tan migration, the gallery deployed but the previews didn't update — Cloudflare's edge cache served the prior version for hours. Two safe patterns: query-string versioning (vg-entity-node.js?v=20260501-1200) on every meaningful change, or content-hash filenames for automatic invalidation per build. Verify the live URL with curl -I after every deploy; WebFetch caches its own copy and will lie to you.
No manual /load, no install step. The agent reads the frontmatter description at session boot; when a user message contains "ShurIQ motion graphics" or "Cavalry MCP" or any other trigger, the skill activates and three reference docs become available on demand.
cd projects/shur/shuriq-report-studio/motion-graphics/integration/stallion-helpers ./run-tech.sh list # see all 89 ./run-tech.sh <demo-name> # run one in Cavalry ./run-tech.sh tour # cycle 50 techniques (~250s) ./run-tech.sh typography # cycle 30 type demos (~150s) ./run-tech.sh grammar # cycle 9 grammar demos (~54s)
Stallion must be running inside Cavalry (Scripts > Stallion) before any demo.