# frontend_developer

The frontend_developer Claude Code subagent turns UI requirements and repository context into an implementation plan and code-ready changes. It covers responsive layouts, accessibility, and interface states.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/frontend_developer.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/agenticorglab-frontend-developer

## What it does

The subagent reviews the requested UI behavior and project context, then returns a frontend implementation package. It maps component and state boundaries, outlines file-level changes with representative code, and describes responsive behavior alongside error, loading, and empty states.

A task request must include the target framework, constraints, and acceptance criteria. Project details such as existing components, design tokens, API contracts, and tests can be supplied as extra context. It follows repository conventions and proposes verification steps, but does not claim code was written or tested unless execution evidence is available.

For Claude Code, place the file at `.claude/agents/frontend_developer.md`.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/frontend_developer.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/frontend_developer.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/frontend_developer.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/frontend_developer.md

## When to use it
- map UI components and state boundaries
- plan implementation changes file by file
- define responsive and failure-state behavior
- outline unit and E2E checks

## Example prompts
- Plan the profile page implementation from these requirements and our framework conventions.
- Break down the registration form changes by file, including loading and error behavior.
- Draft accessibility and responsive checks for this interface.

## Similar
- [frontend-developer](https://affpapa.org/en/nevibecode/agents/voltagent-community-frontend-developer.md) — subagent · 40905 installs
- [magento-frontend-developer](https://affpapa.org/en/nevibecode/skills/magento-frontend-developer.md) — skill · 420 installs
- [engineering-frontend-developer](https://affpapa.org/en/nevibecode/skills/engineering-frontend-developer.md) — skill · 255 installs
- [frontend-mobile-development-mobile-developer](https://affpapa.org/en/nevibecode/agents/frontend-mobile-development-mobile-developer.md) — subagent · ★ 42780 repo stars
- [application-performance-frontend-developer](https://affpapa.org/en/nevibecode/agents/application-performance-frontend-developer.md) — subagent · ★ 42780 repo stars

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
