🧩
AI EngineeringHTML

Governance Encoder

by murphytrueman

Governance Encoder is an AI Engineering skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22
claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills
Install in seconds
Install Governance Encoder
Copy Governance Encoder into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/governance-encoder ~/.claude/skills/governance-encoder

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/governance-encoder/SKILL.md in murphytrueman/design-system-ops
Installs to
~/.claude/skills/governance-encoder
Collection
One of 25 skills cataloged from this repository
Category
AI Engineering3475 skills

What Governance Encoder does

Governance Encoder converts governance policies into machine-checkable JSON or YAML constraint files for AI agents and CI pipelines. Use it when you need to encode rules, not write decision records or documentation.

Governance Encoder is cataloged under AI Engineering on DirSkills. Governance Encoder comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Governance encoder

A skill for converting design system governance policies — the rules about how the system should be used, contributed to, and evolved — from human-readable documentation into machine-executable constraint definitions that AI agents validate against in real time.

Context

Most design system governance lives in documents that humans read and (sometimes) follow. Contribution guidelines in a wiki. Naming conventions in a README. Token usage rules in a Slack thread from eighteen months ago. These rules are enforced by review — a senior team member spots a violation during a PR review or a design crit and asks for a correction.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Governance Encoder

  • What else does murphytrueman publish alongside Governance Encoder?

    Governance Encoder is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Governance Encoder does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.

  • How does Governance Encoder compare to other AI Engineering skills?

    Governance Encoder ranks #3161 by stars among the 3475 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Governance Encoder against them. Open each page to compare what they document and how they install.

More from murphytrueman/design-system-ops

Governance Encoder is one of 25 skills cataloged on DirSkills from murphytrueman/design-system-ops.

See all 25 skills
🤖
2h ago

AI Component Description

AI Component Description generates six-section prose descriptions for components so LLMs can understand purpose, props, composition, accessibility, and examples. Use it when writing Figma MCP descriptions or other text meant to make components legible to Claude and similar agents.
AI Engineering
1767
2h ago

Accessibility Per Component

Accessibility Per Component runs a structured accessibility audit on a single design system component. It checks keyboard use, screen reader behavior, colour contrast, focus, and ARIA against WCAG 2.1 AA.
Quality
1767
📈
2h ago

Adoption Report

Adoption Report separates design system coverage from actual adoption, with trend direction and risk flags. Use it when you need to measure which teams are using the system and where usage is low or declining.
Data
1767
🗂️
2h ago

Backlog Generator

Backlog Generator turns audit findings into sprint-ready work items with titles, effort estimates, acceptance criteria, and rationale. Use it when you need to convert review output into actionable tickets instead of running an audit or defining contribution guidelines.
Automation
1767
⚙️
2h ago

CI/CD Integration

CI/CD Integration generates pipeline files that automate design system checks such as token validation, component linting, accessibility scans, visual regression, and release gating. Use it when you need CI to enforce the same rules audit skills check manually.
DevOps
1767
📣
2h ago

Change Communication

Change Communication produces release notes, migration guidance, and team announcements for design system changes that have already been decided. Use it when you need to communicate a patch, enhancement, breaking change, or system update to consuming teams.
Writing
1767