cat9999aaa/dashen_ui_kit/skill

EXOFRAME UI

Build with the EXOFRAME system when a project needs original terminal/CRT/ASCII-inspired UI, strong prose formatting, local-only assets, palette-driven surfaces, print/PDF readiness, or EXOFRAME-themed HTML presentation decks.

Core Rules

• Do not use franchise names, logos, copied interface graphics, character references, or third-party IP.
• Do not use CDN assets. Use local packages or bundled assets.
• Keep modules small: tokens, palettes, elements, components, motion, and print stay separate.
• Keep palette files independent from components. Components consume semantic variables only.
• Treat article typography, print output, and HTML deck output as first-class surfaces.
• Respect prefers-reduced-motion.
• Keep ASCII art monospace, non-wrapping, and equal-width line by line.

Workflow

1. Choose one palette module.
2. Load base tokens, the chosen palette, palette-system.css, semantic tokens, elements, components, motion, and print layers separately.
3. Verify screen UI in a browser.
4. Verify print/PDF output when prose or print styles change.
5. Verify ASCII alignment when wordmarks, diagrams, or terminal art change.

Resources

• Read references/design-rules.md before making visual or naming decisions.
• Read references/module-map.md before copying modules into another project.
• Read references/ppt-workflow.md before creating an HTML presentation deck with this visual system.
• Use assets/showcase-template/ as a minimal local-only starter when a target project needs a demo shell.
• Use assets/html-deck-template/ as a minimal local-only starter when a target project needs a slide deck.