.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/murphytrueman/design-system-ops
home/skills/murphytrueman/design-system-ops
murphytrueman avatar

murphytrueman/design-system-ops

40 skills

View on GitHub
$npx skills add murphytrueman/design-system-ops
SkillInstalls
accessibility-per-componentRun an accessibility audit on a specific design system component.—adoption-reportProduce a design system adoption report separating coverage from actual adoption, with trend direction and risk flags.—ai-component-descriptionGenerate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption.—backlog-generatorTransform audit findings into sprint-ready work items with effort estimates, acceptance criteria, and stakeholder-friendly rationale.—change-communicationProduce a communication package for a design system change — release notes, migration guide, and team announcement.—cicd-integrationGenerate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility…—codebase-indexGenerate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and…—codemod-generatorGenerate codemods (automated code transformation scripts) for design system migrations — token renames, component API changes, prop deprecations, and import…—component-api-validatorAudit component APIs for consistency, breaking changes, TypeScript coverage, and contract compliance across a component library.—component-auditAudit a design system's component library for health, producing a findings-based assessment of usage, complexity, duplication, and coverage gaps with…—component-decision-treeBuild queryable decision trees that help agents and teams choose between components — structured YAML files mapping user intents to the correct component…—context-engine-builderGenerate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything…—contribution-workflowCreate or document a contribution workflow for a design system — the multi-stage process for evaluating, accepting, and shepherding new contributions through…—decision-recordCreate a structured narrative record documenting why a design system decision was made — the context, options considered, trade-offs, and rationale.—deprecation-processPlan and execute the full deprecation lifecycle for a design system component, token, or pattern — including timeline, migration paths, communication plan, and…—design-to-code-checkCheck alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison.—designer-onboardingCreate an onboarding guide for a designer joining a team that uses a design system.—docs-coverageAudit whether a design system's documentation surface keeps pace with its component library — coverage gaps (components with no docs), staleness (docs that…—drift-detectionIdentify where a design system has diverged from its original intent across the whole system — components implemented differently to spec, tokens overridden…—engineering-onboardingCreate an onboarding guide for an engineer joining a team that consumes the design system.—figma-variable-auditAudit Figma variable collections against token architecture best practices.—governance-encoderConvert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically.—metadata-schema-generatorGenerate structured JSON metadata schemas for design system components — machine-readable constraint definitions that encode props, behavioural rules,…—naming-auditAudit a design system's naming conventions across components, tokens, and patterns.—pattern-documentationWrite documentation for a design system pattern — a multi-component recipe covering use cases, anti-patterns, composition, and related patterns.—release-retrospectiveProduce a structured look-back after a major release or deprecation — capturing what the plan got right, what it missed, and what to do differently.—schema-validatorValidate token files against DTCG 2025.10, Style Dictionary, or custom schemas.—session-memoryPersist and recall findings across skill runs within and between sessions, building a cumulative knowledge base of what has been discovered about a design…—stakeholder-briefWrite a one-page stakeholder brief translating design system health or status into business language.—system-benchmarkBenchmark a design system against industry standards and comparable public systems, producing a qualitative comparison across dimensions with specific, named…—system-healthRun an overall health assessment across a design system, producing a findings-based summary across seven dimensions.—system-pitchWrite a design system investment pitch with a business case and ROI framing.—theme-auditAudit theme coverage and consistency across a design system's semantic and component token tiers.—token-auditAudit a design system's token definitions for naming violations, missing semantic tiers, and structural debt.—token-complianceCheck a codebase or implementation for token compliance — finding hardcoded values, wrong-tier token references, and inconsistent token application in…—token-documentationWrite documentation for design tokens — covering semantic intent, usage context, and do/don't examples.—triageRecommend which design system skills to run first based on a quick assessment of the system's state.—usage-guidelinesWrite usage guidelines for a specific, named component — covering when to use it, when not to, edge cases, and anti-patterns for that one component.—version-bump-advisorRecommend the correct semver bump with reasoning and a generated changelog entry.—visual-reportGenerate visual output — charts, dashboards, and trend graphs — from audit findings, session history, or system health data.—