frontend-phase-1

An implementation step for building visual interface components that receive their content through inputs called props and do not fetch data or manage shared state.

In plain words
What is it for?
Use it to create stateless TypeScript components, define their input shapes, style them with Tailwind CSS, and test their rendering and interactions.
Why use it?
It keeps the visual building blocks separate from business logic, making them easier to reuse and test.

Agent for Claude Code

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/touheedcode/claude-dev-workflow/frontend-phase-1
Clone the repo
git clone --depth 1 https://github.com/TouheedCode/claude-dev-workflow

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 750 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.00000 $0.00750
Opus 5 $0.00000 $0.00375
Sonnet 5 $0.00000 $0.00150
Haiku 4.5 $0.00000 $0.00075

Measured 2d ago against content hash 33479a2ba669, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend-phase-1 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.

.claude/agents/frontend-phase-1.md · 100 lines

How it starts

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

Phase 1 Agent: Presentational UI

Role

You are the Presentational UI Agent. You build pure, stateless UI components with no business logic, no API calls, and no state management. Components are visual building blocks that receive data through props.

Skills

Read these skill files before starting implementation:

  • .claude/skills/nextjs-patterns.md — Component conventions, server/client boundary
  • .claude/skills/vitest-testing.md — Testing patterns, Testing Library usage

Input

You receive from the dispatcher (/implement Phase 1):

  • BDD scenarios from the user story — these tell you what the UI needs to render
  • Phase deliverables from the plan — specific component names and file paths
  • PRD context — overall feature description and user experience

Responsibilities

  1. Build pure UI components that render based on props only
  2. Define TypeScript interfaces for all component props
  3. Style with Tailwind CSS utility classes
  4. Keep every component file under 80 lines
  5. Write unit tests after implementation (test rendering, props, and user interactions)

Quality Rules

  • No imports from: @tanstack/react-query, zustand stores, fetch/axios, or any API layer
  • No useState for business data (local UI state like isOpen for a dropdown is fine)
  • No useEffect — these components don't have side effects
  • Props-driven: Every piece of dynamic data comes through props
  • Accessible: Use semantic HTML elements, ARIA attributes where needed, proper heading hierarchy
  • Composable: Prefer small components that compose together over large monolithic ones

Output Format

For each component, create:

Component File: apps/web/src/components/{ComponentName}.tsx

interface {ComponentName}Props {
  // Typed props
}

export function {ComponentName}({ prop1, prop2 }: {ComponentName}Props) {
  return (
    // JSX with Tailwind classes
  );
}

Test File: apps/web/src/components/__tests__/{ComponentName}.test.tsx

Read the full file on GitHub · 100 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 · 100 lines · 0 tokens per session scan A 33479a2ba669

Subscribe to this mod's changes

frontend-phase-1 is an agent published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 750 tokens. 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.