designmd
LibraryTemplatesNEWToolsCLIGuidesPricing

DesignMD

Discover, vote, and share the best DESIGN.md files on the internet.

♥ Support Itmeo

Products

  • AI Studio
  • WebGradients
  • Free Gradient Generator

Company

  • About
  • Blog
  • Manifest
  • Donate

Explore

  • Changelog
  • Vercel DESIGN.md
  • shadcn/ui DESIGN.md
  • GitHub DESIGN.md
  • DESIGN.md examples
  • llms.txt
  • ai.txt
  • Sitemap
  • Newsletter

Connect

  • Twitter / X
  • GitHub
  • DESIGN.md spec
  • dimabraven.com

© 2016–2026 Itmeo. All rights reserved.

PrivacyTerms
Home/DESIGN.md Files/Codex workflow reference

Codex workflow reference

Editorial referencePractical workflow notes for AI coding agents
Dima BravenDima Braven·Jan 6, 2026

A reference pattern for pairing engineering instructions with DESIGN.md visual constraints for Codex.

referencecodexworkflowtoolsdesign-md
Codex workflow reference screenshot
CursorClaude CodeCodexGoogle Stitch

Sign in to copy full DESIGN.md files, download .md files, and save styles.

# Codex workflow reference

## What this is
Codex is OpenAI tooling for software engineering work such as implementing changes, reviewing code, running checks, and collaborating inside a repository.

This page explains a practical repository pattern: keep AGENTS.md responsible for engineering instructions and use DESIGN.md as the visual source of truth for frontend work.

## Editorial status
This is a DesignMD-authored editorial reference, not an official OpenAI Codex DESIGN.md file and not a reproduction of OpenAI product UI. Use the linked OpenAI page for official product information.

## Why this page exists in DesignMD
This reference is not a scraped brand style page. It is a workflow page for teams that want to pair OpenAI Codex with a durable DESIGN.md file.
Use it when an AI builder needs visual taste before it edits Tailwind classes, creates React components, or turns a prompt into a working interface.
The goal is practical: make the agent read a small design contract before it starts guessing color, density, hierarchy, radius, and component behavior.

## How DESIGN.md fits the workflow
- Keep AGENTS.md focused on engineering invariants, commands, and close-out rules.
- Keep DESIGN.md focused on UI taste, layout density, components, and visual acceptance criteria.
- Mention DESIGN.md explicitly in the task when asking Codex to edit frontend code.
- For monorepos, place product-specific DESIGN.md files near the app or add a top-level routing note.
- Ask Codex to verify screenshots when a frontend change can visually regress.
- Keep DESIGN.md close to the source code, usually in the project root or beside the frontend app that owns the product surface.
- Treat the file as a living design contract. Update it after visual decisions change, not only after a full redesign.
- Reference the file explicitly in your coding-agent instructions so it is read before UI work begins.
- Prefer concrete values over adjectives. Agents follow `--radius-card: 8px` more reliably than "make it polished".
- Pair visual rules with acceptance checks: responsive behavior, hover states, empty states, error states, and accessibility.

## Recommended DESIGN.md structure
A useful DESIGN.md for this workflow should be readable by a human reviewer and precise enough for an agent.

### Product feel
- Define the product category and emotional target in one paragraph.
- Name what the interface should avoid, not only what it should become.
- Include the density target: sparse marketing, focused SaaS, data-heavy console, or code-first tool.

For makers

Get your product in context

Add your tool/site or create the DESIGN.md first. Every listing is reviewed before publication.

Add your tool/site · $19Create my DESIGN.md
See full pricing

Design System Overview

This editorial reference was written by DesignMD to make an AI-agent workflow concrete. It is independent guidance, not an official product design file or an endorsement from the linked tool vendor.

Use it as a starting contract for repository instructions, visual tokens, component behavior, and review checks. Adapt the values to your product instead of copying them as a vendor-owned brand system.

Browse more developer tools and IDEs design systems or explore the full DESIGN.md directory.


Color System

Starter semantic tokens for this editorial workflow — not an official vendor palette. Click any swatch to copy the hex value.

Text / Primary

#111827

Accent

#8B5CF6

Surface / Background

#F5F3FF

Border / Subtle

#DDD6FE


Typography Specimen

Display

2.8rem / 700 / 1.04

The quick brown fox

Heading H1

2rem / 700 / 1.1

The quick brown fox jumps

Heading H2

1.5rem / 600 / 1.15

The quick brown fox jumps over

Heading H3

1.125rem / 600 / 1.2

The quick brown fox jumps over the lazy

Body

1rem / 400 / 1.5

The quick brown fox jumps over the lazy dog

Small / Caption

0.75rem / 400 / 1.5

The quick brown fox jumps over the lazy dog and sat down.

Monospace

const primary = "System";


Layout & Spacing Tokens

Spacing Scale

space-14px
space-28px
space-312px
space-416px
space-624px
space-832px
space-1248px
space-1664px

Border Radius

radius-none0px
radius-sm4px
radius-md8px
radius-lg16px
radius-xl24px
radius-full9999px

Elevation & Shadow

Flatshadow-none
XSshadow-xs
SMshadow-sm
MDshadow-md
LGshadow-lg
XLshadow-xl

Use with AI Coding Agents

Copy one of these prompts into your AI coding agent to apply the Codex workflow reference design system to your project. The DESIGN.md file in your repo root is the source of truth.

# .cursor/rules (or DESIGN.md)
You are working in a project that uses the Codex workflow reference design system.

Read the DESIGN.md file in this project root and follow it strictly when generating UI.
Match the brand's exact colors, typography, spacing scale, and border radius.
Do not create generic Tailwind UI — apply the visual language from DESIGN.md.

Key rules:
- Use the defined color palette, not arbitrary hex values
- Apply the correct font family and weight scale
- Follow spacing tokens (4/8/12/16/24/32px scale)
- Match component patterns: buttons, cards, inputs, badges as specified

Related DESIGN.md files

Stripe

Stripe

Developer-first payments platform. Clean, trustworthy, minimal decoration.

View DESIGN.md
Cursor

Cursor

AI-first code editor. Dark, minimal, keyboard-centric devtool.

View DESIGN.md
Dribbble

Dribbble

Design community and portfolio. Soft, creative, colorful.

View DESIGN.md
Are.na

Are.na

Research and bookmarking platform. Minimal, intellectual.

View DESIGN.md
Rippling

Rippling

Workforce management platform. Dense, enterprise, modern.

View DESIGN.md
Framer

Framer

Interactive design and publishing. Editorial, bold, premium web.

View DESIGN.md

Frequently Asked Questions

Can I use the Codex workflow reference DESIGN.md with Cursor, Claude Code, or Codex?

Yes. Copy the DESIGN.md file into your project root and reference it in your agent rules. For Cursor, add it to .cursor/rules. For Claude Code, include it as CLAUDE.md. For Codex, add it to your system prompt. The agent will read it and apply the Codex workflow reference visual system to any UI it generates.

Is this an official Codex workflow reference file?

No — this is an independent reference created for AI coding agent compatibility. It is not officially endorsed by Codex workflow reference. The visual system was analyzed and documented to help AI agents produce UI that matches the Codex workflow reference aesthetic. Always verify against official Codex workflow reference documentation.

What is a DESIGN.md file?

A DESIGN.md file is a Markdown document that describes a product's visual design system in a format that AI coding agents can read and follow. It captures color palettes, typography, spacing, component patterns, and usage rules — giving AI agents like Cursor, Claude Code, and Codex a source of truth for consistent UI generation.

Can I use the Codex workflow reference color tokens and visual style in my own project?

The design tokens and visual patterns documented here are for reference and AI agent guidance. If you are building a project inspired by the Codex workflow reference visual style, ensure your use is consistent with Codex workflow reference's brand guidelines and any applicable trademark or copyright rules. This file helps AI agents understand a style — it does not grant license to use proprietary brand assets.

How do I add this to my project?

Download the DESIGN.md file (requires free account) and place it in your project root. Then tell your AI agent to read it: "Read the DESIGN.md file in this project and follow its design system when generating UI." The agent will pick it up automatically in most modern AI coding tools.