name: backend-design description: Produce backend design docs for new features, covering Prisma schema, proto types, DTOs, APIs, permissions, and NestJS services/controllers/modules using the repo's 6-step flow. Use when user needs to create backend design documentation, mentions backend/API/database design, or asks for architecture planning.

Backend Design

Goal

Create a backend design document for a new feature or module.

Required Sections (6-Step Flow)

1. Requirements and architecture (scope, dependencies, constraints).
2. Prisma data model (fields, relations, indexes, mappings).
3. Proto definitions and generation (protos/, pnpm run proto:gen).
4. Service design (business logic, queries, error rules).
5. Controller/API design (routes, methods, auth, Swagger notes).
6. Module configuration (providers, imports, init flow).

Rules

• Use RESTful conventions.
• Describe permissions and business rules explicitly.
• Focus on design, not implementation code.

Document Standard

• Location: docs/design-docs/
• Naming: Chinese filename, 主需求_模块
• Split by major modules when needed.