ss-update

# 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 where StyleSeed files are: ```bash # 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 "*/.c...