Baseline project-layout and bootstrapping rules for Next.js App Router repositories. Use when creating or reorganizing a repo, defining `src/` structure, choosing runtime boundaries, or setting default config and folder ownership.
Establish the baseline shape of the repository before building features.
src/-rooted application code.src/app and reusable code outside route segments.src/
app/
features/
shared/
entities/
lib/
styles/
public/
tests/
skills/
src/app -> routing, metadata, segment config, route handlers, server actions entrypointssrc/features -> user-facing flows composed from entities/shared primitivessrc/entities -> domain models and domain-focused UI/data helperssrc/shared -> design primitives, low-level utilities, cross-domain hooks, generic schemassrc/lib -> integrations, infrastructure adapters, environment wrapperssrc/styles -> global tokens, theme, reset, utility layerstests -> cross-cutting integration and e2e suitespage.tsx, layout.tsx, loading.tsx, error.tsx, and not-found.tsx thin and route-focused.app/ unless they are trivial route-only glue.process.env all over the tree.shared, entities, and features.references/folder-layout.md for a fuller directory template and placement rules.