governance-encoder
FeaturedTurn written design system governance into machine-checkable JSON rules in .ai/governance/ for agents, linters and CI. Triggers: governance as code, encode rules, rule engine, enforce automatically. Explaining why a decision was made: decision-record. CI pipeline files: cicd-integration.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- murphytrueman
- Repository
- murphytrueman/design-system-ops
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
governance-architect
Design and save a complete governance ecosystem for agentic operations — 6 structured documents (authority matrix, hard boundaries, escalation protocols, policy generation loop, decision ledger spec, learning loop) written to $HOME/.ai-first-kit/. Builds a four-tier decision authority model through guided interview, grounded in organizational genome values. Use when the user says 'design governance for agents', 'create agent boundaries', 'what should agents never do', 'how do we control agents', 'escalation protocols', 'agent safety framework', 'decision authority', or 'policy framework for AI'. Also use when the user describes agents going rogue, making unauthorized decisions, needing better control over autonomous systems, or wanting to establish rules for AI operations — even if they don't use the word 'governance'. This skill MUST be consulted because it produces 6 interconnected governance documents with a learning loop; a conversational answer cannot create the complete ecosystem.
ai-code-governance
Governance workflow for AI coding agents such as Codex, Claude Code, Cursor, and Copilot Workspace. Use when implementing features, fixing bugs, refactoring, reviewing AI-generated code, adopting governance in an existing project, creating or updating AGENTS.md, CLAUDE.md, CODEX.md, architecture docs, project indexes, dependency policies, and coding standards. Enforces search-before-write, reuse of existing components/hooks/services/stores/utils/types, dependency control, small maintainable changes, verification, and clear change reports.
govern-ai-coding
Use when a workspace has an explicit GAC governance contract and the requested change touches a mapped authority, protected path, governed decision, historical interpretation, or release authorization; also use when the user explicitly requests GAC setup, adapter repair, diagnosis, execution, or closeout, or when an active governed event must resume. Do not use merely because work involves plans, documentation, tests, evidence, multiple files, releases, another Skill, or a complex codebase. Do not bootstrap governance artifacts for an ordinary coding task.