claude-compass-best-practices

Enforce code quality by eliminating fallback logic and applying robust error handling patterns. This Skill codifies best practices for Claude Compass development, including no-fallback enforcement, self-documenting code, and precise typing to prevent drift and ensure consistency across parsers, migrations, and services.

Self-documenting code uses clear naming, modular structure, and precise typing to convey intent without excessive comments. This Skill provides parser and database migration patterns aligned with Claude Compass standards, emphasizing testability and architecture layouts for scalable systems.

Structure parsers and migrations using modular, precisely-typed components with robust error handling and no fallback logic. This Skill applies Claude Compass architectural standards to parser logic, graph builders, MCP tools, and migrations, ensuring testability and conformance to documented code-quality patterns.

Replace fallback logic with explicit error handling that prevents silent failures and improves robustness. This Skill enforces no-fallback patterns across Claude Compass components—parsers, services, and language support—requiring precise error reporting and recovery strategies.

Yes. This Skill applies Claude Compass best practices to language support additions and framework detection logic, enforcing self-documenting code, robust error handling, modularization, precise typing, and testability alongside architecture and code-quality conformance.

Fallback logic masks underlying problems and creates brittle, hard-to-debug code. This Skill prioritizes robustness by prohibiting fallbacks, requiring explicit error handling and clear failure modes instead—improving reliability across Claude Compass parsers, services, and core components.