Generate or update a project-level DESIGN.md codifying reusable design-language conventions.
npx skills add https://github.com/RhyTsui/PMOS --skill design-language-md
Please help me install this Agent Skill. Skill: design-language-md Source: https://github.com/RhyTsui/PMOS/tree/main/skills/design-language-md Command: npx skills add https://github.com/RhyTsui/PMOS --skill design-language-md
It prevents project teams from drifting on UI/UX conventions by centralizing the reusable design-language rules into a single governed DESIGN.md artifact.
Use design-language-md to generate a project-level DESIGN.md for a new page family by providing the project’s requirement or functional truth, any existing confirmed design artifacts, the chosen component-system preference (for example YokaUI), and the known constraints and anti-patterns.
High-intent search queries and answers about installing and using this skill.
A DESIGN.md file prevents UI/UX drift by centralizing reusable design-language conventions, visual language, interaction rules, and component semantics into a single governed artifact. It guides implementation by capturing page-family rules and anti-patterns before handoff.
Documenting component semantics and interaction rules involves generating a DESIGN.md artifact that codifies visual language, component semantics, and anti-patterns. It separates stable language rules from confirmation status to safely guide implementation without incorrectly claiming design is finalized.
Creating a design language document for a new page family requires providing your project's functional truth, confirmed design artifacts, and component-system preference. The process writes a DESIGN.md capturing intent and page-family rules while explicitly recording missing inputs instead of inventing rules.
DESIGN.md works with existing confirmed design artifacts by prioritizing governed product truth first. It resolves conflicts safely by reading confirmed artifacts and separating language from confirmation status, explicitly recording missing inputs instead of inventing rules or guessing.
You should separate design language from confirmation status so the DESIGN.md file guides implementation without incorrectly claiming the design is finalized. It maintains a stable source of truth for visual and interaction rules while accurately reflecting unconfirmed inputs.
scanbottPlan and codify a complete design system into a DESIGN.md source of truth.
hotriluanGenerate UI designs from natural language prompts and export Tailwind/HTML with DESIGN.md.
RenyEnnosGenerate DESIGN.md design-system documentation from Stitch project assets.
Ankish8Generate React/Tailwind UI code using the myOperator design system.
