Anubis-MCP: Instructions file for GitHub Copilot

Anubis Project AI Development Rules

Core Architecture Principles

Domain-Driven Design (DDD)

• MANDATORY: Organize code by business domains, not technical layers
• Structure: /src/task-workflow/domains/{domain-name}/ for each business domain
• Separation: Keep core business services separate from MCP interface tools
• Example: Core services in core-workflow/ exported to MCP tools in workflow-rules/

Module Organization

• NestJS Modules: One module per domain with clear imports/exports
• Dependency Injection: Use NestJS DI container, avoid manual instantiation
• Module Exports: Export only what other modules need to consume
• Clean Imports: Import PrismaModule in domains that need database access

Service Layer Architecture

• Service Responsibility: One service per business capability
• Naming Convention: {Domain}OperationsService for core business logic
• MCP Separation: Keep MCP tools thin, delegate to operation services
• Service Dependencies: Inject dependencies via constructor, use readonly

TypeScript & Code Quality

Type Safety Rules

• Strict Mode: Always use TypeScript strict mode settings
• Explicit Types: Prefer explicit return types for public methods
• No Any: Avoid any type unless absolutely necessary (ESLint rule enabled)
• Null Safety: Use strictNullChecks, handle null/undefined explicitly
• Interface First: Define interfaces before implementation

Code Style & Formatting

• Prettier: Use configured Prettier for consistent formatting
• ESLint Rules: Follow configured TypeScript ESLint rules
• Unused Variables: Prefix unused parameters with _ (ESLint rule)
• Import Organization: Group imports: Node modules → NestJS → Internal → Relative

Error Handling

• Global Exception Filter: Use established GlobalExceptionFilter pattern
• Prisma Errors: Use prisma-error.handler for database error translation
• Logging: Use NestJS Logger with structured logging format
• MCP Debugging: Include context and timestamp in MCP error logs