ijfw-design

# IJFW Design ## Rule 0 - Real HTML mockups, never ASCII When asked to show a design, mockup, layout, screen, or variant, produce REAL HTML and use the live design companion when a shell is available: 1. Start the companion with `ijfw design start` (or `ijfw design start --no-open` in CI/headless sessions). It serves `http://localhost:<port>/design`. 2. Write standalone HTML variants under `.planning/<feature>/mockups/<variant>/index.html` or `.planning/brainstorm/<option>.html`. 3. Push the active variant with `ijfw design push <file.html>`. The open browser reloads automatically. 4. When comparing options, create a tabbed `viewer.html` that loads option files from `/design/files/<name>.html`, then push the viewer and its option files together: `ijfw design push .planning/brainstorm/*.html`. Use the active `DESIGN.md` or the picked template as the source of truth -- real colors, real type scale, real spacing, real content. Prefer DESIGN.md tokens first, then the chosen template/brand direction, then internal heuristics. ASCII wireframes in chat are a LAST-RESORT FALLBACK, permitted only when: - The user explicitly asks for text-only ("just ASCII is fine"). - No writable filesystem is available (extremely rare -- almost never in practice). Do not default to ASCII boxes. Do not "sketch" in chat. The entire point of this skill is on-brand visual output; ASCII wastes the `DESIGN.md` contract, the palette, the type scale, and the user's time. Structural diagrams (Mermaid a...