Frontend Development Workflow

Repository planning gate

When this repository's CLAUDE.md classifies the request as complex or high-impact, the primary agent must invoke plan-tasks before entering this workflow's Plan phase. A subagent must return control to the primary agent rather than create a competing plan or edit target files. Resume this workflow only after an approved docs/plans/PLAN_<descriptive-name>.md maps the relevant A-* to frontend-development-workflow, its assigned role, worktree isolation, and verification. This skill's own planning phase refines the approved action; it never replaces user approval.

Use this skill to complete frontend work through four phases:

1. Plan
2. Orchestrate
3. Develop
4. Verify

For new apps, pages, dashboards, redesigns, components, and non-trivial UI fixes, follow the full workflow. For tiny edits, keep the plan brief but still inspect the existing code and verify the affected UI.

Resource Guide

Load these files only when needed: