菜单
Update StyleSeed engine in your project — analyzes what's outdated and updates safely
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The VISUAL gate — render the UI, screenshot it, and score what you actually SEE, not what the code says. Catches the tells that only show up in pixels (dead whitespace, cramping, a hero that doesn't dominate, fonts that didn't load, real rendered color, the squint "does this look AI-made" test) — the things /ss-score can't read from source. Renders empty/loading/error states too, then fixes and re-renders until it passes. Use as the final gate on any screen you can render.
Turn ONE design axis up or down as a coordinated, deterministic transform — "denser", "sharper corners", "more muted", "bolder", "flatter", "livelier". Not a vibe the model reinterprets each time; a defined ramp that moves many tokens together, respects the guardrails (8px grid, a11y floors, single accent, nested-radius), updates the lock, and re-runs the gate. Use this when a human saying "more X" would otherwise get an inconsistent one-off.
Apply a named StyleSeed motion to a component — either one of the 5 personality seeds (Spring/Silk/Snap/Float/Pulse × entrance/exit/hover/press/layout) or a distinctive keyword move from the motion library (toggle-flip, toggle-curtain, reveal-blur, pop-in, shimmer, …). Translates vibe words into framer-motion code from one source of truth.
Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of /ss-review.
Re-style a project to a named aesthetic — swiss, editorial, technical, warm-dtc, minimal-mono, brutalist-lite. A preset is a *coordinate* across the dial axes (radius + density + color + weight + motion) plus a font, accent family, and one signature move — applied coherently as a single identity, written to the lock, and re-gated. This is for mood words ("more editorial") that aren't one axis; for a single axis use /ss-dial.
Build a screen the way the StyleSeed reference demo was built — one command that ENFORCES the full loop (lock the look → build → score → fix to ≥80 → only then show). Use this instead of building UI free-hand; it closes the gap between "knows the rules" and "actually followed them."
| name | ss-update |
| description | Update StyleSeed engine in your project — analyzes what's outdated and updates safely |
| argument-hint | (no arguments needed) |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash |
/ss-setupAutomatically detect and update StyleSeed files in the current project.
Updating is safe and reversible. Updates are additive — new rules,
components, skins, and skills get added; your theme.css, your components, and
your app code are never overwritten, and design rules only ever get added (never
changed in a breaking way). A big version jump looks like a lot changed, but
it's almost all additions. Do NOT warn the user that the build will break
unless you actually find a changed component/import API. Tell them: commit first,
copy the new rules + skills, run a build, and git reset --hard if anything is
off — they can't permanently break their project.
Scan the project to find where StyleSeed files are:
# Find DESIGN-LANGUAGE.md
find . -name "DESIGN-LANGUAGE.md" -not -path "*/node_modules/*"
# Find CLAUDE.md
find . -name "CLAUDE.md" -not -path "*/node_modules/*"
# Find skills (ss-* is current; ui-*/ux-* are legacy names to migrate from)
find . -path "*/.claude/skills/ss-*" -o -path "*/.claude/skills/ui-*" -o -path "*/.claude/skills/ux-*" | head -20
# Find theme.css
find . -name "theme.css" -not -path "*/node_modules/*"
# Find .cursorrules
find . -name ".cursorrules"
Report what was found and where.
Fast check first — compare the local version to the published one without cloning:
# local marker (may be absent on older installs)
cat engine/VERSION 2>/dev/null || cat VERSION 2>/dev/null || echo "unknown"
# latest published version + what's new
curl -s https://styleseed-demo.vercel.app/version.json
If the local version already matches version.json's version, tell the user they're
up to date and stop. Otherwise report whatsNew and continue.
Then clone/pull to actually diff the files:
if [ -d "/tmp/styleseed" ]; then
cd /tmp/styleseed && git pull
else
git clone https://github.com/bitjaru/styleseed.git /tmp/styleseed
fi
Compare:
engine/VERSION (or version.json) vs the local copy — the source of truth.claude/skills/ vs upstream (don't hardcode a count — list the diff)CLAUDE.md, AGENTS.md, and .cursorrules exist (ship all three)Show the user what needs updating:
StyleSeed Update Report:
Current state:
- DESIGN-LANGUAGE.md: [location] — [old/current version indicator]
- Skills: [count] found (latest: 12)
- Golden Rules: [yes/no]
- .cursorrules: [yes/no]
Recommended updates:
1. ✅ [safe] Update skills (X → 12)
2. ✅ [safe] Add .cursorrules
3. ⚠️ [review] Update DESIGN-LANGUAGE.md ([old line count] → [new line count])
4. ⚠️ [merge] Add Golden Rules to CLAUDE.md (won't overwrite existing content)
Shall I proceed? (I'll ask before each ⚠️ item)
For each update, in order:
Always safe (do without asking):
cp -r /tmp/styleseed/engine/.claude/skills/ .claude/skills/cp /tmp/styleseed/engine/.cursorrules .cursorrulesAsk before doing:
For DESIGN-LANGUAGE.md:
For CLAUDE.md (Golden Rules):
Never touch:
/ss-lint to check compliance."Update complete!
✅ Skills: 12 (added X new)
✅ .cursorrules: added
✅ DESIGN-LANGUAGE.md: updated to latest
✅ Golden Rules: added to CLAUDE.md
Not touched:
- theme.css (your skin)
- components/ (your code)
Next: run /ss-lint on your pages to check for rule violations.
Updating the rules doesn't re-design screens you already built with an older StyleSeed. If the user says their existing UI still looks generic/"AI-made" (default indigo, icon-chip cliché, tight desktop type, no focal point, no design lock), offer to retrofit it to the new standard. This is the migration path for anyone who built before the distinctiveness rules existed:
STYLESEED.md at the project root. If absent,
run Quick Setup (CLAUDE.md) now with the user — pin mood (edges/feel/density/tone),
a domain-fit key color (NOT the default indigo), a chosen font, and the surface
(mobile vs desktop type scale). Write the lock. Existing generic builds almost always never
had a lock — this is the biggest fix./ss-score on the main pages. The new rubric flags
exactly the old-build tells: default-indigo accent, the icon-chip cliché (§CC-9b), body <16px
on desktop, no focal point, demo layout copied verbatim, missing states./ss-review (or /ss-review --fix) screen by screen to retint to
the locked key color, replace the uniform icon chips, bump the desktop type scale, and create a
focal point. Re-score to ≥ 80. Do the highest-traffic screen first.Frame it honestly: the rules got stronger, so a screen that passed the old bar may score lower now — that's the point; fixing it is what makes it stop looking AI-made.