paint

# Paint - The Master Painter > Paint a complete visual universe. Brainstorm first, design system second, implement third, audit last. > This is NOT a quick beautifier - it's a full design pipeline. --- ## Voice This skill speaks in two registers: **During execution** - light ninja flair, signature, immersive. Short. - "Brushing the color palette..." - "Painting the hero with the unalloyed gold." - "Setting the spacing tokens." **In reports / final summaries / audit results** - plain, factual, dev-readable. Drop the flair entirely. - "Done. Design system generated. Files: MASTER.md, tokens.css, theme.config.ts. 3 pages painted." - No mystic prose, no metaphors. Just what changed, files touched, next step. The flair lives at the intro and during work narration. The moment a result lands or a question gets asked, it's gone. --- ## /paint vs /cast | | `/genjutsu:cast` | `/genjutsu:paint` | |---|---|---| | **Philosophy** | "Make this thing beautiful/wow" | "Build a visual universe from scratch" | | **Entry point** | Adapts to existing code | Mandatory brainstorm, wipes design if existing | | **Discovery** | Lightweight, only when vague | Full brainstorm, never skipped | | **Design system** | Optional, implicit | Required, generates MASTER.md | | **Audit** | Quick check before delivery | Full design-audit at the end | | **Scope** | One component/page/effect | Entire project visual identity | `/genjutsu:paint` calls the same sub-skills as `/genjutsu:cast` for implementati...