murphytrueman/design-system-ops

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.

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.

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.

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.

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.

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.

Codebase Index generates a machine-readable component inventory, relationship graph, and summary statistics for a design system codebase. Use it to create .ai/index files for navigation by AI agents and developer tooling.

Codemod Generator creates jscodeshift or AST-based transform scripts for design system migrations such as token renames, prop changes, import updates, and component replacements. Use it when you need to automate code changes across consuming codebases.

Component API Validator audits a component library's public props and types for consistency, breaking changes, and contract drift. Use it for prop reviews, TypeScript coverage checks, and cross-library API normalization.

Component Audit audits a design system component library for usage, complexity, duplication, and coverage gaps. Use it to assess what exists, what is unused, and where the library needs cleanup or expansion.

Component Decision Tree builds structured YAML decision trees that help agents choose the right component from alternatives. Use it when you need intent-to-component mapping and narrowing questions, not usage guidance for a single component.

Context Engine Builder generates structured blueprints for a design system’s UX, UI, content, accessibility, ethical, technical, and business context. Use it when you need AI-readable knowledge files for agents to understand and work with the system.

Contribution Workflow creates a staged process for evaluating, accepting, and shipping design system contributions. Use it when defining how new components, enhancements, or token changes move from proposal to release.

Decision Record creates a structured narrative document for design system choices, including context, options, trade-offs, and rationale. Use it when you need to capture why a decision was made for future reference.

Deprecation Process plans and executes the removal of a design system component, token, or pattern. It covers timelines, usage audit, migration guidance, communication, and phased removal when something needs to be replaced or retired.

Design To Code Check reviews a single component or screen against its design specification and flags mismatches by dimension and severity. Use it when comparing a design to the built implementation or checking what differs between them.

Designer Onboarding creates a practical guide for a new designer joining a team that uses a design system. It covers system context, tooling setup, working norms, and a first contribution path.

Docs Coverage audits a design system’s documentation surface against its component library. It finds undocumented components, stale docs, and orphaned pages using Storybook, local code, and optional docs integrations.

Drift Detection identifies where a design system has diverged from its intended tokens, components, or patterns across consuming products. Use it to classify visual, behavioural, API, and token drift, and to separate intentional exceptions from accidental gaps.

Engineering Onboarding creates a first-day guide for engineers joining a team that consumes a design system. It covers installation, component usage, token access, testing, and the rules that prevent local wrappers and hardcoded values.

Figma Variable Audit checks Figma variable collections against three-tier token architecture, naming, alias chains, and mode coverage. Use it when you need a structured report on variable health or remediation for Figma-based design tokens.

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.

Metadata Schema Generator creates structured JSON metadata schemas for design system components. Use it when you need machine-readable prop rules, composition constraints, accessibility contracts, or other tooling data.

Naming Audit checks design system components, tokens, and patterns for consistency, ambiguity, and clear purpose. Use it when you need a naming review or want to find inconsistent names and rename candidates.

Pattern Documentation writes documentation for reusable design system patterns composed of multiple components. Use it for pattern pages that explain when to use the pattern, when not to, and how the pieces fit together.