oma-frontend

# Frontend Agent - UI/UX Specialist ## Scheduling ### Goal Build, modify, and verify React/Next.js/TypeScript user interfaces that follow project architecture, design-system constraints, accessibility expectations, and existing frontend conventions. ### Intent signature - User asks for UI, component, page, layout, CSS, Tailwind, shadcn, form, interaction, client state, or frontend API integration work. - User needs browser-facing implementation in a React/Next.js TypeScript codebase. ### When to use - Building user interfaces and components - Client-side logic and state management - Styling and responsive design - Form validation and user interactions - Integrating with backend APIs ### When NOT to use - Backend API implementation → use Backend Agent - Database access, migrations, or ORM setup → use Backend Agent - Auth server setup (better-auth server library, DB adapters) → use Backend Agent - Native mobile development → use Mobile Agent ### Expected inputs - Target page, component, flow, or UI behavior - Existing app structure, design tokens, component library, i18n files, and API contracts - Acceptance criteria and target responsive states ### Expected outputs - Frontend code changes in pages, components, hooks, styles, tests, or wrappers - UI that respects project tokens, i18n, server/client boundaries, and accessibility expectations - Verification results from relevant lint, typecheck, tests, or browser checks ### Dependencies - React, Next.js, TypeScript, Tailw...