设计与多媒体

ss-update

bitjaru/styleseed

Check and update an existing StyleSeed installation by exact rule/skill revision, preserve project-owned design decisions, then recompile and verify the effective bundle.

  • 849 次安装
  • 992 星标
  • 收录于

安装命令

npx skills add https://github.com/bitjaru/styleseed --skill ss-update

SKILL.md

Before this workflow, follow the once-per-session update preflight.

StyleSeed update

Registry-first artifact boundary

When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested artifact ID first, then read only .styleseed/bundles/<artifact-id>.md and .styleseed/manifests/<artifact-id>.json. Never fall back to the global legacy bundle for a registry project. Legacy projects may use .styleseed/effective-rules.md only when no registry exists.

Update the engine payload, not the user's product UI. A release version describes a published line; engineRevision identifies the exact maintained rules, skills, entry docs, and palette engine. Two installs with the same release version are not proven equal until their revisions match.

The checker verifies the payload for the active install channel. A repository/plugin checkout uses the full core inventory; a project-local Agent Skills install uses the executable skills inventory. The published endpoint must expose both the engine revision and, for a skills-only install, skillsRevision. The project manifest continues to record the engine revision that compiled its method bundle.

Before this workflow, follow the once-per-session update preflight.

StyleSeed update

Registry-first artifact boundary

When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested artifact ID first, then read only .styleseed/bundles/<artifact-id>.md and .styleseed/manifests/<artifact-id>.json. Never fall back to the global legacy bundle for a registry project. Legacy projects may use .styleseed/effective-rules.md only when no registry exists.

Update the engine payload, not the user's product UI. A release version describes a published line; engineRevision identifies the exact maintained rules, skills, entry docs, and palette engine. Two installs with the same release version are not proven equal until their revisions match.

The checker verifies the payload for the active install channel. A repository/plugin checkout uses the full core inventory; a project-local Agent Skills install uses the executable skills inventory. The published endpoint must expose both the engine revision and, for a skills-only install, skillsRevision. The project manifest continues to record the engine revision that compiled its method bundle.