feature-scaffold

Scaffold new Next.js feature directories by generating structured folders for server actions, queries, schemas, and UI components that enforce workspace-scoped workflows and business-logic separation. This ensures new features align with existing route structures and platform conventions.

Organize server actions and queries in a feature folder by separating data access, schemas, and API handlers into dedicated subdirectories. This approach isolates business logic from feature components and maintains consistency with oRPC and next-safe-action patterns.

Yes, building workspace-scoped features requires next-safe-action for action validation, oRPC for routing, and next-intl for localization. These dependencies enforce structured logging and workspace-aware authentication checks across the scaffolded feature architecture.

Structure localized pages by using server-component page flows that pass promises to client-components, wrapping forms in Card-based layouts, and applying next-intl translations. This pattern ensures localization standards are met without breaking feature folder conventions.

Feature architecture violates workspace-aware auth checks when API handlers and server actions bypass workspace-scoped workflows. Scaffold features with next-safe-action and structured logging to enforce authentication boundaries and maintain route structure integrity.

Yes, the scaffolding pattern applies to both builder app pages and public routes in workspace-scoped workflows. It generates directory structures for API handlers, UI components, and server actions while maintaining platform conventions for each route type.