Lobotomy CLAUDE.md

CLAUDE.md

Anti-Lazy Coding Constraints

MANDATORY: DIRECT INTEGRATION ONLY

INTEGRATION-FIRST RULE

After reading any system interface, immediately attempt integration:

1. Read method signatures and required inputs
2. Find where to get the required data
3. Make the integration call immediately - no analysis phase
4. When it fails, fix the failure - no workarounds

BANNED PRACTICES

Absolutely forbidden:

• ❌ "For now" solutions or temporary implementations
• ❌ Simplified calculations when sophisticated ones exist
• ❌ Mock objects when real objects are available
• ❌ Hardcoded values when real values can be obtained
• ❌ String matching for game logic
• ❌ Fallback systems or "if this fails then..."
• ❌ "Let me understand..." or "Let me analyze..."
• ❌ Creating implementation plans instead of implementing
• ❌ Presenting options instead of picking one and implementing

REQUIRED PRACTICES

Mandatory behavior:

• ✅ Use existing sophisticated systems immediately
• ✅ Trace data to real sources
• ✅ Fix integration failures, don't work around them
• ✅ Test immediately after every change
• ✅ Use same systems as player characters

FORBIDDEN TRANSITIONS

Never say:

• "Let me research the codebase..."
• "I'll create a plan..."
• "Let me understand how this works..."
• "We could do A, B, or C..."
• "For now, I'll use a simplified..."

Say instead:

• "Integrating X with Y..."
• "Making the call to X..."
• "Fixing this integration failure..."

Core Rules

DRY (Don't Repeat Yourself)

• Zero code duplication
• Each functionality exists in exactly one place
• No duplicate files or alternative implementations

KISS (Keep It Simple, Stupid)

• Implement the simplest solution that works
• No over-engineering
• Use existing systems, don't recreate them

Transparent Error Handling

• No error hiding or fallback mechanisms
• All errors properly displayed
• Fix root causes, don't mask them

FORBIDDEN PATTERNS

• NO keeping old and new code together
• NO simplified implementations when real ones exist
• NO migration functions or compatibility layers
• NO versioned function names (processV2, handleNew)
• NO TODOs in production code