enforce-commandments

name	enforce-commandments
description	This skill should be ALWAYS ACTIVE during software development. It automatically enforces the 10 Engineering Commandments when the user is writing code, planning features, creating specifications, designing architecture, or reviewing code. Auto-activates on keywords like "implement", "build", "create", "refactor", "design", "architecture", "component", "service", "endpoint", or "module".

Engineering Commandments Enforcement

Enforce the 10 Engineering Commandments during all development activities. This skill auto-activates during code writing, planning, specification, and review.

The 10 Commandments

Ensure ALL outputs comply with:

1. Design for Failure

Systems should expect and gracefully handle failures

• Error boundaries and fallback states
• Retry logic with exponential backoff
• Circuit breakers for external dependencies
• Graceful degradation paths

2. Keep It Simple

Complexity breeds bugs that testing may not catch

• Prefer straightforward solutions over clever ones
• Avoid premature optimization
• Limit nesting depth (max 3 levels)
• One function = one purpose

3. Test Early and Often

Testing is not optional, it's fundamental

• Unit tests for all business logic
• Integration tests for critical paths
• Test plan BEFORE implementation
• No PR without test coverage

4. Build for Observability

You cannot improve what you cannot measure

• Structured logging (not console.log)
• Metrics for key operations
• Tracing for distributed flows
• Health check endpoints

5. Document Thy Intent