Monorepo NestJS + Nuxt Development

Development rules for a pnpm-based monorepo containing NestJS backend, Nuxt dashboard with Shadcn-vue, and Nuxt frontend with Nuxt UI.

Instructions

Package Manager Rules

1. **Always use `pnpm`** for all package operations

2. Never use npm or yarn commands

3. Use workspace protocol for internal dependencies

Workspace Structure

The monorepo contains three main applications:

#### Backend (`apps/backend/`)

#### Dashboard (`apps/dashboard/`)

#### Frontend (`apps/frontend/`)

NestJS Module Pattern

When creating new NestJS modules, follow this structure:

```

src/modules/{feature}/

├── dto/

│ ├── create-{feature}.dto.ts

│ └── update-{feature}.dto.ts

├── {feature}.controller.ts

├── {feature}.service.ts

├── {feature}.module.ts

└── index.ts

```

**Key practices:**

Vue Component Pattern

**Always use Composition API with `<script setup lang="ts">`:**

```vue

<script setup lang="ts">

// Component logic here

</script>

<template>

<!-- Template here -->

</template>

<style scoped>

/* Styles here */

</style>

```

**For dashboard:** Place UI components in `app/components/ui/`

**For frontend:** Follow Nuxt 3 auto-import conventions

Prisma Workflow

1. Schema location: `apps/backend/prisma/schema.prisma`

2. After any schema changes, run: `pnpm prisma:generate`

3. Apply migrations: `pnpm prisma:migrate`

4. Use Prisma Client from `@prisma/client`

Documentation Structure

Each app maintains its own `AGENTS.md` file:

Common Commands

```bash

Install dependencies

pnpm install

Run backend dev server

pnpm --filter backend dev

Run dashboard dev server

pnpm --filter dashboard dev

Run frontend dev server

pnpm --filter frontend dev

Generate Prisma client

pnpm --filter backend prisma:generate

Run migrations

pnpm --filter backend prisma:migrate

```

Best Practices

1. **Type Safety:** Always use TypeScript with strict mode

2. **Imports:** Prefer absolute imports using path aliases

3. **Components:** Keep components small and focused

4. **API Design:** Follow RESTful conventions in NestJS controllers

5. **Styling:** Use TailwindCSS utility classes; avoid custom CSS when possible

6. **Content:** Use Nuxt Content for static content and documentation pages

Testing

Environment Variables