AnyPost
Free tools
Free · No signup

DESIGN.md generator

Generate a DESIGN.md design-system file for AI coding agents — colors, typography, UI tokens, spacing, and component rules. Guided form, copy-ready Markdown, no signup. Give AI coding agents a single source of truth for colors, typography, UI tokens, and component rules — the same idea as a README, but for design.

Design inputs

Fill in your product identity and tokens. The preview updates as you type.

Colors

Typography

Layout & radius

Rules for agents

Generated DESIGN.md

Save at your repo root (or docs/) and reference it in agent instructions alongside your code style guide.

markdown
---
name: My Product
description: Warm, approachable SaaS UI — cream surfaces, confident primary green, serif headlines, sans body, monospace for code.
colors:
  primary: "#386948"
  primary-dim: "#2b5d3c"
  on-primary: "#e8ffe9"
  primary-container: "#b9efc5"
  surface: "#f7faf4"
  surface-container-low: "#f0f5ee"
  on-surface: "#2c342e"
  text-dim: "#5e665f"
  tertiary: "#745c27"
  border-subtle: "#dfe5dc"
  error: "#a83836"
typography:
  display:
  fontFamily: "Literata, Georgia, serif"
  fontSize: "48px"
  fontWeight: "700"
  lineHeight: "56px"
  letterSpacing: "-0.03em"
  body:
  fontFamily: "Nunito Sans, ui-sans-serif, system-ui, sans-serif"
  fontSize: "16px"
  fontWeight: "400"
  lineHeight: "26px"
  code:
  fontFamily: "JetBrains Mono, ui-monospace, monospace"
  fontSize: "14px"
rounded:
  card: "16px"
  pill: "9999px"
spacing:
  page: "1200px"
  prose: "768px"
components:
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    rounded: "{rounded.card}"
    padding: "12px 24px"
---

## Overview

Warm, approachable SaaS UI — cream surfaces, confident primary green, serif headlines, sans body, monospace for code. Implement tokens in your global CSS or theme file (for example Tailwind @theme or CSS variables). Marketing pages may use light motion; product and account surfaces stay task-focused.

## Colors

- **Primary** `#386948`: CTAs, links, emphasis in headlines.
- **Surfaces**: `#f7faf4` page background; stepped containers `#f0f5ee` for bands and cards.
- **Text**: `#2c342e` body; `#5e665f` secondary.
- **Accents**: tertiary `#745c27`; error `#a83836` for failures.
- **Borders**: `#dfe5dc` for cards and dividers.

## Typography

- **Headlines**: Literata, Georgia, serif, display sizes with tight tracking.
- **Body**: Nunito Sans, ui-sans-serif, system-ui, sans-serif, 16px, line-height ~1.5–1.6.
- **Code**: JetBrains Mono, ui-monospace, monospace for URLs, API keys, and Markdown previews.
- Prefer sentence case for section labels; avoid ALL CAPS eyebrows across the page.

## Elevation

Light borders over heavy shadows. Featured cards: subtle ring on primary. Hover: small translate lift on marketing cards only.

## Layout bands

- **Page background**: surface token on `body`.
- **Hero band**: full-width surface-container-low so the hero separates from the cream body.
- **Cards / panels**: surface-container-lowest with border-subtle.
- **Content width**: page max 1200px; long-form prose max 768px.

## Components

Primary buttons: filled primary background, on-primary text, rounded-card, 12px 24px padding, active scale 0.97. Secondary: surface border, on-surface text. Cards: surface-container-lowest, border-subtle, rounded-card.

## Motion

Marketing pages only: subtle gradient or shimmer on hero CTAs. Product/task UI stays static. Honor prefers-reduced-motion for all decorative animation.

## Accessibility

Target WCAG AA. Use text-dim only for supporting copy on cream surfaces (verify 4.5:1). Touch targets ≥44px on mobile. Focus-visible outlines on interactive elements.

## Do's and Don'ts

**Do**

- Use design tokens from your theme, not ad-hoc hex in components.
- Keep one clear `h1` per page; supporting copy in text-dim.
- Separate marketing hero with a distinct surface band.

**Don't**

- `transition-all` or bounce easing on task-focused UI.
- Decorative motion on converter, editor, or account flows.
- Generic purple gradients or default system-only stacks unless intentional.

What you get

  • Guided form aligned with common DESIGN.md structure (YAML + sections)
  • Colors, typography, spacing, radius, and component tone fields
  • Live Markdown preview with copy and download
  • Example based on AnyPost’s Terra design tokens
  • Honest scope: form-based template, no automatic website scan
  • Free — runs in your browser; no API key

Example: AnyPost DESIGN.md shape

AnyPost ships Terra tokens in DESIGN.md plus globals.css. Your file can follow the same YAML frontmatter and section headings.

markdown
---
name: AnyPost Terra
description: Rooted warmth — earthy greens and warm neutrals for LLM-ready social conversion
colors:
  primary: "#386948"
  primary-dim: "#2b5d3c"
  on-primary: "#e8ffe9"
  primary-container: "#b9efc5"
  surface: "#f7faf4"
  surface-container-low: "#f0f5ee"
  on-surface: "#2c342e"
  text-dim: "#5e665f"
  tertiary: "#745c27"
  border-subtle: "#dfe5dc"
  error: "#a83836"
typography:
  display:
  fontFamily: "Literata, Georgia, serif"
  fontSize: "48px"
  fontWeight: "700"
  lineHeight: "56px"
  letterSpacing: "-0.03em"
  body:
  fontFamily: "Nunito Sans, ui-sans-serif, system-ui, sans-serif"
  fontSize: "16px"
  fontWeight: "400"
  lineHeight: "26px"
  code:
  fontFamily: "JetBrains Mono, ui-monospace, monospace"
  fontSize: "14px"
rounded:
  card: "16px"
  pill: "9999px"
spacing:
  page: "1200px"
  prose: "768px"
components:
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    rounded: "{rounded.card}"
    padding: "12px 24px"
---

## Overview

Rooted warmth — earthy greens and warm neutrals for LLM-ready social conversion Implement tokens in your global CSS or theme file (for example Tailwind @theme or CSS variables). Marketing pages may use light motion; product and account surfaces stay task-focused.

## Colors

- **Primary** `#386948`: CTAs, links, emphasis in headlines.
- **Surfaces**: `#f7faf4` page background; stepped containers `#f0f5ee` for bands and cards.
- **Text**: `#2c342e` body; `#5e665f` secondary.
- **Accents**: tertiary `#745c27`; error `#a83836` for failures.
- **Borders**: `#dfe5dc` for cards and dividers.

## Typography

- **Headlines**: Literata, Georgia, serif, display sizes with tight tracking.
- **Body**: Nunito Sans, ui-sans-serif, system-ui, sans-serif, 16px, line-height ~1.5–1.6.
- **Code**: JetBrains Mono, ui-monospace, monospace for URLs, API keys, and Markdown previews.
- Prefer sentence case for section labels; avoid ALL CAPS eyebrows across the page.

## Elevation

Light borders over heavy shadows. Featured cards: subtle ring on primary. Hover: small translate lift on marketing cards only.

## Layout bands

- **Page background**: surface token on `body`.
- **Hero band**: full-width surface-container-low so the hero separates from the cream body.
- **Cards / panels**: surface-container-lowest with border-subtle.
- **Content width**: page max 1200px; long-form prose max 768px.

## Components

Primary buttons: filled primary background, on-primary text, rounded-card, 12px 24px padding, active scale 0.97. Secondary: surface border, on-surface text. Cards: surface-container-lowest, border-subtle, rounded-card.

## Motion

Marketing pages only: subtle gradient or shimmer on hero CTAs. Product/task UI stays static. Honor prefers-reduced-motion for all decorative animation.

## Accessibility

Target WCAG AA. Use text-dim only for supporting copy on cream surfaces (verify 4.5:1). Touch targets ≥44px on mobile. Focus-visible outlines on interactive elements.

## Do's and Don'ts

**Do**

- Use design tokens from your theme, not ad-hoc hex in components.
- Keep one clear `h1` per page; supporting copy in text-dim.
- Separate marketing hero with a distinct surface band.

**Don't**

- `transition-all` or bounce easing on task-focused UI.
- Decorative motion on converter, editor, or account flows.
- Generic purple gradients or default system-only stacks unless intentional.

Use DESIGN.md with agents

  1. Save the generated file as DESIGN.md in your repo root or a docs/ folder.
  2. Point Cursor, Claude Code, or your agent rules at the file (for example “follow DESIGN.md for all UI work”).
  3. Keep tokens in CSS or Tailwind theme variables in sync with the Markdown so agents and builds agree.
  4. Pair with llms.txt so agents know which docs and marketing pages matter — use the llms.txt generator on this site.

Why DESIGN.md matters for AI-assisted UI

The AnyPost DESIGN.md generator at anypost.md/free-tools/design-md-generator helps teams publish a design-system Markdown file for AI-assisted development. DESIGN.md is plain text in the repo: palette, type scale, spacing, radius, and component patterns agents can read alongside code. The free builder uses a guided form—product name, aesthetic summary, color tokens, fonts, layout widths, and rules for buttons, motion, and accessibility—then outputs YAML frontmatter plus Overview, Colors, Typography, and Do's and Don'ts sections matching how AnyPost documents Terra tokens in its own DESIGN.md. It does not claim to scan arbitrary websites; you edit the template honestly. Save as DESIGN.md, reference it in agent instructions, and keep CSS theme variables in sync. Pair with the llms.txt generator so agents know which docs pages matter. Compose and social post to Markdown tools stay on the same free-tools hub.

Questions

What is DESIGN.md?

DESIGN.md is a plain-text design-system file in your repo — like a README for visual rules. It lists colors, fonts, spacing, and component patterns so humans and AI coding agents build UI that matches your product.

How is this different from Figma or a brand PDF?

Design tools hold assets and specs agents cannot read directly. DESIGN.md is Markdown in the codebase: agents in Cursor, Claude Code, or similar tools can load it as context and follow the same palette and type scale every session.

Does this tool scan my live website?

No. You describe your product aesthetic in the form and the generator outputs a structured template you edit. That keeps output honest and avoids claiming automated extraction from arbitrary URLs.

Who should use a DESIGN.md generator?

Teams starting a project, developers without a formal brand guide, or anyone tired of agents guessing button styles and hex values. Update the file as your design evolves.

How does AnyPost use DESIGN.md?

AnyPost maintains DESIGN.md alongside app/globals.css tokens — warm cream surfaces, forest-green primary, Literata headlines, Nunito body. Use this generator to bootstrap a similar file for your own product.

Markdown → social? Compose · Social → Markdown? Live preview