Feature Structure

A standardized directory layout organizes each feature under app/features into a canonical 6-file model: server.ts, service.ts, repository.ts, types.ts, constants.ts, and index.ts. This structure establishes explicit module boundaries and a defined index export pattern for type-safe composition.

To organize LivestockAI features, create a directory under app/features and populate it with server.ts, service.ts, repository.ts, types.ts, constants.ts, and index.ts. This standardizes module boundaries and documents directory responsibilities to reduce onboarding friction.

Yes, the modular feature structure supports optional shared component resources. You can use sibling directories such as scripts/, references/, and assets/ alongside the standardized feature files to provide richer functionality when needed.

You use a 6-file feature model to enforce a frontmatter-driven metadata contract and consistent infrastructure across server, service, repository, types, and constants files. This promotes maintainable architecture and reliable feature discovery.

The best way to enforce explicit module boundaries is adopting a canonical 6-file model per feature directory, utilizing index.ts to standardize exports. This defined index export pattern enables reliable discovery and type-safe composition across the application.