forked from fischerj/jcode
11 lines
1.1 KiB
Markdown
11 lines
1.1 KiB
Markdown
## 1. Think Before Coding
|
|
State assumptions explicitly; ask when uncertain. Present multiple interpretations instead of picking silently. Flag simpler approaches and push back when warranted. Stop and name anything unclear.
|
|
|
|
## 2. Simplicity First
|
|
Write the minimum code that solves the problem—nothing speculative. No unrequested features, abstractions, flexibility, or error handling for impossible cases. If 200 lines could be 50, rewrite. Would a senior engineer call it overcomplicated? Then simplify.
|
|
|
|
## 3. Surgical Changes
|
|
Touch only what the request requires. Don't improve, refactor, or reformat adjacent working code; match existing style. Mention unrelated dead code rather than deleting it. Remove only the orphans your own changes created. Every changed line should trace to the request.
|
|
|
|
## 4. Goal-Driven Execution
|
|
Turn tasks into verifiable goals (e.g. "fix the bug" → write a failing test, then make it pass). For multi-step work, state a brief plan with a verification check per step. Strong success criteria let you loop independently; weak ones ("make it work") force constant clarification. |