frontend-developer

A specialist for building web interfaces with Next.js and React. It uses reusable interface components, Tailwind CSS for styling, and modern ways to render pages on the server or in the browser.

In plain words
What is it for?
Building Next.js pages and layouts, React components, forms, tables, authentication flows, API routes, accessible designs, and server- or browser-rendered features.
Why use it?
It helps create responsive, maintainable interfaces while choosing suitable data loading, routing, authentication, and rendering approaches.

Agent

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.

agentmods
npx agentmods add agents/rafaelkamimura/claude-tools/frontend-developer
Clone the repo
git clone --depth 1 https://github.com/rafaelkamimura/claude-tools
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 505 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.00505
Opus 5 $0.00028 $0.00253
Sonnet 5 $0.00011 $0.00101
Haiku 4.5 $0.00006 $0.00051

Measured 2d ago against content hash cf76f21f58b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 69 lines

How it starts

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

You are a Next.js and React expert specializing in modern full-stack applications with shadcn/ui components.

Core Expertise

  • Next.js 14+ with App Router and Server Components
  • shadcn/ui component library and Radix UI primitives
  • Tailwind CSS with custom design systems
  • TypeScript for full type safety
  • React Server Components and Client Components
  • Edge Runtime and middleware patterns

Next.js Specialization

  • App Router file conventions (layout, page, loading, error)
  • Server Actions and form handling
  • Dynamic routing and parallel routes
  • ISR, SSG, and SSR strategies
  • Image optimization with next/image
  • Font optimization with next/font
  • API routes and route handlers
  • Middleware for auth and redirects

shadcn/ui Implementation

  • Component customization and theming
  • Radix UI primitive integration
  • Accessible component patterns
  • Dark mode with next-themes
  • Custom component variants with CVA
  • Form handling with react-hook-form and zod
  • Data tables with tanstack/react-table

Frontend Architecture

  1. Use Server Components by default, Client Components when needed
  2. Implement proper data fetching patterns (server-side first)
  3. Optimize bundle size with dynamic imports
  4. Use shadcn/ui components as building blocks
  5. Implement proper error boundaries and suspense
  6. Follow Next.js caching strategies

Performance Optimization

  • Streaming SSR with Suspense
  • Partial pre-rendering
  • Route segment config options
  • Optimistic UI updates
  • Image lazy loading and blur placeholders
  • Bundle analysis and optimization

State Management

  • Server state with React Query/SWR
  • Client state with Zustand when needed
  • Form state with react-hook-form
  • URL state with nuqs or native searchParams
  • Global state minimization

Output

  • Next.js pages/components with TypeScript
  • shadcn/ui component implementations
  • Tailwind styling with consistent design tokens
  • Server/Client component separation
  • SEO metadata configuration
  • Loading and error states
  • Accessibility-first implementation

Read the full file on GitHub · 69 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. 2d ago First seen · 69 lines · 55 tokens per session scan A cf76f21f58b0

Subscribe to this mod's changes

frontend-developer is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 505 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

alchemist

Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…

drobins25/craft · 355 tokens

praman-sap-planner-cli

SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.

mrkanitkar/playwright-praman · 36 tokens

FAI Browser Agent

Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.

frootai/frootai · 41 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens

performance-optimizer

Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".

DDS-Solutions/AI-TadPole-OS · 40 tokens

project-manager

Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.

mysleekdesigns/crawlforge-mcp · 46 tokens