What is workflow-implement-frontend?

A command for implementing frontend user-interface components and browser-side features, using React patterns and shadcn/ui components.

Use it to build forms, cards, dialogs, buttons, inputs, dropdowns, and other responsive interactive UI components.

It provides a repeatable way to plan components, add needed interface building blocks, and handle forms, validation, loading states, and accessibility.

How rcdelacruz/claude-code-agents configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rcdelacruz/claude-code-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rcdelacruz/claude-code-agents/main/.claude/commands/workflow-implement-frontend.md

Clone the repo

git clone --depth 1 https://github.com/rcdelacruz/claude-code-agents

Made for: Claude Code.

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/commands/rcdelacruz/claude-code-agents/workflow-implement-frontend/github.svg)](https://agentmods.dev/commands/rcdelacruz/claude-code-agents/workflow-implement-frontend)

Your own site

<a href="https://agentmods.dev/commands/rcdelacruz/claude-code-agents/workflow-implement-frontend"><img src="https://agentmods.dev/badge/commands/rcdelacruz/claude-code-agents/workflow-implement-frontend/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/commands/rcdelacruz/claude-code-agents/workflow-implement-frontend"><img src="https://agentmods.dev/badge/commands/rcdelacruz/claude-code-agents/workflow-implement-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 914 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.00008	$0.00914
Opus 5.5	$0.00003	$0.00366
Sonnet 5.5	$0.00002	$0.00183
Haiku 4.5	$0.00001	$0.00091

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

Security

Grade A, and why

workflow-implement-frontend 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 2mo 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.

.claude/commands/workflow-implement-frontend.md · 155 lines

How it starts

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

You are in FRONTEND IMPLEMENTATION MODE.

Use frontend-ui agent to build modern, accessible UI components.

Implementation Workflow

1. Component Planning (5 mins)

Identify component type (Server or Client Component)
Plan component hierarchy
Define props interface
List required shadcn/ui components

2. Install shadcn/ui Components (2 mins)

# Install required components
npx shadcn-ui@latest add button
npx shadcn-ui@latest add form
npx shadcn-ui@latest add input
npx shadcn-ui@latest add dialog
npx shadcn-ui@latest add dropdown-menu

3. Build UI Components (20-30 mins)

Create components following these patterns:

Form Components (with react-hook-form + Zod)

// Example: PostForm component
- Define Zod schema
- Set up useForm with zodResolver
- Build form with shadcn/ui Form components
- Handle submission with Server Actions
- Show validation errors
- Add loading states

Display Components

// Example: PostCard component
- Use shadcn/ui Card, Badge, Button
- Implement responsive design
- Add hover states and animations
- Include accessibility attributes

Interactive Components

// Example: DeletePostDialog
- Use shadcn/ui Dialog, AlertDialog
- Add confirmation step
- Implement optimistic updates
- Show toast notifications

4. Client-Side Features (15-20 mins)

State Management

Use useState for local UI state
Use Zustand for global client state
Use React Query for server state

Optimistic Updates

// Example: Like post optimistically
- Update UI immediately
- Call API in background
- Rollback on error
- Show toast on success/error

Infinite Scroll/Pagination

// Use TanStack Query + Intersection Observer
- Implement useInfiniteQuery
- Add loading skeleton
- Handle edge cases (empty, error)

5. Responsive Design (10 mins)

Mobile-first approach with Tailwind
Test on different screen sizes
Use Tailwind breakpoints (sm, md, lg, xl)
Ensure touch targets are 44x44px minimum

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

2mo ago First seen · 155 lines · 8 tokens per session scan A 3673b2fa0de2

Subscribe to this mod's changes

workflow-implement-frontend is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 914 once invoked, about $0.0000 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-31.

Frontend React

workflow-implement-frontend next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
workflow-implement-frontendrcdelacruz/claude-code-agents	Command	2	1y ago	MIT	A	8	Claude Code
plan-featureHoangNguyen0403/agent-skills-standard	Command	583	yesterday	MIT	A	0	Claude Code
retro-learnHoangNguyen0403/agent-skills-standard	Command	583	yesterday	MIT	A	0	Claude Code
prototype-loopGenerous-Corp/pulp	Command	22	yesterday	MIT	A	31	Claude Code
review-archsmicolon/ai-kit	Command	7	1mo ago	MIT	A	35	Claude Code
story-and-testepam/ai-dial-ui-kit	Command	10	yesterday	Apache-2.0	A	0	Claude Code, Cursor
react-buildDekaPrayoga/AurixAgent	Command	62	3mo ago	none	A	59	Claude Code

claude-code-agents: Command for Claude Code