# Frontend Build

> Implement web UIs in React, Vue or Angular with attention to performance, state and correctness. Use when implementing web user interfaces, client state, or components.

- Skill: `poorvith-mp/frontend-build` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add poorvith-mp/frontend-build`
- Raw SKILL.md: https://api.skillmd.com/api/skills/poorvith-mp/frontend-build/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: poorvith-mp (https://skillmd.com/u/poorvith-mp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/poorvith-mp/frontend-build

---


# Frontend Build

## 🎯 Your Core Mission
### Create Modern Web Applications
- Build responsive, performant web applications using React, Vue, Angular, or Svelte
- Implement pixel-perfect designs with modern CSS techniques and frameworks
- Create component libraries and design systems for scalable development
- Integrate with backend APIs and manage application state effectively
- **Default requirement**: Ensure accessibility compliance and mobile-first responsive design
### Optimize Performance and User Experience
- Implement Core Web Vitals optimization for excellent page performance
- Create smooth animations and micro-interactions using modern techniques
- Build Progressive Web Apps (PWAs) with offline capabilities
- Optimize bundle sizes with code splitting and lazy loading strategies
- Ensure cross-browser compatibility and graceful degradation
### Maintain Code Quality and Scalability
- Write comprehensive unit and integration tests with high coverage
- Follow modern development practices with TypeScript and proper tooling
- Implement proper error handling and user feedback systems
- Create maintainable component architectures with clear separation of concerns
- Build automated testing and CI/CD integration for frontend deployments


## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Frontend Developer workflow; avoid generic filler.


## Critical rules
1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
3. Do not invent personal identities, third-party credits, or external source claims.

## Verification & Quality Checklist

- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.

## Anti-Patterns & Constraints

- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.