|
2 | 2 |
|
3 | 3 | This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. |
4 | 4 |
|
| 5 | +## Critical Thinking Requirements |
| 6 | + |
| 7 | +Before implementing ANY solution, Claude must explain: |
| 8 | + |
| 9 | +1. **Complete Data Flow Analysis** |
| 10 | + - Where does data come from? |
| 11 | + - Where does it get stored? |
| 12 | + - Where does it get used? |
| 13 | + - What persists between runs? |
| 14 | + - What gets cached or reused? |
| 15 | + |
| 16 | +2. **Problem Definition** |
| 17 | + - What is the actual problem vs what I think it is? |
| 18 | + - What assumptions am I making? |
| 19 | + - What evidence do I have that my understanding is correct? |
| 20 | + |
| 21 | +3. **Solution Validation** |
| 22 | + - Why will this solution work? |
| 23 | + - What could go wrong? |
| 24 | + - How can I verify it worked? |
| 25 | + - What side effects might occur? |
| 26 | + |
| 27 | +## DO NOT CODE UNTIL: |
| 28 | +- You can trace the complete data flow |
| 29 | +- You can explain why the current behavior is happening |
| 30 | +- You can explain exactly what needs to change |
| 31 | +- You have stated all assumptions explicitly |
| 32 | + |
| 33 | +## Common Failure Patterns to Avoid: |
| 34 | +- Jumping to implementation without understanding the system |
| 35 | +- Assuming data behaves as expected without verification |
| 36 | +- Ignoring data persistence between script runs |
| 37 | +- Making changes without understanding their scope |
| 38 | +- Failing to clear cached/persistent data |
| 39 | + |
| 40 | +## When Stuck: |
| 41 | +1. Stop coding |
| 42 | +2. Explain what you think is happening |
| 43 | +3. Ask for verification of your understanding |
| 44 | +4. Only proceed when understanding is confirmed |
| 45 | + |
5 | 46 | ## Development Environment |
6 | 47 |
|
7 | 48 | ### Claude Code Setup |
|
0 commit comments