before-frontend-dev

To align frontend code with project guidelines, review the repository spec and identify relevant files for components, hooks, state management, and type-safety before implementation. This mandatory pre-development review ensures coding consistency and structured planning.

Frontend development guidelines are project-specific standards for components, hooks, state management, and type-safety. They are needed before starting any frontend task to prevent inconsistent code and wasted effort from unaligned development practices.

Start frontend onboarding by opening the repository spec to read and understand the frontend guidelines. This standardizes coding practices for new developers, accelerating kickoff by ensuring adherence to component and hook standards.

Yes, the pre-development review applies to state management and hook guidelines. It identifies and applies relevant guideline files from the repository spec to your specific task, ensuring type-safety considerations and component standards are met.

Unaligned frontend development causes inconsistent code because developers dive into tasks without consulting project guidelines. Bypassing the mandatory review of component, hook, and state management standards leads to wasted effort and fragmented codebases.

The best way to plan a frontend task is to review the official guidelines in the repository spec first. This creates a structured implementation plan that satisfies project-specific requirements for components, hooks, state management, and type-safety.