The single biggest reason a StyleSeed build lands *generic* when the reference demo (styleseed-demo.vercel.app) looks *designed* is **not missing rules — it's a skipped process.** The demo went through: lock the look → build → run the Quality Gate → fix to a floor → repeat. A free-hand bui

Target: **$ARGUMENTS**

Guide the user through setting up StyleSeed for their project, step by step.

Action: **$0** | Token type: **$1** Arguments: $ARGUMENTS

Create a new page: **$0** Description: $ARGUMENTS

A mood word — "make it more editorial", "give it a Swiss feel" — is **not one axis**. It's a defined *position across several* (this radius **and** that density **and** that color temperature **and** that weight **and** that motion), tied together with a font and one signature move. Left to plai

Audit a component or page for accessibility issues and fix them

Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices

Add appropriate user feedback states (loading, success, error, empty) to a component or page

Review UI code for design system compliance, accessibility, and best practices

Automatically detect and update StyleSeed files in the current project.

Generate a new component: **$0** Description: $ARGUMENTS

Pattern type: **$0** Description: $ARGUMENTS

Audit a component or page for accessibility issues and fix them

Design a user flow: **$0** Description: $ARGUMENTS

Add appropriate user feedback states (loading, success, error, empty) to a component or page