For existing users
Same workflows.
One StyleSeed entry.
You can stop choosing between a long list of commands. The current core keeps 22 workflows inside styleseed. Your agent selects the one your task needs.
스킬이 너무 많이 보이나요? 기존 기능은 유지하고, 시작점은 styleseed 하나로 통합하세요. 아래 요청을 복사하면 업데이트와 옛 항목 정리를 함께 진행합니다.
Ask once. Finish the update.
Paste this into your coding agent where you already use StyleSeed. You do not need to remember the old skill names.
Read https://styleseed-demo.vercel.app/upgrade.md and update my existing StyleSeed installation through its current channel, agents, and project/global scope. Preserve my design decisions and any modified skill files. After installing, read the newly installed update workflow, back up and consolidate verified old skill entries, recompile only affected existing rule bundles, and verify the installed revision. Report remaining duplicates and the backup path. Do not redesign the application or switch a pinned version or release channel without my choice.Paste into your coding agent in the project where you use StyleSeed.
한국어 업데이트 요청 복사하기
https://styleseed-demo.vercel.app/upgrade.md 를 읽고, 기존 설치 경로·사용 에이전트·프로젝트/전역 범위를 유지해서 StyleSeed를 업데이트해줘. 내 디자인 결정과 직접 수정한 스킬은 보존해. 설치 후 새 업데이트 절차를 읽고, 원본과 일치하는 옛 스킬을 백업해서 통합한 뒤 필요한 기존 규칙 번들만 다시 만들고 설치 리비전을 검증해줘. 남은 중복과 백업 위치를 알려줘. 앱을 재디자인하거나 고정 버전·릴리스 채널을 임의로 바꾸지는 마.StyleSeed를 쓰던 프로젝트의 코딩 에이전트에 붙여넣으세요.
What your agent will do
- Find and update your existing installation. Keep the same agent, project or global scope, and release channel. A pinned version stays your decision.
- Back up and consolidate old entries. Reinstalling alone can leave old commands behind. The update checks each old entry and archives unchanged copies outside the skill list. Modified files stay in place for review.
- Check the result and restart the session. Refresh affected existing rule bundles and verify the installed revision. Your agent reports the backup location and any entries that still need attention. Start a fresh session to refresh the skill list.
Your application code, design tokens, and approved design choices remain yours. Updating StyleSeed does not redesign your screens.
Still seeing duplicate commands?
A plugin plus a separate CLI install can expose two copies. Your agent should identify both and help you choose one. Customized, linked, or unrecognized old entries are preserved rather than silently removed.
Stable release archives follow their own release schedule. This guide does not switch them to the latest development revision without your choice.
Will everyone get an update notice?
Versions with a session update check can recommend an update the next time you use StyleSeed. Very old or unused installations cannot receive a remote notice. Share this guide with teammates who still have the old list.