About the format
A design skill turns taste into instructions an agent can use.
It is a focused set of rules for a visual direction, a product surface, or a design workflow. The useful part is not the label; it is the concrete decisions the skill helps an agent make.
What belongs in one
A strong skill names the visible decisions an agent should preserve: typography, spacing, surface hierarchy, color roles, component behavior, motion, and the states that are easy to forget. It gives the implementation a direction without pretending that one preset fits every product.
How to use it
- Choose a direction that matches the product task, not only the mood.
- Read the local DesignMD page and check the source/provenance status.
- Give the agent the skill together with your product context and constraints.
- Keep the rules that prevent repeated mistakes; remove decorative instructions that do not change implementation.
What DesignMD adds
DesignMD is the local reading and discovery layer: internal routes, editorial framing, related directions, and transparent attribution. Source owners keep their original artifacts and licenses. A page marked metadata-only describes the local editorial content mode; when an upstream artifact is verified, its own page shows the exact source path and install command without copying the file into DesignMD.