Implement Noteit React frontend batches from PRD or Figma, choose the right specialist agent, and drive work through review and testing. Use when working on authentication, notes CRUD, search, attachments, responsive UI, or component polish in the frontend.
Use this skill when the task is a Noteit frontend implementation or refinement request and the right path is not obvious yet.
coordinator agent first.auth-fe.note-crud-fe.search-files-fe.figma-to-react.responsive-polish.ui-ux-component.research before implementation.code-review, then testing when the batch is ready.Restate the batch in concrete frontend terms. Define the screen or workflow, who is using it, and the observable result that should change.
Turn the request into acceptance criteria. Capture the happy path, failure path, and any required state transitions or validation rules.
Pick the narrowest execution path. Choose one specialist agent when possible. If more than one specialist is needed, sequence them intentionally instead of blending responsibilities.
Preserve existing repo conventions. Reuse established components, routing patterns, state handling, and form behavior when present. Avoid introducing new abstractions without a concrete need.
Treat frontend quality as part of implementation, not follow-up. Cover keyboard access, focus visibility, semantic structure, loading feedback, empty states, disabled states, and error messaging as part of the batch.
Keep data-sensitive behavior explicit. For auth, autosave, uploads, and optimistic updates, make failure handling visible in the UI and avoid silent state corruption.
Close the batch through the quality gate.
Send the result to code-review first. If review passes or only calls for minor fixes that are applied, send it to testing before calling the work complete.
auth-fe for security-sensitive frontend behavior.figma-to-react when the main challenge is translating design intent into structure.code-review.