LifeOS

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

API DTO and response contract rules for LifeOS backend/frontend compatibility. Use when adding or changing endpoints, request/response DTOs, error payloads, versioning decisions, or Swagger/OpenAPI documentation.

Authentication and ownership enforcement rules for LifeOS multi-user isolation. Use when creating or changing auth flows, guarded endpoints, user-scoped queries, or nested resource access checks.

Clean Architecture + DDD rules for this repo. Triggers: adding/refactoring code across src/domain|application|infrastructure, moving files between layers, creating ports/adapters/use-cases.

Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.

Repository documentation conventions for LifeOS. Use when creating or updating README, docs/*, architecture notes, API behavior notes, or implementation decisions that must remain clear for future contributors and agents.

PostgreSQL schema and query safety rules for LifeOS. Use when changing tables, indexes, constraints, migrations, date handling, performance-sensitive queries, or any persistence design decision.

Prisma + PostgreSQL conventions for LifeOS persistence. Use when editing schema.prisma, generating migrations, implementing repositories/adapters, tuning transactions, or mapping Prisma models to application/domain contracts.

React web feature architecture guidelines for LifeOS. Use when creating pages, feature modules, forms, API hooks, global stores, and UI composition in frontend/src for scalable and testable structure.

Incremental refactor playbook for moving legacy LifeOS code toward Clean Architecture/DDD. Use when splitting monolithic services/controllers, introducing ports/adapters, or migrating features without breaking current behavior.

Business rules for LifeOS review scheduling and mastery scoring. Use when implementing or modifying study session completion, review generation, interval multipliers, urgency calculation, or topic mastery updates.

Vitest testing patterns for LifeOS backend and frontend. Use when adding unit/integration tests, refactoring behavior, fixing regressions, or validating business rules such as ownership and spaced review scheduling.

Strict TypeScript guidance for LifeOS backend (NestJS) and frontend (React). Use when creating or refactoring DTOs, domain/application types, API client types, generics, type guards, or when resolving TypeScript errors without weakening type safety.