What problem does it solve? An Allium (.allium) specification is written for spec authors, not for the people who own, build, or use the system. This Skill turns a spec into a self-contained static HTML document that a non-spec-reader can pick up cold: a narrated walkthrough of how the system actually behaves, backed by a full reference appendix, diagrams, and wireframe mockups. ## Core Features & Use Cases - Narrative documentation: Produces an orientation, a cast of actors, and chronologically ordered journeys walked from the spec's entrypoints, written in plain domain language rather than raw Allium clause syntax. - Reference appendix and diagrams: Renders config/entity/rule/surface tables from allium model/plan JSON, plus hand-authored Mermaid relationship, sequence, and state diagrams. - Inline validation findings: Attaches allium check/analyse diagnostics (deadlocks, unreachable triggers, missing producers) to the exact journey step or construct they concern, phrased as plain-language caveats. - Wireframe mockups: Optionally generates a low-fidelity mockup per declared surface via the Wireframer skill, embedded inline in the journeys that reach it. - Use Case: Point it at spec/leadout.allium and get docs/alluminate/leadout/index.html — a static page you can commit, open directly, or publish via GitHub Pages. ## Quick Start Ask your AI assistant to run the alluminate skill against your .allium spec file to generate the HTML document under docs/alluminate/.