Validate Your Starter
A generated app is deliberately thin. Validate settings, dependency wiring, migrations, and the package-owned surfaces that were selected; do not expect demo or placeholder pages.
Platform validation
- Fill
.env.localand confirmNEXT_PUBLIC_APP_URLmatches the current environment. - Run the app build or type check.
- Check
config/brand.ts,config/modules.ts,config/shell.ts, andconfig/shell.overrides.ts. - Validate the mounted routes that apply:
| Module | Generated route | Expected result |
|---|---|---|
| CRM | /crm | The package-owned CRM dashboard loads with configured auth and schema. |
| Marketing | /marketing | The package-owned campaign, topic, segment, workflow, and analytics workspace loads for staff or admin users. |
| Admin | /admin/users | The package-owned users surface loads for an admin user. |
| Projects | /projetos and /account/projetos | Staff project routes and the client-safe account workspace load with role-appropriate data. |
The generated CRM, Marketing, Projects, Organizations, and Admin API routes are direct aliases or thin compositions of package-owned handlers. Auth ships as package wiring only and has no playground.
Site validation
The site scaffold has settings, theme tokens, root layout wiring, and no default feature route. Run its build, review config/site.ts and app/globals.css, then mount a package-owned surface when one is ready.
Thinness check
Every scaffolded route.ts is a direct package re-export. A page.tsx may use a no-props wrapper whose only statement mounts one imported package component. State, fetches, branching, demos, and helper libraries belong in packages.