SureForge
SkillAn instruction-only skill that makes agents research before they ask, plan before they build, and verify before they call anything done.
- workflow
- verification
- quality
- skill
A Claude Code skill that answers how-does-X-work questions as animated Victorian patent sheets — parts drawn in with numbered leader lines, one plain sentence per step, exported as GIF, MP4 or PNG
Blueprint is a skill for Claude Code: give it a topic and it returns an animated explainer in the style of an old patent drawing — a part kit of 28 pieces (drawers, cabinets, gears, gates, locks, clocks, queues and more), numbered leader lines, things moving along the lines, and one plain sentence per step. The explanation is a chain of but...so... reasoning anchored to one concrete case: the cache example starts from a 120 ms lookup and ends at a 2 ms drawer hit. Sheets ship as a single dependency-free runtime with a <blueprint-scene> element (play/loop/view/click/still modes, blue or linen paper, numbered parts key, speed control, reduced-motion support) or as a standalone HTML file built by scripts/build.mjs. A linter (scripts/check.mjs) catches unknown ids, empty scenes, undrawn parts, overlapping parts, lines through parts or text and gates swinging into things. Export paths cover GIF (README/Slack), MP4 (ffmpeg or Chromium WebCodecs), PNG at 2x, and per-step PNGs for slides; sources cited by an incident sheet are listed under it, not drawn into exports. An incident template turns a postmortem into a ready-made story ending on a timeline. The repo includes 10 small and 11 complex examples, a gallery page, and a website; influences and packaging credit are documented in the README. Needs Node 18+; Playwright (pinned 1.56.1) is optional and only needed for frame rendering and exports.
Use when a concept, an outage or an internal flow needs a self-explanatory picture a reader can step through — docs pages, READMEs, incident reviews, talks. Skip it when you need editable diagram-tool output or live data; sheets are hand-laid scenes, not generated graphs.
Via the skills CLI: npx skills add intincrab/blueprint Or clone into the skills folder: git clone https://github.com/intincrab/blueprint.git ~/.claude/skills/blueprint Needs Node 18+. Playwright is optional (frame rendering and GIF/MP4/PNG exports); set it up once in the skill folder: cd ~/.claude/skills/blueprint npm i npx playwright install chromium Lint and build need nothing but Node: node scripts/check.mjs <scene.js> node scripts/build.mjs examples/small/cache.js --out cache.html Offline or distro Chromium: point BLUEPRINT_CHROMIUM at the binary instead of downloading.
MP4 export on Linux needs ffmpeg (Playwright's Chromium there lacks an H.264 encoder), and --audio may fall back to ffmpeg as well; on macOS Chromium's WebCodecs covers it. The runtime loads IBM Plex Mono from Google Fonts by default — add no-font (or --no-font) for fully offline pages. A multi-scene file exports only its first scene unless you pick --scene. Scenes you make with the skill are yours per the README. MIT. 58 stars as of writing (2026-11-21).
Repository
intincrab/blueprintCharted
An instruction-only skill that makes agents research before they ask, plan before they build, and verify before they call anything done.
Guizang's agent skill turns your repo's recent updates into a finished promo video — real components, code-rendered animation, an original code-written soundtrack — no video editor involved.
An agent skill that geolocates a photo with nothing readable in it — OSM geometry, elevation skylines and satellite tiles turn “where was this taken?” into a measured answer with an error radius.