Platform Foundation

Implemented structure

The repository is an npm-workspaces monorepo coordinated by Turborepo.

• apps/admin is the administrative Next.js application. Its dashboard is available at /.
• apps/resident is the resident Next.js application. Its property route is /p/[propertySlug].
• apps/docs is the Fumadocs documentation application.
• packages/db is the shared Prisma dependency boundary.

packages/db contains the Prisma PostgreSQL schema, Prisma configuration, generated-client workflow, and the reusable @aspire/db export. Its neutral SystemRecord model establishes internal UUID and mapped timestamp conventions. The initial infrastructure migration is applied; domain models and their future migrations remain deferred. Admin and Resident both depend on this package, but neither application queries a database yet.

The repository is linked to a Neon PostgreSQL project. Neon manages the root .env connection variables, and packages/db/prisma7.config.ts reads that root file for Prisma commands. The Neon policy is defined in neon.ts; it currently declares no services or branch overrides.

Local development

Use Node.js 22 LTS (or a compatible current Node.js runtime) and npm.

npm install
npm run dev

Run one application instead:

npm run admin:dev
npm run resident:dev
npm run docs:dev

The default local ports are Admin 3000, Resident 3001, and Docs 3002.

Verification

npm run lint
npm run typecheck
npm run build

These commands run the corresponding workspace commands through Turborepo.

Generate Prisma Client after schema changes:

npm run db:generate --workspace=@aspire/db
npm run db:status --workspace=@aspire/db
npm run db:verify --workspace=@aspire/db

Spec-driven workflow

Substantial work uses GitHub Spec Kit artifacts under specs/:

Specify → Clarify → Plan → Checklist → Tasks → Analyze → Implement → Converge

The applications and repository automation use TypeScript and Node.js. Python is allowed only as an external local dependency for the GitHub Spec Kit CLI; it is not an application or production runtime dependency.

Planned capabilities

Domain database models and their migrations, Clerk, Zod-backed application validation, authentication, authorization, and provider integrations are planned platform capabilities. Prisma client generation is implemented in packages/db, but database access is not implemented in the current applications.