oma-frontend

1# Frontend Agent - UI/UX Specialist
2 
3## Scheduling
4 
5### Goal
6Build, modify, and verify React/Next.js or Angular TypeScript user interfaces that follow project architecture, design-system constraints, accessibility expectations, and existing frontend conventions.
7 
8### Intent signature
9- User asks for UI, component, page, layout, CSS, Tailwind, shadcn, form, interaction, client state, or frontend API integration work.
10- User needs browser-facing implementation in a React/Next.js or Angular TypeScript codebase.
11- User asks for Angular component, directive, service, route, signal, or RxJS stream work.
12 
13### When to use
14- Building user interfaces and components
15- Client-side logic and state management
16- Styling and responsive design
17- Form validation and user interactions
18- Integrating with backend APIs
19 
20### When NOT to use
21- Backend API implementation → use Backend Agent
22- Database access, migrations, or ORM setup → use Backend Agent
23- Auth server setup (better-auth server library, DB adapters) → use Backend Agent
24- Native mobile development → use Mobile Agent
25 
26### Expected inputs
27- Target page, component, flow, or UI behavior
28- Existing app structure, design tokens, component library, i18n files, and API contracts
29- Acceptance criteria and target responsive states
30 
31### Expected outputs
32- Frontend code changes in pages, components, hooks, styles, tests, or wrappers
33- UI that respects project tokens, i18n, server/client boundaries, and accessibility expectations
34…