Design.MD vs MDV

Design.MD is a collection of Markdown files that encode brand visual languages in a format AI coding agents actually understand. Drop a DESIGN.md file into your project and your AI coding agent — Cursor, Claude Code, Lovable, v0, Bolt — generates UI that matches the target brand instead of defaulting to "the AI beige" of generic Tailwind defaults. The library ships with 60+ ready-made design system files covering popular brands like Stripe, Notion, Linear, and Vercel, encoding their exact color palettes, typography scales, spacing systems, component patterns, and motion guidelines. Files include Tailwind configurations, CSS variables, and component-level patterns — not just vibe words. If a brand isn't available, there's a custom generation flow and a request system. This is a deceptively simple idea with real product leverage. AI agents are excellent at building functional UIs but terrible at design consistency without explicit constraints. DESIGN.md files act as a persistent design brief that the agent can read every time it touches the front end. For indie builders, agencies, and rapid prototypers, this solves a real and recurring problem — free and open, which removes any friction to adoption.

MDV (Markdown Data Views) is a markdown superset that extends standard .md files with embedded live data, interactive charts, and presentation-ready slides. The goal is a single document format that serves simultaneously as developer documentation, a live dashboard, and a shareable slide deck — without requiring a separate tool for each use case. MDV files can embed SQL queries, API calls, and data transforms directly in markdown, with results rendering as tables, charts, or visualizations on the fly. The syntax extends frontmatter conventions that markdown users already know, keeping the learning curve minimal. Output can be previewed in a local server, exported as HTML, or converted to a slide deck — the same source file serves all three outputs. MDV surfaced on Hacker News with 44 points and active discussion around the concept of "living documents" — reports and runbooks that stay current because their data sources are live queries rather than screenshots. For developer-heavy teams who live in their editors and resist adopting heavyweight BI tools, MDV offers a markdown-native alternative that slots into existing documentation workflows.