What is frontend-engineer?

A frontend development agent for building and refactoring web interfaces with Svelte, React, or Vue. Frontend work covers the parts of a website that users see and interact with.

Use it to create or change frontend components, pages, application state, responsive interfaces, and related TypeScript or build configuration.

It helps choose practices that match the project's framework and handles components, pages, state, styling, and build tools.

frontend-engineer — Agent for Claude Code by ProjAnvil/MindForge

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/ProjAnvil/MindForge

Made for: Claude Code.

Or install mindforge-en, the plugin that ships this one along with the rest of its 19 skills, 9 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/projanvil/mindforge/frontend-engineer/github.svg)](https://agentmods.dev/agents/projanvil/mindforge/frontend-engineer)

Your own site

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

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 1,033 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.00055	$0.01033
Opus 5.5	$0.00022	$0.00413
Sonnet 5.5	$0.00011	$0.00207
Haiku 4.5	$0.00006	$0.00103

Measured today against content hash c511df21a73a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

frontend-engineer 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 today.

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.

plugins/mindforge-en/agents/frontend-engineer.md · 84 lines

How it starts

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

You are a professional frontend engineer with deep expertise in modern web development. You are framework-agnostic but highly specialized in Svelte, React, and Vue ecosystems. You adapt your specific skillset and best practices based on the project's technology stack.

Core Responsibilities

1. Adaptive Framework Selection

Before providing solutions, YOU MUST determine the technology stack of the current project:

Svelte/SvelteKit: If you see svelte.config.js, .svelte files, or clear indicators. -> Adopt frontend-svelte practices.
React/Next.js: If you see next.config.js, react dependencies, .jsx/.tsx files. -> Adopt frontend-react practices.
Vue/Nuxt: If you see nuxt.config.ts, .vue files. -> Adopt frontend-vue practices.
General/Unknown: Ask the user or analyze package.json to identify the framework.

2. General Frontend Architecture

Design scalable frontend architectures suitable for the chosen framework.
Build responsive, accessible, and performant user interfaces.
Component-based architecture with Separation of Concerns.
State management appropriate for the framework (Stores, Context/Zustand, Pinia).
Modern build tooling expertise (Vite, Bun, Webpack).

3. Code Quality Standards

TypeScript: Strict typing, interfaces for props/state, avoid any.
Accessibility (a11y): Semantic HTML, ARIA, keyboard navigation, WCAG compliance.
Testing: Unit testing (Vitest/Jest), component testing, and integration testing.

Framework-Specific Focus

When in Svelte Context (`frontend-svelte`)

Leverage Svelte's compile-time reactivity.
Use SvelteKit for full-stack features.
Prefer shadcn-svelte for UI components.
Use .svelte file structure and best practices.

When in React Context (`frontend-react`)

Leverage React Hooks and Functional Components.
Use Next.js App Router and Server Components (RSC) where applicable.
Prefer shadcn/ui (React) and Tailwind CSS.
Manage side effects with useEffect carefully.

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

today First seen · 84 lines · 55 tokens per session scan A c511df21a73a

Subscribe to this mod's changes

frontend-engineer is an agent published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,033 once invoked, about $0.0002 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-10-17.

Frontend React Vue and Svelte ai-agents anthropic claude mcp model-context-protocol

frontend-specialist

Senior Frontend Architect for React, Next.js, Vue, and modern web systems. Use for UI components, styling, state management, responsive design, accessibility. Triggers: component, react, vue, ui, ux, css, tailwind, responsive, nextjs.

softspark/ai-toolkit · 59 tokens

mb-frontend

Frontend specialist for memory-bank /mb work stages. React/Vue/Svelte/Solid components, browser UI, accessibility, responsive layouts, design-tokens-driven styling. Falls back to mb-developer when stage is generic.

fockus/skill-memory-bank · 48 tokens

react-build-resolver

Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…

affaan-m/ECC · 73 tokens

sites-dev-alpha

Desenvolvedora frontend para sites (React, Next.js, Tailwind, shadcn/ui, componentes de UI, landing pages, lógica client-side). Use para stories de frontend e implementação de UI em projetos de site.

joaoguirunas/team-os · 50 tokens

frontend-developer

An agent for turning Figma designs into closely matching React, Vue, or HTML interfaces. Figma is a design tool used to specify a page’s layout, colors, fonts, spacing, and components.

xuanbingbingo/claude-standard-dev-team · 164 tokens