Skip to main content
subagent CX Codex

design-bridge · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install

design-bridge converts DESIGN.md documents into precise, structured UI instructions for implementation agents.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/design-bridge.toml
Open on GitHub

What design-bridge does

This subagent acts as an intermediary between brand design documentation and frontend code. It pulls a DESIGN.md from the VoltAgent/awesome-design-md repository or reads it from your local cache, scanning sections covering hex palettes, interaction states, type scales, spacing hierarchies, shadows, and breakpoints.

Output lands in a structured specification file such as design/instructions-<site>.md. It includes a quick-reference color table, responsive rules, and tailored component prompts ready for UI builders. The subagent refuses to guess or alter values when source documentation is incomplete, asking for guidance instead of inventing styling details.

What it helps with

  • convert DESIGN.md systems into structured UI build instructions
  • generate quick color reference tables mapping names to hex roles
  • extract typography scales and layout spacing without manual copying
  • create reusable component prompts for frontend implementation agents

Example prompts for the agent

  • Convert the local DESIGN.md into implementation rules for the UI agent
  • Locate the brand DESIGN.md in awesome-design-md and build design/instructions-site.md
  • Extract the full color palette, typography hierarchy, and shadow scales from DESIGN.md

How to install design-bridge

Manually: put the files in place

.codex/agents/design-bridge.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about design-bridge

How to install design-bridge in Codex?

Place the subagent definition file into .codex/agents/design-bridge.toml in your repository.

What does design-bridge do?

It reads brand design files like DESIGN.md and compiles them into verified UI instructions, color maps, and prompt templates for downstream frontend agents.

How does design-bridge handle missing design parameters?

It is instructed not to guess or invent design tokens; instead, it asks for clarification when the source specification lacks data.

Source text

design-bridge.toml · MIT
# design-bridge

Use when a task needs a DESIGN.md (e.g. from the VoltAgent/awesome-design-md collection) translated into precise, implementation-ready UI instructions that faithfully match a target brand.

Own the bridge between a design system document and code: turn a DESIGN.md into actionable UI build instructions that preserve the source brand exactly.

Capture both the numbers (hex, sizes, spacing) and the feel (mood, density, signature details) so downstream implementation matches the original.

Working mode:
1. Confirm the target site/brand and locate its DESIGN.md (fetch from the awesome-design-md collection or read from local cache).
2. Analyze the document across all standard sections without skipping any.
3. Extract visual language: theme, color palette and roles, typography, components, layout, elevation, responsiveness.
4. Synthesize structured instructions and save them for implementation agents to consume.

Focus on:
- visual theme and atmosphere: mood, density, brand philosophy, signature details
- color palette and roles with hex values and hover/active states
- typography: fonts, weights, sizes, spacing, hierarchy
- component stylings: buttons, cards, inputs, nav, badges
- layout principles: spacing, grid, widths, whitespace, radius scale
- depth and elevation: shadow formulas and levels
- responsive behavior: breakpoints and layout adaptation
- a quick color reference (name -> hex -> role) and reusable component prompts

Quality checks:
- verify every standard section was extracted, not skipped
- confirm values are copied faithfully and never invented or "improved"
- ask before assuming when information is missing rather than guessing
- keep descriptions factual, avoiding opinion or marketing language
- ensure output is structured for direct use by UI/frontend implementation agents

Return:
- saved instructions file (e.g. design/instructions-<site>.md)
- quick color reference table (name -> hex -> role)
- typography, component, layout, elevation, and responsiveness rules
- example component prompts ready for implementation
- suggested handoff to UI/frontend implementation agents

Do not modify, omit, or guess design values when the source DESIGN.md is incomplete unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Design →

design-bridge by other authors comes first.

design-bridge VoltAgent Community design-bridge reads a DESIGN.md from the awesome-design-md repo and rewrites it as concrete instructions for building UI that matches the chosen brand. CX Codex ★ 26,718repo stars stitch::generate-design official google-labs-code stitch::generate-design is a Claude Code skill that turns a text prompt or image into a UI screen through Stitch MCP, then edits it with targeted prompts. CX Codex +1 12,500installs create-design-md ibelick create-design-md creates or updates a DESIGN.md file from a code repository or website. It gives coding agents persistent UI context without altering application source code. CX Codex +1 5,800installs muapi-ui-design SamurAIGPT muapi-ui-design turns a product brief into a design spec for high-fidelity UI mockups and wireframes: atomic design, tokens, layout patterns. CX Codex +1 3,000installs design-lab 0xdesign design-lab — a skill that interviews you about a UI task, builds five different directions in a throwaway lab, then turns the pick into an implementation plan. CX Codex +1 2,100installs ui-design mblode ui-design — a Claude Code skill that picks visual direction, builds React, Next and Tailwind interfaces, and audits shipped UI for defects. It also stress-tests components with worst-case data. CX Codex +1 1,600installs design-better BuilderOS design-better — a skill that pushes any coding agent toward designer-quality frontend work: hierarchy, states, accessibility, motion. Useful when the UI runs fine but still looks unfinished. CX Codex +1 1,100installs

From the same set176

The whole set →
graphql-architect graphql-architect — a subagent that audits GraphQL schemas for architectural flaws, performance risks, and security gaps. Guides schema evolution, resolver design, and federation without breaking clients. CX Codex ★ 6,505repo stars fullstack-developer fullstack-developer handles bounded cross-layer features from user actions down to backend effects and UI updates. Useful when a single worker needs to own the full integration path. CX Codex ★ 6,505repo stars frontend-developer frontend-developer — a scoped subagent for frontend changes and UI bug fixes, with checks for state integrity, accessibility, and nearby regressions. CX Codex ★ 6,505repo stars electron-pro electron-pro — a subagent for Electron development: helps map responsibility across main, preload, and renderer processes, design IPC bridges, verify security boundaries, and validate packaging assumptions. CX Codex ★ 6,505repo stars code-mapper The code-mapper subagent maps code paths, ownership boundaries, and execution flow before edits. Use it when behavior is spread across several layers. CX Codex ★ 6,505repo stars backend-developer backend-developer is a Codex subagent for scoped backend implementation and bug fixes once the owning code path is known. It checks a success case and a high-risk failure path. CX Codex ★ 6,505repo stars api-designer api-designer designs API contracts, plans versioning, and inspects breaking changes before implementation starts in Codex. CX Codex ★ 6,505repo stars healthcare-admin This Codex subagent handles healthcare administration work, including medical coding, compliance reviews, and payer contract analysis. Use it when a task concerns healthcare operations rather than general software development. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open