iso-figure

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: none for the install itself: no account, no API key, no paid plan or service, and nothing else to install first. The skill installed is a single instruction file. Using it afterwards only needs a browser to open and verify the HTML file it produces, which is local. Install "iso-figure" for me. It is a playbook for building an interactive isometric line-art figure of an object in a single self-contained HTML/SVG file: a monochrome technical-illustration look on a captioned plate, with parts you can press that produce real output (typed text, a number, a sound, a changed display) and a live state readout. Repository: https://github.com/MrBongoC/ai-iso-skill (the skill is the whole skills/iso-figure/ folder at the pinned commit: SKILL.md only) Pinned version: install the code at commit 44b4da7714148eef547cc1b102e433472dfe3531 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/MrBongoC/ai-iso-skill into a temporary folder, check out commit 44b4da7714148eef547cc1b102e433472dfe3531, and copy the skills/iso-figure/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 8644bcc2677a289025228dd036e6bb6457690a317e98ec43803edc3c7cd4bde7 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds one file only: SKILL.md (9,041 bytes). There is no separate script, library or dependency list in the folder: the file is instructions plus the small JavaScript projection kernel and the CSS to copy verbatim into the single HTML file the skill later produces. The rest of the repository (README.md, LICENSE, examples/, docs/ with its GIFs, and the .claude-plugin/ plugin manifests at the root) is not part of the skill and is not installed. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. The file names no account, no API key, no telemetry and no remote service. - At use time, everything is local: I name an object, you decide first what pressing a part produces, decompose the object into 3-8 boxes (each box drawn as its three visible faces, ordinary rects, text and paths placed on a face by one SVG matrix() from the kernel), emit the scene back to front, and write one self-contained HTML file. Interaction is class toggles on SVG groups driven by one state object and one render(); motion is CSS only; the frame is four monospace corner captions (Fig N, the object name, the instruction, and a live readout that changes on every interaction). SKILL.md is explicit: no external scripts, and the produced file must run opened from disk — so a figure contacts no host at use time either, and nothing is sent then. Sound, when the object makes it, is local too: an AudioContext created inside the first press handler, routed through one master gain into an AnalyserNode whose waveform is drawn on the screen face. Typed text shown on a screen is escaped for & and < before it is written into the SVG. - Verification at use time is also local, and only when I ask you to use the skill: SKILL.md's procedure step 9 says to load the produced file in a browser (headless is fine), drive it with real key and mouse presses at projected coordinates, read back the readout, screenshot one interacted state, and check that nothing is clipped, that nearer parts cover farther ones, and that there are no console errors. Do none of that during this install. - The look rules are part of the skill: every colour is a CSS custom property with both a dark and a light set, two greys only for linework and one near-white (near-black in light) live colour, no hue, gradients or shadows, no real company logos, product silhouettes or trademarked marks, texture from repetition (vents, key grids, ribbed lines), and the svg carries role="img", tabindex="0" and an aria-label stating what it is and how to operate it, with prefers-reduced-motion honoured. A figure that only animates is out of scope: if the user cannot press it and get output, the skill says to pick a different object. - The upstream README also offers other install routes (the Claude Code plugin commands /plugin marketplace add MrBongoC/ai-iso-skill and /plugin install iso-figure@ai-iso-skill, and downloading iso-figure.skill from the latest GitHub release for Claude.ai). Do not use any of them for this install: they fetch the current version, not the pinned commit. The manual route in step 1 and step 3 below is the only route here. - The two files under examples/ in the repository (desk-synth.html and pocket-calculator.html) are sample figures the author made with the skill; they are not installed. Note for honesty that, unlike what SKILL.md prescribes for figures it produces, those two sample files load a DM Mono stylesheet from fonts.googleapis.com when opened — that host is named only in the examples, never in SKILL.md, and no example file is copied by this install. 3. When I say "yes, install", install it as a skill: copy the whole iso-figure folder into the agent's skills directory, in a folder named "iso-figure", keeping its file (SKILL.md). 4. Verify with no network calls: frontmatter valid, file in place. 5. Report what was installed, where, and what I still need to do myself (for example: name the object I want a figure of myself; using the skill is a separate step that only starts when I ask for it, and it produces a local HTML file that I open in a browser — no account, key or service is needed then either). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.