What is design-bridge?

A helper that copies the relevant rules from DESIGN.md, a project’s design-guidelines file, into the active findings document when work involves a user interface.

Use it while building or changing screens, pages, forms, buttons, navigation, layouts, themes, or other interface elements.

It keeps the agent’s current UI work aligned with the project’s existing colors, spacing, typography, and component rules.

design-bridge — Skill for Claude Code by OthmanAdi/MDDesign

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add OthmanAdi/MDDesign --skill design-bridge

Clone the repo

git clone --depth 1 https://github.com/OthmanAdi/MDDesign

Made for: Claude Code.

Or install mddesign, the plugin that ships this one along with the rest of its 5 skills, 10 commands, 5 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/othmanadi/mddesign/design-bridge/github.svg)](https://agentmods.dev/skills/othmanadi/mddesign/design-bridge)

Your own site

<a href="https://agentmods.dev/skills/othmanadi/mddesign/design-bridge"><img src="https://agentmods.dev/badge/skills/othmanadi/mddesign/design-bridge/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/othmanadi/mddesign/design-bridge"><img src="https://agentmods.dev/badge/skills/othmanadi/mddesign/design-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,254 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00080	$0.01254
Opus 5.5	$0.00032	$0.00502
Sonnet 5.5	$0.00016	$0.00251
Haiku 4.5	$0.00008	$0.00125

Measured 1mo ago against content hash 8315491dfe69, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-bridge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.clinerules/design-bridge/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Bridge

Runtime companion. Lives between DESIGN.md and findings.md.

When you (Claude) should run this skill

You are running this skill when ANY of the following is true:

The active phase in task_plan.md mentions UI keywords (button, card, modal, layout, color, typography, spacing, dialog, navigation, form, input, page, screen, theme, brand, design, component, header, footer, sidebar, hero, cta).
The user just asked you to build, change, or review a UI element.
The PreToolUse hook fired before a Write or Edit against a file matching *.tsx|*.jsx|*.vue|*.svelte|*.html|*.css|*.scss.
The user explicitly ran /mddesign:inject.

What to do

Step 1: Detect DESIGN.md

Glob for DESIGN.md at the project root (CWD).
If absent, do nothing. Surface a one-line note ONLY if the user explicitly invoked the skill: "No DESIGN.md found at project root. Run /mddesign:harvest to generate one from your codebase."

Step 2: Detect the relevant token slice

Read DESIGN.md once.
Identify the token categories the current task touches. Heuristics:
- "button|cta|link" → components.button, colors.primary, colors.secondary, typography (button), rounded
- "card|panel|tile" → components.card, colors.surface, rounded, spacing
- "modal|dialog|overlay" → components.modal, colors.surface, rounded, elevation
- "form|input|field" → components.input, colors.border, typography (body), rounded
- "color|theme|palette" → all colors
- "type|font|heading" → all typography
- "layout|grid|spacing" → spacing scale, layout section
- default → colors (primary, secondary), typography (heading, body)

Step 3: Find the existing "## Design Context" block in findings.md

Read findings.md.
Look for a section header ## Design Context (case-sensitive).
If absent, you will append a fresh block.
If present, you will replace the block contents.

Step 4: Build the new block

The block format:

## Design Context

> Auto-injected by MDDesign on <ISO timestamp>. Source: DESIGN.md.
> Phase trigger: <phase id or "manual">

### Tokens in scope
<bulleted list of token references with values, format `colors.primary = #3B82F6`>

### Component specs in scope
<for each touched component, copy its spec from DESIGN.md verbatim>

### Do's and Don'ts (relevant excerpt)
<copy the relevant Do/Don't lines from DESIGN.md if any>

> If you stray from these tokens, name the deviation explicitly in findings.md before writing code.

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 113 lines · 80 tokens per session scan A 8315491dfe69

Subscribe to this mod's changes

design-bridge is a skill published in the GitHub repository OthmanAdi/MDDesign (14 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,254 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Design and UX agent-orchestration ai-agents anthropic cline codex-cli

suede-site-alchemy

Suede AI conversion-rate optimization for landing, launch, campaign, and product pages. Turns a page into a conversion path: funnel stage, friction inventory, hero, proof, CTA ladder, pricing presentation, mobile task path, and falsifiable A/B hypotheses with a pre-registered experiment ledger, then implements and…

JasonColapietro/suede-creator-skills · 143 tokens

suede-design

Suede AI design skill for interfaces that feel intentional instead of templated: design tokens, color strategy, OKLCH ramps, type scale, fluid type, visual hierarchy, dark mode, spacing, component laws, motion, full surface builds that ship layout and words together, reference-to-target restyles (Suedify), and…

JasonColapietro/suede-creator-skills · 211 tokens

design-bridge