styleseed

StyleSeed

Make expert design judgmentrepeatable by coding agents.

StyleSeed turns recorded design decisions into project-local rules and implementation workflows. Support experts, not replace them with a collection of tastes. Open source, for Claude Code · Codex · Cursor.

Same product. Same prompt. Only the rules changed.

Measured on 120 rendered benchmark cells: the enforced gate improved both Codex and Claude Code by +5.3 points. Raw rules alone were inconsistent (Codex +1.6, Claude Code −3.7), which is why StyleSeed ships a render → score → revise loop—not a prompt dump. Read BENCH-V1 and inspect the raw evidence →

Easy Start (30 seconds)

Our goal is repeatable application of expert judgment, not a claim of expert-level output today. The engine compiles selected rules, preserves project choices, and supports code and rendered checks. A score does not replace human design acceptance. Product principles · Quality-first roadmap

1. Open your project in Claude Code, Codex, Cursor, or another coding agent.

2. Paste this message:

Install StyleSeed with `npx skills add bitjaru/styleseed`, then set it up for this project. Help the agent repeat our design decisions, not replace our design system. First inspect approved tokens, components, and project choices; report unsupported choices instead of silently remapping them. Ask what I am building and only the unresolved decisions you need. Choose a supported output grammar, brand recipe, and semantic palette—or derive a local grammar from my references. For creative exploration use `/ss-studio` in Claude Code or `$ss-studio` in Codex and pause for my selection. Otherwise resolve the approved direction with `/ss-resolve` or `$ss-resolve`, implement, score to at least 80, and inspect the rendered result. Report evidence and remaining human decisions; do not treat a score as my approval.

3. Approve the install, answer the short setup questions, and describe what you want to build. The invoked workflow handles the design lock, build, code gate, and visual check. Bring existing design decisions when you have them; review proposed choices when you do not.

Agent	If you want to run it manually
Claude Code	/ss-studio for exploration, or /ss-setup → /ss-build for a decided screen
Codex	$ss-studio for exploration, or $ss-setup → $ss-build from /skills
Cursor and others	Paste the message above or use the installed skill picker

Claude Code guide · Codex guide · See examples · Need help?

Evaluating the repository?

Use the three-minute verification path to test a clean public install before trusting the README. The source-level evaluator quickstart then connects that install to the published release manifest, Windows PowerShell evidence, CI, SBOM, benchmark boundary, and production build.

Want a first PR? Fix a doc, add a regression fixture, improve a skin, or claim a good first issue. Small docs and test fixes need no proposal. See the 15-minute contribution path.

What the current rules check

StyleSeed ships 74 craft rules and a 0–100 scored gate that tells an installed agent to revise screens below 80 before presentation. Checks must be interpreted through the selected grammar and project contract, not as universal taste. The workflow must actually be invoked; a markdown file alone cannot block delivery, and 80 points is not expert approval.

Check	Why
Unselected default accent	require an intentional, recorded color role
Emoji as UI icons 🚗 🧺 ⭐	inject random colors, render differently per OS
The icon-in-a-chip above every feature card	gen-1 AI tell — decoration pretending to be information
All-even grid of same-weight centered cards	the #1 machine-composed tell: no focal point
Accidental flat-black backgrounds	use the selected grammar's surface model; explicit supported exceptions differ
Type sizes outside the selected scale	prevent unintentional hierarchy drift
Hardcoded hex in components	tokens only — otherwise the lock can't hold across screens

Banning the defaults isn't enough — agents converge on new uniforms once the old ones are blocked. That's why the rules come with an enforced score-then-fix loop, not a checklist. What happens after install ↓

One component. Three token skins. Same chat UI morphing across Toss · Raycast · Arc-inspired token sets. A skin changes color and type material; a StyleSeed brand recipe changes the actual geometry, containment, controls, collections, density, and motion.

Skins are inspired-by token sets, not recreations. Compare the nine structural recipes →

 

Expert decisions become repeatable instructions — not one universal aesthetic.

Judgment with implementation context — decisions, applicability, and evidence, not just palettes  ·  Right grammar for the result — consumer service, operations, technical, editorial, commerce, institutional, marketing, or sequential story  ·  Real morphology choices — nine brand recipes change structure and component selection, not just palette  ·  Generative palette engine — any key color becomes OKLCH ramps, context-fit surfaces, a scored companion, semantic roles, contrast evidence, CSS tokens, and media anchors; eight recipes remain maintained product postures  ·  Studio pipeline — three directions, human selection, interaction scenes, image/video jobs, working prototype, and a prototype-first reel  ·  References become rules — /ss-reference compiles screenshots, URLs, Figma, or an existing UI into an evidence-backed project grammar  ·  Only the context you need — /ss-resolve compiles the chosen method into a small, hash-verifiable project bundle  ·  Beyond web UI — adapters for product UI, social carousels, decks, documents, and graphics  ·  Fights the AI tells — the default indigo, the icon-chip cliché, template layouts, rainbow lists  ·  Auxiliary proof gates — code score + rendered pixel verification before you see it  ·  Every agent — ships CLAUDE.md + AGENTS.md + .cursorrules  ·  A design lock that stops drift  ·  Free & MIT

Core judgment × output grammar × surface adapter × domain/page × brand recipe × palette recipe × optional profile. Read the architecture →

Full pages: before · after · more before/afters →

🔥 We ran an early version of this page through our own gate. It scored 58/100 → here's the receipt

Same product, six looks — each one /ss-restyle <preset> away. Coherent, distinct, never generic.

Easy Start · Studio · Palettes · Claude Code UI guide · Codex UI guide · Brand recipes · Architecture · Engine + Recipes + Skins · Motion · Skills · Wiki · 한국어

---

What happens after Easy Start

Why the prompt installs first: the context compiler and quality gates can only run when the skills are installed. Installing turns STYLESEED.md into a small source-hashed rule bundle, then actually scores and fixes the result before you see it. Without installation, llms.txt still tells any agent how StyleSeed is structured and where its machine-readable catalog lives, but compilation and gates become a weaker manual path. Works with Claude Code (CLAUDE.md), Codex / Amp / Gemini CLI (AGENTS.md), and Cursor (.cursorrules) — StyleSeed ships all three. (Planning first is what keeps the result from looking random — see Troubleshooting.)

What your agent actually does with StyleSeed loaded: