paint

Run the paint pipeline, which brainstorms product, audience, mood, references, and stack, then validates a visual and interaction thesis before generating a MASTER.md design system. Tokens are emitted as Tailwind config or CSS variables for web, Kotlin theme files for Compose, or Swift extensions for SwiftUI.

Paint builds an entire visual universe from scratch with a mandatory brainstorm and a generated design system, while cast adapts existing code with lightweight discovery and no required design system file. Use cast for single components or effects and paint for whole-project identity.

Yes, it detects SwiftUI via Package.swift or xcodeproj files and Compose via Gradle dependencies, then generates platform-native tokens such as Color+App.swift or Theme.kt. It also handles Compose Multiplatform with expect/actual token structures.

Only light scope shortens the pipeline, and only when the target is one isolated component with an existing visual identity and no downstream systematization. Even then, one brainstorm question, an interaction thesis, and validation gates remain mandatory.

The audit verifies reduced-motion support, presence of exit animations, and stack-specific accessibility and performance rules before delivery. It runs on every project regardless of scope and cannot be skipped.