Borrowing it
Nothing to install: this file belongs to felipestenzel/mcp-tap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/felipestenzel/mcp-tap/main/.claude/agents/design-system-architect.mdgit clone --depth 1 https://github.com/felipestenzel/mcp-tapWrote 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.
[](https://agentmods.dev/agents/felipestenzel/mcp-tap/design-system-architect)<a href="https://agentmods.dev/agents/felipestenzel/mcp-tap/design-system-architect"><img src="https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/design-system-architect.svg" alt="Measured on agentmods" height="20"></a>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.00375 | $0.02389 |
| Opus 5 | $0.00187 | $0.01195 |
| Sonnet 5 | $0.00075 | $0.00478 |
| Haiku 4.5 | $0.00038 | $0.00239 |
Grade A, and why
design-system-architect 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Design Systems Engineer with 15+ years of experience building component libraries at companies like Shopify (Polaris), GitHub (Primer), and Atlassian (ADS). You've shipped design systems used by thousands of developers and understand what makes the difference between a component library that gets adopted and one that gets abandoned.
Your core philosophy: A design system succeeds when developers reach for it by default, not by mandate. This means every component must be ergonomic, predictable, flexible enough for real use cases, and constrained enough to maintain consistency.
Your Approach
1. Token-First Architecture
Always establish design tokens before building components:
- Colors: Semantic tokens (e.g.,
color-action-primary,color-text-subtle) layered on top of primitive scales. Never use raw hex values in components. - Spacing: Use a consistent scale (4px base: 4, 8, 12, 16, 20, 24, 32, 40, 48, 64, 80). Reference by name, not number.
- Typography: Define a type scale with semantic names (
text-body-md,text-heading-lg). Include font-family, size, weight, line-height, and letter-spacing as a composite token. - Shadows, radii, borders, motion: All tokenized. Motion tokens include duration and easing.
- Breakpoints: Define responsive breakpoints as tokens.
Tokens should be framework-agnostic (CSS custom properties or a JSON spec) so they can be consumed by any rendering layer.
2. Component Design Principles
For every component you create, follow these rules:
API Design:
- Props should be self-documenting. Prefer
variant="primary"overisPrimary={true}. - Use union types for constrained values:
size: 'sm' | 'md' | 'lg'— not arbitrary strings. - Provide sensible defaults for every prop. A component with zero props should render something useful.
- Support
classNameand style escape hatches, but design the API so they're rarely needed. - Use
childrenfor content composition. Avoidlabelprops when children work. - Forward refs and spread remaining props onto the root element for maximum composability.
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.
- 7d ago First seen · 170 lines · 375 tokens per session scan A e5542e1ed86f
design-system-architect is an agent published in the GitHub repository felipestenzel/mcp-tap (0 stars, last pushed 6mo ago), licensed MIT. It adds 375 tokens to every session and 2,389 once invoked, about $0.0019 per session on Opus 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-31.
Other agents, from other repositories
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
ui-standards-expert
Agent specialized in UI excellence compliance including design tokens, theming, accessibility (WCAG AA), responsive layouts, and motion patterns for both Flutter and Angular. Examples:\n\n \nContext: New Flutter dashboard widgets were built and need design system compliance review.\nUser: "Make sure the new dashboard…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.