Validate MDS component specifications against a canonical JSON schema.
npx skills add https://github.com/eboody/eran.codes --skill mds-component-spec
Please help me install this Agent Skill. Skill: mds-component-spec Source: https://github.com/eboody/eran.codes/tree/main/.codex/skills/mds-component-spec Command: npx skills add https://github.com/eboody/eran.codes --skill mds-component-spec
This Skill provides a standardized JSON schema and contract for defining component specifications, ensuring consistency and enabling code generation across MDS agents.
component_spec.json, ensuring all necessary fields like meta, content, ui, and state are correctly defined for downstream processing and code generation.Use the mds-component-spec skill to validate a new component specification file against the canonical schema.
High-intent search queries and answers about installing and using this skill.
You can define a component specification using a canonical JSON schema that governs UI, state, events, and backend interactions to enforce quality and enable consistent code generation. This contract ensures downstream agents process reusable components uniformly.
A component contract is a standardized JSON schema defining UI, state, and backend interactions. It works with MDS agents by enforcing field requirements and cross-reference invariants, ensuring agents generate valid Rust Maud components.
You validate a component specification by checking it against the canonical JSON schema, which enforces detailed field requirements for meta, content, ui, and state. This ensures all necessary cross-reference invariants are met before downstream processing.
Yes, the component spec schema provides the blueprint for generating Rust Maud components. By defining content, UI, state, events, and backend interactions, the schema enforces the protocol adherence needed for automated code generation.
The schema requires strict adherence to detailed field requirements and cross-reference invariants. Components failing these validations cannot proceed to code generation, meaning specifications must comprehensively define UI, state, events, and backend interactions without missing fields.
GenerativeAgentsGenerate a review-ready PRD from initial-requirements.md using the PRD template.
wlfmnstrDesign type-safe React component APIs using compound components, render props, and hooks.
vladm3105Validate cross-document traceability and integrity across SDD framework documents.
yuhle-qugDesign REST APIs with HTTP semantics and OpenAPI documentation.