governance

Skill: Governance

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.

Steps

1. Read ${CLAUDE_SKILL_DIR}/../../../workflows/governance.md (SemVer table, contribution workflow, deprecation policy, change comms).
2. Classify the change: major (breaking: renamed/removed token or prop, changed anatomy/default), minor (additive: new token/component/variant/optional prop), patch (fix: contrast/bug/doc/value tweak in tolerance).
3. For a new component/token: confirm it serves a real, repeated need (≥ 2 places) before promoting product → candidate → core. Design it to the full quality bar (${CLAUDE_SKILL_DIR}/../../../.claude/rules/components.md → Component Quality Bar).
4. For a deprecation: mark with reason + replacement + removal version; keep working ≥ 1 minor cycle; provide a migration map (${CLAUDE_SKILL_DIR}/../../../design-systems/crosswalk.md style); remove only in a major.
5. Wire any new file into CLAUDE.md (File Reference Map + relevant table/router) and add a changelog entry.

Skill: Governance

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.

Steps

1. Read ${CLAUDE_SKILL_DIR}/../../../workflows/governance.md (SemVer table, contribution workflow, deprecation policy, change comms).
2. Classify the change: major (breaking: renamed/removed token or prop, changed anatomy/default), minor (additive: new token/component/variant/optional prop), patch (fix: contrast/bug/doc/value tweak in tolerance).
3. For a new component/token: confirm it serves a real, repeated need (≥ 2 places) before promoting product → candidate → core. Design it to the full quality bar (${CLAUDE_SKILL_DIR}/../../../.claude/rules/components.md → Component Quality Bar).
4. For a deprecation: mark with reason + replacement + removal version; keep working ≥ 1 minor cycle; provide a migration map (${CLAUDE_SKILL_DIR}/../../../design-systems/crosswalk.md style); remove only in a major.
5. Wire any new file into CLAUDE.md (File Reference Map + relevant table/router) and add a changelog entry.