Reimagine It

/reimagine-it

Banks: references/notes.md · references/forms.md · references/webpage-craft.md (only for the webpage form) · references/craft-floor.md (the interaction contract every webpage output must clear; read every run) · references/review.md (§5.d named-object accuracy + clone scan; load on every verify) · references/forms/ (non-webpage form packs: pdf, document, slides, universal) · references/domains/ (only when the user gave a domain token: artistic / dashboard / photography / cinematic (aka 3d, webgl) / ecommerce / landing / portfolio / infographic) · references/modifiers/ (only when the user gave a modifier: glassmorphism / bento / neon / brutalism / neumorphism / handdrawn) · references/locks/ (loaded on --ref <name>) · references/research/web-craft-2025.md (deep source pack — Awwwards SOTY stack scan, Rauno/Emil craft floor, Lupi/Fragapane data humanism, Feixen/Weingart/Troxler print grammar, Apple AIDA cinematic, view-transitions, scroll-driven animations, kinetic type, sound, neubrutalism — read once, cite in reports) · references/research/infographic-craft.md (15-source infographic pack — Cleveland–McGill, Tufte, Bertin, ISOTYPE, Minard/Snow, Cairo, Lupi, FT Visual Vocabulary, USWDS, WCAG charts, InfoAlign layouts — load when the form or domain is infographic) · examples.md

/reimagine-it is a Content-Derived Design engine. The shipped product reads HTML and writes HTML: extract the headings, facts, names, dates, numbers, links, emails, and colors already in the file, then generate a standalone page in one of 17 tokens (or --auto). Default output is offline.

Do not claim the CLI redesigns PDF, PPTX, DOCX, MOBI, or “any file.” If the user pointed at another format, convert or wrap it as HTML first, run the engine, and only then — if they asked and the toolchain exists — export with a host tool. Report that extra step as host conversion, not as an engine feature.

If local.md exists beside this file, Read it after this skill (host chairs, org, paths). Public installs have no local.md.

Say once: "Running /reimagine-it."

Engine — run the CLI; do not invent the page

The shipped product is the CLI. /reimagine-it is orchestration around it, not a license to hand-author HTML.

1. If the source is not HTML, wrap or extract it into HTML first. Do not claim the engine ingested PDF, PPTX, or DOCX.
2. Run the matching command and use the file it writes:

npx reimagine-it --auto -i page.html -o redesign.html
npx reimagine-it -i page.html -t infographic -o poster.html
npx reimagine-it variations -i page.html -n 3 -o review/
npx reimagine-it extract -i page.html
npx reimagine-it audit redesign.html

3. Open that artifact. Report from it. If npx reimagine-it cannot run, ship REIMAGINED: partial and name the exact blocker — do not substitute a model-written page.

Categories (you choose · agent decides)

Optional tokens. Combine freely. You pick tokens; the agent picks questions, form (if unset), mutations, and the stretch.

Combine freely. Known form / domain / modifier tokens load packs. Every other word is kept and followed. There is no list of allowed leftover words.

/reimagine-it auto
/reimagine-it webpage cinematic

/reimagine-it webpage infographic
/reimagine-it infographic
/reimagine-it infographic <any leftover words>
/reimagine-it svg
/reimagine-it audit
/reimagine-it 3js
/reimagine-it simulation
/reimagine-it webpage artistic glassmorphism --font "Playfair Display, serif"
/reimagine-it lock gold/domains/cinematic/after.html as house-cinema
/reimagine-it webpage --ref house-cinema
/reimagine-it webpage bento --variants 3

Interview is off unless they picked interview. Do not grill unprompted. Do not ask "what style do you want?" — not even in interview.

Every mode must ship an artifact (unless --plan-only). A list of vibes is not the deliverable.

Hard contract

1. Read this file. Load references/notes.md and references/forms.md.
2. Sniff context. Interview only if interview was chosen.
3. Name the adjacent possible: spare parts already here + one combination they did not request.
4. Pick four notes in private (device · leap · craft · effect). Answer with mutations, not mood words.
5. Route a hero form. Run the CLI into that form (-t or --auto). Do not hand-author a replacement page.
6. Name one stretch they did not know was in bounds. Build it if cheap; otherwise give the exact next command.
7. Kill list in notes.md. No "wow". No prompt-slop. No TED-over-B-roll.
8. Paid gate: code, SVG, HTML, PDF, docx, pptx, local demos are free. Ask before billed image/video/model APIs.
9. No commit/push unless asked.
10. Report REIMAGINED: shipped | partial | blocked.

Procedure

REIMAGINED Progress:
- [ ] 0. Mode + categories parsed (leftover words kept as brief) + context sniffed
- [ ] 0.5. Interview only if that category was chosen
- [ ] 0.75. Adjacent possible named (private)
- [ ] 0.85. Anchor list — extract 3–5 concrete nouns/proper nouns/dates/verbs from the source; every plate must map back
- [ ] 1. Four notes chosen (private)
- [ ] 2. Hero form routed (unless user forced one)
- [ ] 2.4. Variation sample picked (avoid previous draw; pin if --seed / --variant)
- [ ] 2.5. Modifiers / font override / --ref loaded if present
- [ ] 2.6. Output is standalone HTML (host conversion only if the user asked and the toolchain exists)
- [ ] 2.7. Craft floor loaded (references/craft-floor.md) — every rule enforceable before render
- [ ] 3. Hero artifact written (or N variants if --variants)
- [ ] 4. Stretch named (and built if cheap)
- [ ] 4.5. --full plus-pass if requested
- [ ] 5. Verify with evidence (functional + visual + craft-floor scan)
- [ ] 6. Report REIMAGINED: shipped | partial | blocked

Auto mode — the automatic design loop

auto is the person-like invocation: the user gives context, not a pile of commands. Infer the best form from the source, generate up to three coherent candidate directions, run the craft-floor checks, and return the strongest standalone artifact plus the selected token, seed, evidence, and rejected candidates. Never overwrite the source. Never invent facts. If a host can render previews, show the selected artifact and make the alternatives available for comparison.

Auto is deliberately model-agnostic. An agent host may use the returned plan as structured context, delegate visual review to a subagent, or supply a model-specific renderer. The core engine remains deterministic and safe without an API key. --auto is an explicit CLI equivalent; plain /reimagine-it remains the full inferred workflow.

0. Token parse (open brief — do not drop words)

This skill is a creative engine. The user may type anything after /reimagine-it. Do not require a matching pack. Do not autocorrect unknown words into a listed domain. Do not ask "what style do you want?"

1. Split on whitespace. Consume flags and their arguments (--seed, --style, --font, --ref, --variants, --sound, --notes, --plan-only, --full, --variant, --allow-fetch, --ask-format, --list-refs). Handle lock … as … as its own command.
2. Classify remaining words that exactly match a known form, domain (incl. 3d / webgl), or modifier.
3. Join every leftover word, in order, as the brief. Empty brief is allowed. Multi-word briefs are the point.
4. A known modifier still loads its pack (neon, handdrawn, …). Leftover words around it stay in the brief.

The brief is a lens, not new content and not a closed theme list. Apply it to ground, motif, pattern, type, and motion. Source facts stay source facts. Log it on the report Brief: line (or none).

0. Context sniff (do not skip)

In parallel, cheaply:

• Workspace root, README, GOAL.md if present (read; do not overwrite)
• git status -sb if a repo
• Open / recently viewed files if known
• User text after the slash
• Domain files the repo already points at (CONTRIBUTING, protocol docs, failing tests)
• The target file if the user pointed at one (prefer .html; if they pointed at PDF/PPTX/DOCX, wrap or extract into HTML before calling the engine)

One-sentence lock: what this is, what happens to them.

If context is empty (blank chat, empty folder) and no interview: still ship. Invent from the folder name and any README. Do not stall for a brief.

0.5 Interview category (skip unless chosen)

Only when they passed interview. You choose the category; the agent decides the questions.

• After the sniff, ask only what context cannot answer.
• One question at a time. Wait. Multiple questions at once is bewildering.
• Each question includes a recommended answer. They can take it, replace it, or say just go to skip the rest and build.
• Questions come from the note bank (device / leap / craft / effect) — not "what style" or "any preferences?"
• If the codebase can answer, Read/Grep instead of asking.
• Cap 4 questions, then build. Do not leave the session in interview forever.

0.75 Adjacent possible (private)

From the parts already in this repo or thread, name one unused combination. That is the leap candidate. Do not dump a mood board.

Pick one SCAMPER letter as the mutation (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse). Do not run all seven in chat.

0.85 Anchor list (private, but every plate must map to one)

From the source, extract 3–5 concrete anchors: proper nouns (people, places, brands), dates, numbers, verbs of action, physical objects, quoted phrases. These are the units of content the design must serve.

Every plate, tile, section, chart, or hero unit in the output must map back to at least one anchor. If it does not, delete it — do not paint a placeholder tile with the word blank, sample, or an alt-text stand-in (see must-not).

Record the anchor → plate mapping privately (or in the local ledger). Cite it on the report Anchors: line so the user sees the design isn't drifting from the source.

Example — Texas notebook source: anchors = {Jordan Rivers, Big Bend, 1836, Post Office, west Texas sunset}. Draw C's shader-hero → sunset; letterpress-card #01 → 1836; map plate → Big Bend; caption → Rivers; kicker → Post Office. Every unit serves an anchor.

1. Four notes (private)

From references/notes.md: one Device, one Leap (vastness + accommodation, moral beauty, big ideas, small self), one Craft, one Effect. Mutations name a cut, plate, magnet, withheld title, first-run beat, API shape, or demo — not "cinematic."

Do not dump the bank in chat.

2. Form router

Follow references/forms.md unless a category forced the family.

Webpage / HTML / infographic → load references/webpage-craft.md before writing the file. If the user added a domain (second word), also load the matching pack in references/domains/. Token infographic — as a visual form or as a domain — always loads references/domains/infographic.md and references/research/infographic-craft.md. Lock structure (list / sequence / hierarchy / compare / values / relation) from this source before drawing marks. If they added a modifier (third word or --style), also load the matching pack in references/modifiers/. Leftover words are the brief (step 0) — follow them; do not require a pack file. If they passed --ref <name>, load references/locks/.md instead of (or in addition to) a domain — treat locks as domain packs.

SVG → load references/forms/svg.md. Marks in the field, type in the gutter. No label on a path. Alive-micro default: 2–4 loops on marks (weenie-breathe + one fact-loop + hover pairing). Brief still / no-motion / print freezes loops. Leftover words are a lens. Do not clone the Texas gold weenie onto a different source.

3js → load references/forms/3js.md. Reserved HUD strip. Silhouettes from this source. Not a primitive demo. Alive-micro default: idle life on 2–3 meshes (weenie-turn, flow along a source curve, sun-breath) plus camera ease / wide-drift. Brief still pins the camera and freezes meshes. Leftover words are a lens. Do not clone the Texas gold room onto a different source.

simulation → load references/forms/simulation.md. Playable model of this source's sequence (years, days, handshake steps — whatever it times with). Type in the gutter. Marks on the field. Nested short spans are inspectable. Default paused on the first fact. Leftover words are a lens. Do not clone the Texas 1836–1995 clock onto a different source.

PDF / document / slides → host conversion only. Prefer: extract or wrap as HTML, run npx reimagine-it, ship HTML. Load references/forms/ only if the user explicitly asked for that format and Weasyprint / python-docx / python-pptx (etc.) is on the machine. Do not present those packs as CLI tokens.

Any webpage output — with or without a domain / modifier / lock — must land hero-scale inline SVG doing real work, three moving elements at any moment, and 3D that reads in a still (rotation ≥ 12° + shadow blur ≥ 24px, or translateZ ≥ 30px + real shadow, or inline WebGL2). If a screenshot cannot prove all three, the redesign did not earn the form. Exception — infographic: the poster stays orthographic (paper drop-shadow only; no rotateX on the board).

Non-HTML export — optional, never the default claim. If the user asked for PDF/PPTX/DOCX and the toolchain exists, follow the matching form pack. Otherwise ship HTML and name the missing tool.

Form follows the leap:

• Capability in this codebase → implement here (plus a tiny proof: test, CLI, fail-demo).
• Seeing-tool (infographic, weenie, canvas, explainer HTML, one-shot deck/PDF) → <workspace>/reimagined/<yyyy-mm-dd>-<slug>/.
• Never hide a product feature inside reimagined/ as a souvenir.

2.4 Creative variation (never repeat)

/reimagine-it must not return the same output twice for the same source unless the caller pinned a seed with --seed <n> (or picked a named --variant). Every fresh run samples a new combination along the axes below so the same brief produces a real range of draws instead of one canned "official" answer:

Rules:

1. Never repeat the previous draw's exact combination. Track it in memory or the local ledger for the session.
2. Content narrows the set — do not pick card-fan for a printed field guide, do not pick letterpress-deboss for a WebGL cinematic. The content decides which sub-space is coherent; variation happens inside it. The leftover brief may reweight that sub-space (ground, pattern, type, motion) without adding facts.
3. The reader register governs coherence. Once you pick a register, the other axes must fit its grammar. A cinematic-shader register needs inline-shader-hero + shader-loop motion + matcap-hero or alcove-scenes 3D; a poster-jazz-improv register needs poster-tile-one-size plates + no-3D-just-shadow + high asymmetry. Do not glue incompatible axes. svg / 3js forms ignore webpage motion samples — they use alive-micro from the form pack. simulation ignores them too — it uses the clock in forms/simulation.md.
4. --seed <n> pins the sample deterministically. Given the same source + same seed, the output must be byte-equivalent so users can reproduce a specific draw for locks or PRs.
5. --variant a / --variant b / … are named seeds. a is the first canonical draw, b the second, etc. Ship them under after.html, after-2.html, after-3.html when a gold pack demonstrates the variance.
6. Show the sample in the report Draw: line so the user knows which combination was picked (e.g. Draw: cinematic-shader · shader-glow · inline-shader-hero · custom-data-glyph · scroll-driven-axis-morph · variable-single-family · matcap-hero).

Gold demonstration (gold/webpage/): Draw A after.html (dashboard-live · deep-night), Draw B after-2.html (editorial-drift · parchment), Draw C after-3.html (cinematic-shader · shader-glow — the raised bar from v2.2 research). twins.png proves the range at a glance.

Gold infographic (gold/domains/infographic/after.html, v2.3): one Texas-notebook draw. Live runs derive palette, pattern, glyphs, and composition from this source (plus leftover brief). Cloning that gold’s scenery or its poster chrome onto a different source is a fail.

Gold Jules (gold/jules/): one parlor draw. Default webpage is the parlor you walk into (full-bleed counter + cone), not a stationery slip. Artistic is a painting of this shop's materials (not gold's cream/coral sine waves). Photography is still-lifes of marble / freezer / walk-up (not a VOL/ISSUE folio clone). Infographic is a star around the cone. SVG is stacked scoops. 3js camera sits on the counter. Simulation is the flavor board. Proof that a second source must not look like the first.

Gold forms (gold/forms/): one Texas-notebook draw each. Live svg / 3js / simulation runs derive weenie, meshes, clock unit, geography, palette, and composition from this source. Do not reuse weenie-left / schematic-center / gutter-right / timeline-bottom, The years run, or an All three place HUD.

2.5 Modifiers · font · lock (extend the pack)

• Modifiers are additive and composable. glassmorphism waives the spine's "blur / glassmorphism as the design" cut-list entry and adds its own non-negotiables (real depth behind the glass, layered panels, reduced motion budget). bento restructures the section grid into named tiles. Modifiers stack (artistic glassmorphism is a real combination); packs must not fight the spine on grid / palette cap / one motif.
• Font override (--font "...") replaces the display or body family. Build a full CSS stack with sensible fallbacks (a serif family gets serif at the end, a mono family gets monospace). Never fetch a webfont; if the user wants one, they must pass --allow-fetch and understand it breaks the offline promise.
• Lock: on /reimagine-it lock <path> [as <name>], read <path> (HTML/CSS/JSON/PDF metadata/etc.) and extract palette + type stack + motifs + motion + 3D signatures + section structure. Write references/locks/.md as a full pack. Later /reimagine-it <target> --ref <name> loads that pack as if it were a domain, so the same design DNA can be applied to a different target (or a different medium — a webpage lock can inform a slides pack).

2.6 Output format(s) — HTML is the engine product

The CLI and playground always ship standalone HTML. That is the valid product claim.

1. Default: run npx reimagine-it (or --auto) on HTML and write .html. Do not invent a PDF/PPTX/DOCX twin.
2. If the source was not HTML: convert or wrap it as HTML first (extract text into a simple page). Then run the engine. Say so in the report Formats: line.
3. If the user explicitly asked for PDF / slides / docx and the local toolchain exists, follow the matching pack in references/forms/ after the HTML artifact exists. If the toolchain is missing, ship HTML and name the exact next command — do not claim the engine wrote that format.
4. --ask-format is only for that optional export step, not for choosing whether the engine works. Default remains HTML.

Log the decision on the report Formats: line (usually html).

3. Build

Include a 5-line README.md next to one-shot folders: what it is, how to run/open, which note drove it. In-place code changes: the proof (test or demo command) is the README.

Hero craft (any form):

• One magnet in the first encounter (weenie, first-run command, first sentence, first failing-then-green demo, first spread, first slide)
• Real content from this context — no lorem, no fake stats, no invented APIs
• Effect before method: they should be able to say what happened, not only how you did it
• Withhold the label until the artifact has done work

Stretch (required in the report): one thing they did not know was in bounds. Build when it is one extra file or a small sibling; otherwise give the exact next slash (/reimagine-it auto, /reimagine-it webpage cinematic, /reimagine-it lock <path>, …).

4. --full plus-pass

After the hero exists: re-read it. Apply one plus (criticism that contains a new move). Do not restart. Do not add a second product.

4.5 --variants N (optional)

If the user asked for N variants, produce N distinct outputs from the same brief. Each variant must land a different make-strange move (not the same page with a new color). Write to <hero>/var-1/, <hero>/var-2/, … and ship a strip.png composite so the user can pick.

5. Verify (functional + visual)

Two passes. Skipping either is a partial at best, not a shipped.

5.a Functional pass — the artifact does the thing:

• Path exists. Report it as a markdown link.
• Code/CLI: the command or test actually ran; paste the exit or the proving line.
• Visual file well-formedness: viewBox on SVG; HTML opens; no required CDN if offline was implied; PDF opens in a viewer; docx/pptx opens in the target app; ebook (mobi/epub) opens in Kindle Previewer / Calibre.
• Motion / 3D: two stills 500 ms apart show visible pixel change; at least one element has ≥ 12° rotation + ≥ 24 px shadow blur, or inline WebGL2.
• Prose: the piece is a file they can keep, not only chat.
• Protocol: a spec they can implement or a spike that runs — not only a metaphor.

5.b Visual verification pass — actually look at the render.

Render the hero into an image (headless Chrome for HTML → PNG at ≥ 1400 px wide; PDF → first-page PNG; docx → export to PDF then PNG; pptx → first-slide PNG; mobi/epub → open in Previewer and screenshot the first two pages). Read the image tool result (or open it in the IDE viewer) and manually scan for every one of these failure modes before reporting shipped:

• Blank plates / placeholder labels. No visible element may literally read blank, placeholder, TBD, TODO, lorem, …, […], xxx, sample text, Title goes here, caption, or an alt-text stand-in. If a slot has no real content from the source, delete the slot — do not paint a card with the word "blank" on it.
• Every plate maps to an anchor. Cross-check every visible unit against the anchor list from step 0.85. Unmapped tiles are drift — delete them.
• Clipped / overlapping text. No label is cut off by another element (e.g. POST OFFICE rendered as POST O CE because a foreground shape overlaps the text). Fix z-index / padding / overflow or move the overlapping element. SVG / 3js: no label sits on a mark, mesh, or path; 3js HUD is a reserved strip, never a stack on the canvas.
• Broken image / broken svg. No alt text is showing where a picture should be. No <svg> renders empty.
• Runaway columns / squashed hero. Nothing extends past the viewport. Hero is not vertically flattened.
• Off-palette accent. Every colored element is on the content-derived palette. No stray CSS-default blue link, no browser-default <button> chrome.
• Wrong content. All copy on the render actually appears in the source (or is a caption/index the skill added). No fabricated place names, dates, statistics, or people.
• Motion proof. If the pack claims motion (svg/3js default is alive-micro), capture two frames (~600 ms apart) and compare hashes; identical hashes = motion did not run. Brief still is the exception.

5.c Craft-floor pass (webpage only) — grep the produced HTML/CSS and confirm the craft-floor contract holds: Run the deterministic audit: npx reimagine-it audit <output-file.html> (or /reimagine-it audit). This runs 19 checks across typography, palette, motion, content, structure, and performance with no LLM and no API key. Python scripts/audit.py is the GitHub Action mirror and must agree. Zero failures must pass; warnings are advisory. Supports --verbose and --json for CI.

• Focus & selection: at least one ::selection rule; at least one :focus-visible rule; no outline: 0 / outline: none without a real replacement.
• Reduced motion: a @media (prefers-reduced-motion: reduce) block is present and decomposes correctly (transitions off, focus indicators still visible, essential state feedback preserved).
• Compositor-only motion: no @keyframes or transitions animate top, left, right, bottom, width, height, margin, padding, font-size, letter-spacing, line-height, word-spacing, color, or background-color (last two are OK for :hover on a static element only). Everything animated during scroll/interaction uses only transform, opacity, or filter.
• No transition: all. Explicit properties, always.
• Kinetic type reserves space: any variable-font axis morph has a letter-spacing buffer or min-width reservation on the animated element.
• Interactive elements have hover + focus states (not just :hover).
• Sound off by default: if --sound was not passed, there is no <audio autoplay>, no Howler autoplay: true, and no unmuted <video> outside an explicit user gesture.
• Auto source safety: auto may read and write only the generated artifact/report; it must not mutate the source unless the user explicitly asks for an edit.

If any of these fail, patch the CSS in one pass; if the fix crosses into "add a whole subsystem," downgrade to partial and name the specific miss.

5.d Named-object + clone pass — load references/review.md. If the source names a public object (the Lone Star flag, a cone, a press), the weenie is that object — not a gold-star / cream-stripe remix. A second source must not wear Texas gold DNA or layout chrome. Gold fixtures: python scripts/review_gold.py.

Log the verify passes on the report:

• Visual verify: with what you scanned for and what you fixed
• Craft floor: with the results of the grep (e.g. ::selection ✓, :focus-visible ✓, prefers-reduced-motion ✓, compositor-only ✓, no transition:all ✓, sound off ✓).

If any failure mode is present and cannot be fixed in one pass, ship partial and name the specific bug — never dress a placeholder up as done.

6. Report

REIMAGINED: shipped | partial | blocked
Mode: reimagine-it
About: <one sentence>
Hero: <path + how to run/open>
Domain / modifier / --ref: <if any>
Brief: <leftover phrase, or none>
Font stack: <if --font was passed>
Anchors: <3–5 nouns/proper nouns/dates from the source that every plate mapped back to>
Draw: <reader-register> · <ground> · <hero-move> · <plate-style> · <motion> · <type-accent> · <3D-signature>
      (svg / 3js: motion is `alive-micro` unless the brief was `still`)
Seed: <n if pinned, else "fresh">
Formats: <usually "html"; name any optional host export>
Sound: <off | ambient | feedback | full — with tier + mute-control + no-autoplay confirmed>
Stretch: <what they didn't know was possible>
Notes: <only if --notes>
Functional verify: <what you actually ran, opened, or checked>
Visual verify: <scan result: no blank plates? no clipped text? every plate maps to an anchor? palette on-source? named weenie is the real object (flag cloth is white star / white over red, not gold-on-parchment)? motion advanced? composition is this source's object, not gold's layout chrome?>
Craft floor: <::selection ✓, :focus-visible ✓, prefers-reduced-motion ✓, compositor-only motion ✓, no transition:all ✓, sound off unless --sound ✓>

Lead the user-facing reply with the artifact and the stretch, not the protocol.

Must not

• Ship a bullet list instead of an artifact
• Return the same draw twice for the same source without an explicit --seed/--variant pin
• Drop leftover user words because they are not a named form, domain, or modifier
• Clone gold DNA or gold composition onto a source that is not that notebook — not the palette (Texas parchment/navy/star-red), not the scenery (Lone Star, Alamo chapel, 1836–1995 map-clock), and not the layout chrome (00 · MASTHEAD rail, /reimagine-it infographic kicker, weenie-left / map-center / gutter-right / timeline-bottom SVG, The years run + All three HUD). Method travels. Composition does not.
• Report shipped without the visual verification pass (5.b) — no exceptions
• Paint a plate that literally reads blank, placeholder, TBD, TODO, lorem, sample, caption, …, […], Title goes here, or any alt-text stand-in. Empty slot → delete the slot. Real content only.
• Ship a render with clipped or overlapped text (e.g. a foreground shape covering half a label). Fix z-index / padding / overflow before reporting shipped.
• Hand-author a redesigned page when npx reimagine-it can run. The CLI is the engine; the skill is the wrapper.
• Claim the CLI redesigns PDF, PPTX, DOCX, MOBI, or “any file.” HTML in, HTML out. Host conversion is extra and optional.
• Silently pretend a missing export toolchain ran. If the user asked for PDF/PPTX and the tool is missing, ship HTML and name the next command.
• Ship a webpage output that fails the craft floor (§5.c) on any of: ::selection styled, :focus-visible styled, prefers-reduced-motion block present and decomposed correctly, compositor-only motion, no transition: all, no outline: 0 without a real replacement, no autoplay sound unless --sound was passed. Patch in one pass or downgrade to partial.
• Animate top / left / right / bottom / width / height / margin / padding / font-size / letter-spacing / line-height / word-spacing / color / background-color for anything that runs during scroll or interaction.

…(truncated)