VoltAgent/awesome-design-md
This repository treats visual direction as agent-readable project context: drop in a DESIGN.md containing tokens, component rules, and guardrails to reduce inconsistent generated UI.
The repository provides ready-made **DESIGN.md** files derived from public websites. Each can encode colors, typography, components, spacing, shadows, responsive behavior, touch targets, guardrails, and prompt examples in plain Markdown.
Put the file at the project root and use it as persistent context for a coding agent before requesting UI. The practical pattern is to replace vague style prompts with explicit design tokens and behavioral constraints that can be reviewed in version control.
The repository provides ready-made **DESIGN.md** files derived from public websites. Each can encode colors, typography, components, spacing, shadows, responsive behavior, touch targets, guardrails, and prompt examples in plain Markdown. Put the file at the project root and use it as persistent context for a coding agent before requesting UI. The practical pattern is to replace vague style prompts with explicit design tokens and behavioral constraints that can be reviewed in version control. The files are unofficial extractions of publicly visible design systems and come without warranty. A named brand reference may improve consistency, but builders still need to verify token accuracy, usability, originality, and fit for their own product.
awesome-design-md turns visual references into persistent, reviewable project constraints rather than another one-shot style prompt. It complements procedural taste skills by supplying tokens, component rules, and interaction guardrails that survive across requests. Because the files are unofficial extractions, it also narrows their authority: they are starting context to verify and adapt, not validated design systems or proof of usability and originality.