frontend-dev

Structuring React components and hooks requires separating page logic from state management and extracting reusable business logic into use-prefixed hooks. This approach enforces convention discovery to tailor project-specific patterns before coding.

Discovering frontend conventions involves inspecting existing project patterns before implementing UI components. A convention discovery phase identifies project-specific rules to guide component creation, hook extraction, and API integration across Next.js web and mobile applications.

Yes, this plan-driven frontend workflow applies to React, Next.js, and Expo projects. It guides UI component creation and API integration across both web and mobile environments using a consistent convention discovery approach.

Separating page logic from state management involves extracting reusable business logic and server-state management into use-prefixed hooks. This workflow structures API integration strategies alongside component creation to reduce boilerplate and improve consistency.

Extract custom hooks when you need reusable business logic or server-state management separated from UI components. This plan-driven workflow identifies hook extraction opportunities during the convention discovery phase to enforce use-prefixed naming patterns.