unique

Generates visuals that are unique to the product they are for, and builds them on the right stack. Five skills: product-brief turns an idea into surfaces and capabilities; stack-route picks the best technology per capability against one shared byte and main-thread budget, with a platform-primitive-first rubric and a fidelity ladder for 3D, particles, data viz, editors, realtime and AI UI — every choice recorded with its rejected alternative and its fallback; frontend-design commits to a design contract that separates 'make it unique' (falsifiable originality gates, provenance tracing every color and typeface to a fact about the subject) from 'as good as Stripe' (borrow the craft bar, never the look) from 'match our system'; a spectacle doctrine decides when 3D, shaders, particles and ambient motion are actually earned — every effect must reveal a mechanism, respond to the person, or repay attention, priced by visit frequency, derived from the subject's own verb and specified with a mapping, a degrade path and a cut line; build-surface implements semantics and states before the happy path, with heavy capabilities behind a lazy boundary; ship-audit verifies Core Web Vitals, WCAG 2.2 AA, the state matrix and the bundle budget before anything is called done. Design is judged on the rendered page, not on its source: both frontend-design and ship-audit serve the surface, screenshot it at 390/768/1440 and score seven weighted axes against the images — composition, type, color, density, usability, signature and content, weighted into one 0-10 total under a jury-shaped profile for expressive surfaces and a usability-led one for product surfaces, reporting 'not rendered' rather than a verified design when no browser is available. Landing pages get their own doctrine — the page as an argument, a hero taxonomy, proof that is real or absent, and the tightest performance budget in the plugin — and a repertoire of named devices on five axes — composition, type, color and material,

5 skills · 6 commands