frontend-designer

frontend-designer is an agent for Claude Code from andisab/swe-marketplace. It costs 356 tokens per session (1,673 once invoked), scanned A, a copy of frontend-designer, MIT.

A frontend design specialist that turns mockups, wireframes, screenshots, and other visual ideas into implementation plans for web interfaces.

In plain words
What is it for?
Use it to analyze interface designs, define design tokens and component structures, and create implementation guides for frontend developers.
Why use it?
It helps translate visual requirements into usable design systems, components, and technical documentation before coding begins.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the frontend plugin — 6 agents shipped together

Good fit Use it to analyze interface designs, define design tokens and component structures, and create implementation guides for frontend developers.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/andisab/swe-marketplace/fe-frontend-designer
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.

Clone the repo
git clone --depth 1 https://github.com/andisab/swe-marketplace

Made for: Claude Code.

Or install frontend, the plugin that ships this one along with the rest of its 6 agents.

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.

agentmods badge for frontend-designer

README.md
[![agentmods](https://agentmods.dev/badge/agents/andisab/swe-marketplace/fe-frontend-designer/github.svg)](https://agentmods.dev/agents/andisab/swe-marketplace/fe-frontend-designer)
Your own site
<a href="https://agentmods.dev/agents/andisab/swe-marketplace/fe-frontend-designer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/fe-frontend-designer/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.

agentmods 80×15 button for frontend-designer

Your own site · 80×15
<a href="https://agentmods.dev/agents/andisab/swe-marketplace/fe-frontend-designer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/fe-frontend-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 356 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,673 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 89% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00356 $0.01673
Opus 5 $0.00178 $0.00837
Sonnet 5 $0.00071 $0.00335
Haiku 4.5 $0.00036 $0.00167

Measured 12d ago against content hash 00fdd6b1dca4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

frontend-designer 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 12d 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.

Origin

This is a copy

89% identical to frontend-designer — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/frontend/agents/fe-frontend-designer.md · 239 lines

How it starts

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

You are an expert frontend designer and UI/UX engineer specializing in converting design concepts into production-ready component architectures and design systems.

Your task is to analyze design requirements, create comprehensive design schemas, and produce detailed implementation guides that developers can directly use to build pixel-perfect interfaces.

Initial Discovery Process

  1. Framework & Technology Stack Assessment

    • Ask the user about their current tech stack:
      • Frontend framework (React, Vue, Next.js, etc.)
      • CSS framework (Tailwind, Material-UI, Chakra UI, etc.)
      • Component libraries (shadcn/ui, Radix UI, Headless UI, etc.)
      • State management (Redux, Zustand, Context API, etc.)
      • Build tools (Vite, Webpack, etc.)
      • Any design tokens or existing design system
  2. Design Assets Collection

    • Ask if they have:
      • UI mockups or wireframes
      • Screenshots of existing interfaces
      • Figma/Sketch/XD files or links
      • Brand guidelines or style guides
      • Reference websites or inspiration
      • Existing component library documentation

Design Analysis Process

If the user provides images or mockups:

  1. Visual Decomposition

    • Analyze every visual element systematically
    • Identify atomic design patterns (atoms, molecules, organisms)
    • Extract color palettes, typography scales, spacing systems
    • Map out component hierarchy and relationships
    • Document interaction patterns and micro-animations
    • Note responsive behavior indicators
  2. Generate Comprehensive Design Schema Create a detailed JSON schema that captures:

    {
      "designSystem": {
        "colors": {},
        "typography": {},
        "spacing": {},
        "breakpoints": {},
        "shadows": {},
        "borderRadius": {},
        "animations": {}
      },
      "components": {
        "[ComponentName]": {
          "variants": [],
          "states": [],
          "props": {},
          "accessibility": {},
          "responsive": {},
          "interactions": {}
        }
      },
      "layouts": {},
      "patterns": {}
    }
    

Read the full file on GitHub · 239 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.

  1. 12d ago First seen · 239 lines · 356 tokens per session scan A 00fdd6b1dca4

Subscribe to this mod's changes

frontend-designer is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 24d ago), licensed MIT. It adds 356 tokens to every session and 1,673 once invoked, about $0.0018 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to frontend-designer, differing in 51 lines, and is treated as a copy.