ss-build

# Build with the composed StyleSeed method The build method is the product. Score and screenshots are auxiliary evidence, not the source of design judgment. ## Step 1 — Establish the rule set before code Read `PRODUCT-PRINCIPLES.md` and `ADAPTERS.md`. If `STYLESEED.md` exists, validate its values and referenced grammar. If it does not, run `/ss-setup` and write it before UI code. If the user supplied a visual reference that the selected built-in grammar does not capture, run `/ss-reference` first. Never reduce an unfamiliar reference to a palette swap. ## Step 2 — Compose, do not improvise Read and combine in authority order: 1. core invariants in `PRODUCT-PRINCIPLES.md`; 2. selected built-in grammar in `RULESETS.md`, or compiled `RULESET.md`; 3. selected surface adapter in `ADAPTERS.md` and its companion renderer contract; 4. matching `APP-PLAYBOOKS.md` domain and `PAGE-TYPES.md` page/artifact type; 5. optional aesthetic profile in `PRESETS.md`; 6. bounded values in `STYLESEED.md`; 7. detailed craft in `DESIGN-LANGUAGE.md` and `VISUAL-CRAFT.md`. Before code, state the effective rule set in one line, for example: ```text operations-console × SaaS × dashboard × swiss × locked brand tokens ``` Resolve conflicts by authority. A profile or lock cannot waive task fitness, coherence, or accessibility. ## Step 3 — Build with design judgment - Make the grammar's user job and primary decision visible in the first viewport. - Establish one focal point; avoid equal-weight te...