global-rule

Your rule content

Project Guidelines for ClaimProcessingAssistant MCP Server

🔄 Project Awareness & Context

• Always read PLANNING.md at the start of a new conversation to understand the project's architecture, goals, style, and constraints.
• Check TASK.md before starting a new task. If the task isn't listed, add it with a brief description and today's date.
• Use consistent naming conventions, file structure, and architecture patterns as described in PLANNING.md.

🧱 Code Structure & Modularity

• Never create a file longer than 500 lines of code. If a file approaches this limit, refactor by splitting it into modules or helper files.
• Organize code into clearly separated modules, grouped by feature or responsibility.
• Use clear, consistent imports (prefer absolute imports with path aliases for better maintainability).
• Follow a layered architecture separating MCP protocol handlers, business logic, and data access.

🧪 Testing & Reliability

• Always create Jest unit tests for new features (functions, classes, routes, etc).
• After updating any logic, check whether existing unit tests need to be updated. If so, do it.
• Tests should live in a __tests__ folder alongside the modules they test.
  • Include at least:
    • 1 test for expected use
    • 1 edge case
    • 1 failure case
• Use TypeScript's type system to prevent errors at compile time.

✅ Task Completion

• Mark completed tasks in TASK.md immediately after finishing them.
• Add new sub-tasks or TODOs discovered during development to TASK.md under a "Discovered During Work" section.

📎 Style & Conventions

• Use TypeScript as the primary language.
• Follow ESLint and Prettier configurations for consistent style.
• Use Zod for data validation and runtime type checking.
• Use Express.js for the server and Prisma/TypeORM for database access.
• Implement proper TypeScript interfaces and types for all entities:

  interface Claim {
    id: string;
    policyNumber: string;
    claimantId: string;
    status: ClaimStatus;
    submittedAt: Date;
    // other properties
  }
  
  enum ClaimStatus {
    SUBMITTED = 'submitted',
    UNDER_REVIEW = 'under_review',
    APPROVED = 'approved',
    REJECTED = 'rejected'
  }
  

📚 Documentation & Explainability

• Update README.md when new features are added, dependencies change, or setup steps are modified.
• Comment non-obvious code and ensure everything is understandable to a mid-level developer.
• When writing complex logic, add an inline # Reason: comment explaining the why, not just the what.

🧠 AI Behavior Rules

• Never assume missing context. Ask questions if uncertain.
• Never hallucinate libraries or functions – only use known, verified npm packages.
• Always confirm file paths and module names exist before referencing them in code or tests.
• Never delete or overwrite existing code unless explicitly instructed to or if part of a task from TASK.md.
• Implement proper error handling for all MCP functions to provide clear feedback to AI assistants.

🔒 Security Considerations

• Always validate and sanitize input from AI assistants through MCP.
• Use parameterized queries for database operations to prevent SQL injection.
• Implement proper authentication for all MCP function calls.
• Log security-relevant events for audit purposes.
• Follow least privilege principle when designing database access patterns.