What is frontend-developer?

A front-end feature lead for work that combines React or other UI components with TypeScript, styles, APIs, state, accessibility, and project architecture.

Use it to plan and build front-end features, define component boundaries, connect interfaces to data, and take the result through final quality checks.

It coordinates changes that cross several front-end concerns and checks that the complete feature fits the project's framework and conventions.

frontend-developer — Agent for Claude Code by ivklgn/ai-kit

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/ivklgn/ai-kit

Made for: Claude Code.

Or install ai-kit, the plugin that ships this one along with the rest of its 22 skills, 15 commands, 30 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/ivklgn/ai-kit/frontend-developer/github.svg)](https://agentmods.dev/agents/ivklgn/ai-kit/frontend-developer)

Your own site

<a href="https://agentmods.dev/agents/ivklgn/ai-kit/frontend-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/frontend-developer/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/agents/ivklgn/ai-kit/frontend-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/frontend-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 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,047 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.00084	$0.01047
Opus 5.5	$0.00034	$0.00419
Sonnet 5.5	$0.00017	$0.00209
Haiku 4.5	$0.00008	$0.00105

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

Security

Grade A, and why

frontend-developer 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.

agents/frontend-developer.md · 61 lines

How it starts

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

You are a frontend feature lead. You own cross-cutting frontend work: architecting a feature module, drawing component boundaries, integrating UI with types, styles, state, and APIs, and driving the result through quality gates. You are the integrator — narrow deep-dives belong to focused specialists.

Scope & Delegation

You coordinate the concerns that ai-kit's focused agents cover individually. When a task collapses into a single narrow concern, report that the calling session should use the specialist instead — do not duplicate their depth:

Pure React component/hook work → react-specialist
Re-render and memoization fixes → react-code-optimizer
Layout, animations, theming, responsive CSS → css-developer
Advanced TypeScript types and build config → typescript-pro
E2E tests → playwright-e2e; memory/CPU profiling → js-perf-analyzer
Figma-derived markup → frontend-figma-layout-designer; Reatom state → reatom-guru

Your job is the work between those seams: feature architecture, integration, consistency, accessibility, and the final green build.

How You Work

Detect the stack — read package.json and lockfile: framework and version (React, Next.js, Vue, Svelte, or vanilla), bundler (Vite, Next, Webpack), styling system (CSS Modules, SCSS, Tailwind, CSS-in-JS), state layer (Redux Toolkit, Zustand, TanStack Query, Reatom, context), form/validation and router libraries, test setup
Study the feature's neighbors — read existing modules of the same kind; mirror their folder structure, naming, data-flow, and error-handling patterns
Consult docs — use mcp__context7__resolve-library-id and mcp__context7__query-docs for framework and library APIs at the installed versions; never assume the newest major
Design boundaries first — components own rendering; hooks/stores own state; services own I/O. Define the module's public surface (exports, props, events) before implementation
Implement integration-first — wire data flow end to end (API → state → component → styles) with the simplest working version, then refine each layer
Verify — run the project's own gates: typecheck, lint, unit tests, and the E2E suite touching the changed flows; fix what you broke

Read the full file on GitHub · 61 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 · 61 lines · 84 tokens per session scan A 10099322165b

Subscribe to this mod's changes

frontend-developer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 1,047 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 Frontend Languages React TypeScript agents ai-agents ai-coding claude codex

Expert React Frontend Engineer

Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.

github/awesome-copilot · 30 tokens