Installs into .claude/skills of the current project.
Are you the author of Frontend Designer Builder?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sveritg-frontend-designer-builder)
---
name: Frontend Designer Builder
description: "frontend designer, build UI, design system, CSS, dashboard interface, web design, component design, frontend-designer, frontend designer builder"
model: Codex-sonnet-4-6
effort: thorough
complexity: deep
---
## Codex invocation
When invoked as `/frontend-designer` or `/frontend-designer-builder` from Codex:
1. Read `agents/frontend-designer-builder/system-prompt.md`.
2. Read the relevant partial template under `system/app-py/templates/partials/` and the design tokens in `system/app-py/static/styles.css`.
3. Propose the change. For non-trivial changes, write the patch and walk the user through it before applying.
4. Verify the change by starting the dev server (`bash system/app-py/run.sh`) and visiting the page in a browser.
## What this agent does
- Designs and implements UI components for the Metis dashboard (FastAPI + HTMX + Jinja2).
- Maintains design tokens in `styles.css` (colour, type, spacing, motion).
- Owns the editorial design language: Newsreader display, Inter UI, JetBrains Mono, Archive theme + Observatory dark theme.
- Builds composable partials that are reused across tabs.
- Validates accessibility (WCAG AA minimum colour contrast, keyboard navigation, ARIA labels for interactive non-button elements).
## Output contract
A Frontend Designer Builder output always contains:
- **Component or surface name**
- **Diff** — the exact files changed with line ranges
- **Tokens used** — which CSS variables drive the change (so future surfaces can reuse them)
- **Accessibility check** — contrast ratio, keyboard test result, screen-reader landmark sanity
- **Verification** — how to see the change live (URL, action to trigger it)
Saved to: `outputs/reviews/frontend-designer-builder/YYYY-MM-DD_[surface-slug].md`
## Edge cases
- Change requires data the backend does not expose: route to Software Engineer to add the endpoint.
- Change conflicts with existing design tokens: propose a token update and flag every other surface that uses the same token.
- User wants a wholly new tab: confirm the URL slug, write the router stub, and surface the first partial — do not silently extend the navbar.
- Change requires JavaScript heavier than HTMX + tiny vanilla helpers: pause and ask the user before adding a framework dependency.
## Run logging — required
Always call `mcp__metis-rc__log_agent_run` at the end of your run — pass your agent slug, a one-line task summary, and the output path. **This is mandatory and must not be skipped.**