Ss reference
Open-source design-method engine for Claude Code, Codex & Cursor. Gives coding agents fixed design judgment—not one fixed aesthetic—then selects or derives the right grammar from references, locks project decisions, and verifies UI, carousels, decks & docs. 20 skills · MIT.
npx -y skills add bitjaru/styleseed --skill ss-referenceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Compile screenshots, URLs, Figma exports, or an existing UI into a project-local StyleSeed output grammar with evidence, tokens, confidence, anti-patterns, and a validation screen. Use when the user supplies a design reference that StyleSeed does not already model.
SKILL.md
2.2 KB, as published. Nobody here has run it
Compile references into a design grammar
Do not merely imitate the supplied screen. Read PRODUCT-PRINCIPLES.md, RULESETS.md,
ADAPTERS.md, and REFERENCE-COMPILER.md, then execute the compiler pipeline in full.
Workflow
- Ingest every supplied reference and assign evidence IDs (
R1,R2, ...). If a URL can be rendered, capture it. If an image cannot be seen, stop claiming visual analysis for it. - Separate references by surface adapter and job. Do not merge a marketing homepage with an app dashboard unless the user explicitly wants both languages connected.
- Observe and measure the twelve axes. Every rule cites evidence IDs and a confidence level.
- Resolve contradictions instead of averaging them. Explain any material choice briefly.
- Choose the nearest built-in fallback grammar and adapter, then compile the project artifacts required by
REFERENCE-COMPILER.mdunder.styleseed/rulesets/<slug>/. - Update
STYLESEED.mdto selectreference:<slug>while preserving bounded brand choices. - Validate transfer: apply the grammar to one representative screen not present in the source
set, run
/ss-score, then/ss-verifyif renderable. Fix and repeat to the gate floor. - Report what was learned, what remains low-confidence, where the artifacts live, and the validation result.
Rules
- Visible evidence before adjectives. “Calm” is not a rule; the spacing, type, color, hierarchy, and motion decisions that create calm are rules.
- Never copy protected assets, brand marks, or prose.
- One reference produces a provisional grammar. Say so and keep confidence low where warranted.
- The generated grammar is project-local. Do not edit
RULESETS.mdor publish it as built-in. - Core invariants and accessibility remain non-negotiable.