agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/design-system-governance/SKILL.md

design-system-governance

Skill32 starsChanged 6 months agoMITView on GitHub

Define how a design system evolves: ownership models, contribution lifecycle, semantic versioning as a contract, deprecation policy, and quality gates.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

design-system-governance

Catalogue stub — full skill: Owl-Listener/designer-skills

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/design-system-governance/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/design-system-governance/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as design-system-governance, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/design-system-governance ] && echo "global" || echo "project"

    Global:

    npx skills add Owl-Listener/designer-skills --skill design-system-governance -g -y

    Project:

    npx skills add Owl-Listener/designer-skills --skill design-system-governance -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add Owl-Listener/designer-skills
/plugin install design-systems@designer-skills

Heads-up

  • License: MIT
<!-- das:install:end -->

Invoke after install

  • Skill name: design-system-governance
  • Trigger phrases: "design system governance", "design system contribution model", "component versioning policy", "design system deprecation"

What it does

The Owl-Listener design-system-governance skill: the three ownership models (centralized / federated / hybrid) with trade-offs, the contribution lifecycle (request → triage → design → review → build → release → communicate), semver as a consumer contract, a deprecation process with migration guidance, and the quality bar a component must clear to enter the system.

When NOT to use

  • Authoring tokens themselves → use design-tokens-skill
  • Driving adoption of an existing system → use design-system-adoption (a separate skill in the same Owl-Listener repository; this stub does not install it)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free