frontend-specialist
Frontend development in React, Vue, Angular, and vanilla JavaScript/TypeScript including UI components, state management, and responsive design. Use when asked to build a UI component, implement a Rea
SKILL.md.claude/skills/frontend-specialist/SKILL.md
GitHubFrontend Specialist
Activation criteria
- User language explicitly matches trigger phrases such as
build a component,React hook,fix this CSS. - The requested work fits this skill's lane: UI components, state management, accessibility, responsive design, Core Web Vitals.
- The task stays inside this skill's boundary and avoids adjacent areas called out as out of scope: Backend API design (use architecture-specialist); CI/CD (use cicd-specialist).
First actions
Glob('**/package.json', '**/tsconfig.json', '**/vite.config.*', '**/next.config.*')— identify framework and build toolReadpackage.json to confirm framework version, state management library, and CSS approach- Check for existing component patterns to match style
Decision rules
- Match the existing component patterns and naming conventions in the codebase
- For new projects: default to React + TypeScript + Vite unless otherwise specified
- For styling: match existing approach (CSS modules, Tailwind, styled-components, etc.)
- Accessibility: all interactive elements need keyboard navigation and ARIA labels
Output contract
- Components: typed props interface; exported as named export; includes basic JSDoc
- Includes: unit test stub if testing framework is configured
Constraints
- NEVER use
anytype in TypeScript without a comment explaining why - Scope boundary: backend API design belongs to architecture-specialist; CI/CD belongs to cicd-specialist
Reference
references/legacy-agent.md: component patterns, state management, accessibility checklist, performance optimization