ss-update

Detect outdated StyleSeed engine files and update them while preserving custom code and assets.

22|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/izzoa/polyrouter --skill ss-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-update
Source: https://github.com/izzoa/polyrouter/tree/main/.agents/skills/ss-update
Command: npx skills add https://github.com/izzoa/polyrouter --skill ss-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify outdated StyleSeed engine files in a project and update them safely without overwriting your custom app code, theme, or components.

Core Features & Use Cases

  • Setup detection: Finds StyleSeed files such as DESIGN-LANGUAGE.md, CLAUDE.md, .cursorrules, theme.css, and installed skills.
  • Safe engine updates: Copies new engine skills and supporting rules while preserving existing project-specific work.
  • Guided review flow: Compares local and upstream versions, reports what changed, and asks before any higher-risk documentation updates.
  • Use case: A team upgrading an older StyleSeed installation can quickly learn what is stale, what is safe to merge, and what should be reviewed manually.

Quick Start

Ask the assistant to update the StyleSeed engine in the current project and report which files are outdated before making any changes.

Frequently Asked Questions about ss-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely update engine configuration files without overwriting custom code?

To safely update engine configuration files, you need a guarded merge process that compares local and upstream versions, preserving custom app code and design assets while applying new rules. This ensures controlled upgrades without losing project-specific work.

What is the best way to synchronize outdated skills and rules in a project?

Synchronizing outdated skills and rules requires detecting installed engine files, comparing their versions against upstream sources, and copying new engine skills while preserving existing configurations. A guided review flow reports changes before applying higher-risk documentation updates.

How do I detect which project files are outdated before performing a migration?

Detecting outdated project files involves scanning for specific engine files like DESIGN-LANGUAGE.md, CLAUDE.md, .cursorrules, and theme.css. The detection process compares local versions with upstream sources to identify stale files before any changes are made.

Can I upgrade my design engine without losing my theme.css and components?

Yes, you can upgrade a design engine without losing theme.css and components by using a guarded merge strategy. The update process explicitly preserves design assets and custom app code while only copying new engine skills and supporting rules.

What are the limitations of automated skill synchronization for documentation files?

Automated skill synchronization for documentation files requires manual review for higher-risk updates. While the process can detect outdated files and copy new engine skills, it asks for confirmation before merging documentation changes to prevent unintended overwrites.

Does the StyleSeed update process work with existing .cursorrules and CLAUDE.md files?

Yes, the StyleSeed update process works with existing .cursorrules and CLAUDE.md files by detecting them during setup. It compares local and upstream versions, reports what changed, and asks before applying any higher-risk documentation updates.