design-system-ops

In the author's own words, from each skill's SKILL.md — showing the first 30 of 36 files.

• accessibility-per-component

  Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.

  skills/accessibility-per-component/SKILL.md on GitHub (opens in a new tab)

• adoption-report

  Adoption report: coverage (what the system provides), reach (teams with access) and adoption (teams shipping with it), design vs engineering, trend and at-risk teams. Triggers: adoption report, usage metrics, which teams use the system. Not docs coverage — use docs-coverage.

  skills/adoption-report/SKILL.md on GitHub (opens in a new tab)

• agent-instructions

  Write the AGENTS.md that tells coding agents how to use this design system: where things live, sourced rules, how to check work, what not to do; Claude, Cursor or Copilot pointers on request. Triggers: AGENTS.md for our system, make it AI-navigable, agent instructions. Inventory: codebase-index.

  skills/agent-instructions/SKILL.md on GitHub (opens in a new tab)

• ai-component-description

  Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.

  skills/ai-component-description/SKILL.md on GitHub (opens in a new tab)

• backlog-generator

  Turn existing audit findings into sprint-ready tickets with T-shirt estimates, acceptance criteria, dependencies and phases. Triggers: tickets from audit, backlog from findings, sprint planning from report. Not for the contribution process (contribution-workflow).

  skills/backlog-generator/SKILL.md on GitHub (opens in a new tab)

• change-communication

  Write release notes, a migration guide and a team announcement for a design system change that is already decided, scaled to its impact. Triggers: release notes, announce this change, tell teams about a breaking change. Semver call: version-bump-advisor. Deprecation plan: deprecation-process.

  skills/change-communication/SKILL.md on GitHub (opens in a new tab)

• cicd-integration

  Generate CI pipeline files and check scripts (GitHub Actions, GitLab, CircleCI, Bitbucket) that automate design system checks: token validation, hardcoded values, a11y scans, visual regression, bundle size. Trigger: set up CI, quality gates, automate these checks. Not for running an audit.

  skills/cicd-integration/SKILL.md on GitHub (opens in a new tab)

• codebase-index

  Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.

  skills/codebase-index/SKILL.md on GitHub (opens in a new tab)

• codemod-generator

  Generate tested jscodeshift/postcss codemods for design system migrations: token renames, prop renames or removals, import paths, component swaps. Triggers: codemod, migration script, rename this prop everywhere. Deprecation planning: deprecation-process. Release notes: change-communication.

  skills/codemod-generator/SKILL.md on GitHub (opens in a new tab)

• component-api-validator

  Audit prop APIs across a component library: naming consistency, boolean/default patterns, type coverage, exported types, breaking changes between versions. Trigger: component API audit, are our props consistent, prop naming review. For semver calls use version-bump-advisor.

  skills/component-api-validator/SKILL.md on GitHub (opens in a new tab)

• component-audit

  Deep audit of a component library: inventory, usage, duplication, complexity, coverage gaps. Triggers: audit my components, unused components, what components do I have, assess my library. Not for a whole-system view (system-health) or AI index files (codebase-index).

  skills/component-audit/SKILL.md on GitHub (opens in a new tab)

• component-decision-tree

  Write "choosing between" pages (docs/choosing/) that route an intent to the right component via narrowing questions; YAML trees on request. Triggers: which component should I use, choose between X and Y, dialog vs drawer, selection guide. One chosen component: usage-guidelines.

  skills/component-decision-tree/SKILL.md on GitHub (opens in a new tab)

• contribution-workflow

  Design or document how new work enters a design system: contribution types, proposal criteria, review stages, sign-off and release. Triggers: contribution process, how should someone contribute, contribution guidelines, adding a new component. Not for audit findings to tickets (backlog-generator).

  skills/contribution-workflow/SKILL.md on GitHub (opens in a new tab)

• decision-record

  Write a narrative decision record (ADR) for a design system choice: context, options, trade-offs, consequences, including declined proposals. Triggers: document this decision, ADR, why did we choose, capture the reasoning. Machine-checkable rules: governance-encoder.

  skills/decision-record/SKILL.md on GitHub (opens in a new tab)

• deprecation-process

  Plan a deprecation end to end for a component, token, variant or pattern: usage audit, migration path, timeline to a major-version removal, notices. Triggers: deprecate, sunset, phase out, retire, remove, replace X with Y. Announcing non-deprecation changes: change-communication.

  skills/deprecation-process/SKILL.md on GitHub (opens in a new tab)

• design-to-code-check

  Compares a component or screen's design spec with its code and logs each gap as a build error or spec gap. Use it for design QA, handover review or sign-off: whenever someone asks if a build matches its design or spec, even one component with the spec pasted in. System-wide drift: drift-detection.

  skills/design-to-code-check/SKILL.md on GitHub (opens in a new tab)

• docs-coverage

  Audit whether docs keep pace with components: undocumented components, stale docs, orphaned pages, with join confidence. Triggers: docs coverage, which components are undocumented, stale docs check. Not for writing docs (usage-guidelines) or doc analytics (adoption-report).

  skills/docs-coverage/SKILL.md on GitHub (opens in a new tab)

• drift-detection

  Finds where consuming code has drifted from what the design system intended: local re-implementations, token overrides, forked patterns, classified by cause. Use it whenever someone asks where a codebase, product or team has drifted or gone off-system. One component vs spec: design-to-code-check.

  skills/drift-detection/SKILL.md on GitHub (opens in a new tab)

• figma-variable-audit

  Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.

  skills/figma-variable-audit/SKILL.md on GitHub (opens in a new tab)

• governance-encoder

  Turn written governance rules into enforcement that runs: ESLint, Stylelint, dependency-cruiser and CODEOWNERS config traced to sources, plus GOVERNANCE.md for rules with no executable form. Triggers: governance as code, enforce our rules, lint our rules. Pipeline files: cicd-integration.

  skills/governance-encoder/SKILL.md on GitHub (opens in a new tab)

• metadata-schema-generator

  Generate per-component JSON metadata files (.ai/metadata/) from source: props, behaviour, composition, a11y contract, prohibited prop combinations. Triggers: component metadata schema, machine-readable component JSON, manifest for MCP/codegen. Prose for Figma: use ai-component-description.

  skills/metadata-schema-generator/SKILL.md on GitHub (opens in a new tab)

• naming-audit

  Audit component and pattern naming for consistency and clarity, with rename suggestions. Triggers: naming review, are our component names consistent, fix our naming. Token names: token-audit. Prop names: component-api-validator. Figma variable names: figma-variable-audit.

  skills/naming-audit/SKILL.md on GitHub (opens in a new tab)

• onboarding

  Onboarding guide for a designer or engineer joining a team that uses the design system, grounded in the repo and Figma library rather than a template. Triggers: onboard a new designer, onboard a new engineer, getting-started guide, first week with the system, developer or designer onboarding.

  skills/onboarding/SKILL.md on GitHub (opens in a new tab)

• pattern-documentation

  Document a multi-component pattern (form validation, empty states, error handling): when to use, composition, states, a11y, anti-patterns. Triggers: document this pattern, write the pattern page. One named component: use usage-guidelines. Choosing a component: component-decision-tree.

  skills/pattern-documentation/SKILL.md on GitHub (opens in a new tab)

• release-retrospective

  Review how a shipped release, migration or deprecation went against its plan: blast radius, comms, migration, timeline, support load, each gap classed. Triggers: release retro, post-mortem, how did the deprecation go. Planning a new deprecation: deprecation-process.

  skills/release-retrospective/SKILL.md on GitHub (opens in a new tab)

• schema-validator

  Validate token files structurally against DTCG 2025.10 (including resolvers), Style Dictionary 3 to 5 or Tokens Studio: parse errors, $type/$value, name rules, broken or circular aliases. Trigger: validate token JSON, DTCG compliance, are my token files valid. Naming or architecture: token-audit.

  skills/schema-validator/SKILL.md on GitHub (opens in a new tab)

• stakeholder-brief

  Turns design system status or a recommendation into a one-page brief in business language. Use it whenever someone wants an update, summary or note on the system for a VP, exec or stakeholder, however short. Investment case: system-pitch. Charts: visual-report.

  skills/stakeholder-brief/SKILL.md on GitHub (opens in a new tab)

• system-health

  Holistic health check across tokens, components, docs, adoption, governance, AI readiness, platform maturity, with status labels and an inferred maturity stage. Triggers: how healthy is my system, health check, big picture, how do we compare with public systems. Not for one area (use its audit).

  skills/system-health/SKILL.md on GitHub (opens in a new tab)

• system-pitch

  Investment pitch for a new or continuing design system: cost of current state, ROI with visible assumptions, objections, the ask. Triggers: pitch the system, business case, justify the investment, sell this to leadership. For a routine status update use stakeholder-brief.

  skills/system-pitch/SKILL.md on GitHub (opens in a new tab)

• theme-audit

  Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.

  skills/theme-audit/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 54.9k stars · 30 skills
• autoharnessby tigerless-labs Autoharness — a self-learning skill layer for Claude Code — distills skills from your real sessions, updates them as you work, and prunes t… 11.1k stars · 1 skill
• harnessby revfactory A meta-skill that designs domain-specific agent teams, defines specialized agents, and generates the skills they use. 9.2k stars · 2 skills
• universal-modderby rehan-remade Point Claude at any game. Skills, tools and the fal MCP that let Claude Code mod almost any PC game you own: recon, reverse engineering, fa… 7.9k stars · 9 skills
• terminal-browserby zenbu-labs A real browser inside your terminal 3.9k stars · 1 skill