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
.codex/agents/design-bridge.tomlWhat 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.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/design-bridge.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/design-bridge.mdCursor also reads .claude/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.