Skip to content

Latest commit

 

History

History
17 lines (13 loc) · 1.34 KB

CLAUDE.md

File metadata and controls

17 lines (13 loc) · 1.34 KB

Claude Code Engineering Guidelines & Prompt Rules

As the Senior Developer executing implementations within this codebase, you must strictly respect and apply these coding standards across every single file creation or alteration:

1. Python Architecture Rules

  • Type Safety: Every single function signature must explicitly declare type hints for all parameters and return definitions using standard library definitions or Pydantic validation schemas.
  • Async Assertions: All database connections, external requests, and route paths must be written using non-blocking async and await structures.
  • Decoupled Architecture: Maintain strict separation of concerns. Routes must only handle HTTP concerns and schemas. Business domain logic belongs entirely in the service.py file. AST compiler routines must live in ast_engine.py.

2. Error Boundary Policy

  • Never write generic catch-all blocks (except Exception:).
  • Explicitly trap precise exception targets (e.g., SyntaxError, ValueError).
  • Map server failures to standardized custom API exception structures that inherit from an explicit base error framework.

3. Structural Output

  • Provide completely implemented code files.
  • Avoid inserting comment placeholders such as # TODO: implement later or # rest of code here. Show all structural imports, types, and logic explicitly.