| name | frontend-development |
| description | Build or refactor React and TypeScript user interfaces in the front or mobile packages. Use for components, pages, interactions, state, accessibility, responsive layout, API integration, and frontend architecture. Do not use for server-only changes. |
Frontend Development
Use this skill for work under omni-platform-front/ or omni-platform-mobile/.
Required Context
- Read the target package README and its
package.json.
- Read the current entry point and nearby components before choosing a pattern.
- Read
references/component-checklist.md when component ownership, interaction, accessibility, or responsive behavior matters.
- Use
karpathy-guidelines for scope control and verification discipline.
Defaults
- Keep state at the lowest owner that needs it; lift only for real coordination.
- Prefer semantic HTML and visible keyboard focus.
- Keep loading, empty, error, and disabled states explicit.
- Reuse existing tokens, components, utilities, and API clients before adding new ones.
- Keep network access behind a typed boundary; do not scatter raw fetch calls across presentation components.
- Use stable responsive dimensions and verify narrow and wide layouts when UI changes.
Verification
Run the affected package build from the repository root. Use browser or screenshot verification for visual or interaction changes when available.