ss-build — StyleSeed Screen Build Workflow

A disciplined build workflow that resolves the StyleSeed rule set before any code, then forces the screen through a code-score gate and a pixel-verification gate before it can be presented.

Design & UIAdvanced★ 968⑂ 89AI score 7/10Last updated: Sep 29, 2026

What it does

Registry-first resolution: when .styleseed/project.json and artifacts/index.json exist, it resolves the artifact ID and reads only that artifact's bundle and manifest — no silent fallback to the legacy global bundle.
Requires a one-line statement of the effective rule set before coding, e.g. operations-console × SaaS × dashboard × enterprise-workbench × swiss × locked brand tokens.
Builds against the grammar's contracts (composition, density, type, color, surface, action, state, responsive, motion) plus the brand recipe's morphology, including loading/empty/error/focus/reduced-motion states.
Code gate loop with /ss-score: at most three correction passes, early stop at ≥80; a failed, skipped or unexecuted required functional scenario blocks completion regardless of score.
Pixel gate loop with /ss-verify across required viewports; if no renderer exists it must declare the visual gate skipped rather than imply a pass.

Who it's for

Frontend and product engineers already running the StyleSeed design engine.
Teams that want AI-built UI to pass measurable quality gates instead of shipping improvised layouts.
Organizations enforcing locked brand tokens and consistent design grammar across screens.

Example uses

"Build the operations console dashboard" → resolve the artifact, declare the rule set, implement, score with /ss-score, verify with /ss-verify, then report with evidence.
Rebuilding a settings page → name required outcomes first ("a saved setting survives reload", "a failed save preserves the draft") and prove them with the project's real test runner.
Legacy project with no STYLESEED.md → run /ss-setup first, then write UI code under the resolved rules.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/bitjaru/styleseed/HEAD/engine/.claude/skills/ss-build/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the engine/.claude/skills/ss-build folder from the GitHub repo bitjaru/styleseed into my ~/.claude/skills/ss-build/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/bitjaru/styleseed.git && mkdir -p ~/.claude/skills && cp -r styleseed/engine/.claude/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

Open a terminal.
Clone the repository: git clone https://github.com/bitjaru/styleseed.git
Create the skills directory: mkdir -p ~/.claude/skills
Copy all engine skills: cp -r styleseed/engine/.claude/skills/* ~/.claude/skills/
- ss-build uses relative references to ss-setup, ss-resolve, ss-score, ss-verify and ss-update, so copy the whole folder rather than a single file.
Restart Claude Code, open your project root, and invoke /ss-build <what to build>.
For a brand-new project, run /ss-setup first so a .styleseed/ registry or STYLESEED.md lock exists before UI work.

View source on GitHub ↗License: MIT