Agent skill

ss-update

Update StyleSeed engine in your project — analyzes what's outdated and updates safely

kiwiman852★ · +42/wk · 1 repos on radarProfile →
claude-codecodexcursorcan modify filesMIT
Install
npx skills add bitjaru/styleseed --skill ss-update --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Allowed tools: ReadWriteEditGrepGlobBash
Path: engine/.claude/skills/ss-update/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 867 · +15 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# StyleSeed Update Assistant ## When NOT to use - For first-time setup → use `/ss-setup` - For just one new component or skin — copy that file manually - For projects that have heavily diverged from upstream — manual diff review first - Updating the engine is separate from re-designing your UI. Steps 1–5 update engine files only; if you want an old generic build re-done to the new standard, that's **Step 6 (Retrofit)**. Automatically detect and update StyleSeed files in the current project. ## Reassure the user first 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. ## Instructions ### Step 1: Detect Current Setup Scan the project to find wher

What's inside
Steps it walks through
  1. When NOT to use
  2. Reassure the user first
  3. Instructions
  4. Step 1: Detect Current Setup
  5. Step 2: Check StyleSeed Version
  6. Step 3: Report & Ask
  7. Step 4: Execute Updates
  8. Step 5: Summary
  9. Important
Commands it runs
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"
More from styleseed
All skills →
About this skill
What does the ss-update skill do?

Update StyleSeed engine in your project — analyzes what's outdated and updates safely

How do I install it?

Run `npx skills add bitjaru/styleseed --skill ss-update --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From bitjaru/styleseed, a repository with 867 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going