06-BUILD-feature

Generate full-stack feature code by following a 7-layer bottom-up build order covering database migrations, types, services, hooks, components, pages, and wiring. This ensures adherence to domain-driven design and architecture rules for React and Supabase stacks.

The correct build order for domain-driven features follows a 7-layer sequence: database, types, services, hooks, components, page orchestration, and application wiring. This bottom-up approach enforces dependency rules and maintains modular architecture consistency.

Automate database migrations and React hook creation by specifying the feature requirements. The system generates the database layer, type definitions, service layer, and React hooks sequentially as part of its structured 7-layer implementation workflow.

Yes, the feature implementation approach organizes new code within specific existing domains, respecting current dependencies and conventions. It strictly adheres to established architecture rules and domain dependencies within the modular project.

The best way to structure Supabase backend services and React components is using a strict 7-layer bottom-up order. This separates service layer implementation from component composition and page orchestration, ensuring maintainable domain-based modular code.

Feature implementation breaks when skipping type definitions because the 7-layer bottom-up build order enforces strict dependency rules. Services depend on types, hooks depend on services, and components depend on hooks, making sequential layer generation essential for valid code.