metadata-schema-generator

Generate JSON metadata schemas encoding component props, rules, and accessibility contracts.

155|7|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/murphytrueman/design-system-ops --skill metadata-schema-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metadata-schema-generator
Source: https://github.com/murphytrueman/design-system-ops/tree/main/skills/metadata-schema-generator
Command: npx skills add https://github.com/murphytrueman/design-system-ops --skill metadata-schema-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of structured JSON metadata schemas for design system components, enabling machine-readable definitions for tooling like linters, code generators, and AI agents.

Core Features & Use Cases

  • Automated Schema Generation: Creates JSON schemas that encode component props, behavioral rules, composition constraints, and accessibility contracts.
  • Tooling Integration: Produces machine-readable data for MCP servers, linters, and code generators, bridging the gap between human documentation and machine understanding.
  • Use Case: Generate a JSON schema for your Button component that defines its variant prop, specifies that it can only contain Icon or text children, and mandates an aria-label when used icon-only.

Quick Start

Generate a JSON metadata schema for the 'Button' component.

Frequently Asked Questions about metadata-schema-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate JSON schemas for design system components?

To generate JSON schemas for design system components, you can use automated schema generation tooling that extracts component data from Figma, Storybook, and source code to synthesize machine-readable definitions encoding props, behavioral rules, and accessibility contracts.

What is machine-readable component metadata used for?

Machine-readable component metadata is used to bridge human documentation and machine understanding, providing structured JSON data for programmatic consumption by AI agents, linters, MCP servers, and code generators to automate UI governance.

Can I extract component composition constraints and accessibility rules from Storybook and Figma?

Yes, you can extract component composition constraints and accessibility rules by integrating schema generation tooling with Storybook and Figma to synthesize source code data, encoding constraints like child element limits and mandatory aria-labels into JSON.

How do I encode behavioral rules and props for AI agents?

You encode behavioral rules and props for AI agents by generating structured JSON metadata schemas that programmatically define component properties, valid states, and composition limits, allowing automated tooling to understand and interact with UI components correctly.

Do I need source code access to generate JSON metadata schemas for UI components?

Source code access is highly beneficial for generating accurate JSON metadata schemas, as the generation process integrates directly with source code alongside Figma and Storybook to extract and synthesize comprehensive component data into machine-readable formats.