before-frontend-dev

Reviewing frontend guidelines before coding ensures your React components and hooks match repository standards. This process enforces mandatory pre-coding documentation steps, directing you to relevant spec files for state management and type-safety to prevent inconsistent implementations.

Starting a new TypeScript frontend feature requires reading the main frontend spec and relevant guideline files based on your task type. This approach aligns your implementation with established repository conventions for components, hooks, state management, and type-safety.

You must read frontend type-safety and state management guidelines before implementing changes involving TypeScript types or state handling in ongoing tasks. This mandatory pre-coding review ensures your work matches the repository's required patterns.

This pre-coding guideline review applies to ongoing frontend tasks involving components, hooks, state management, and TypeScript type-safety changes. It requires a comprehensive pass over official specs to ensure your changes match the repository's established patterns.

Reviewing documentation before writing frontend code prevents incorrect implementations by ensuring you understand the project's required patterns for components, hooks, state management, and type safety. This avoids inconsistent code and aligns your work with repository standards.

To find the right frontend docs for a specific component or hook task, navigate to docs/specs/frontend and select the relevant guideline files based on your task type. This task-specific reading directs you to the correct subset of documentation needed before implementation.