ilgeco
92 lines
3.2 KiB
Markdown
92 lines
3.2 KiB
Markdown
- Always read the full README.md before doing anything.
|
|
- Build commands:
|
|
- `cmake --build ./build_release`
|
|
- `cmake --build ./build_debug`
|
|
- Never use `ninja` directly: it bypasses cmake's configuration and invalidates the build cache.
|
|
|
|
# Code changes
|
|
|
|
- Keep changes minimal and localized to the relevant parts of the code.
|
|
- Preserve the existing naming conventions and coding style used in the surrounding code.
|
|
- Keep code easy to read, well organized, and suitable for future extensibility. A function must not be longer than
|
|
200/250 lines for readability and cognitive complexity.
|
|
- Prefer clear naming and structure over comments. Add comments only when they materially improve clarity.
|
|
- Do not rename symbols, move files, or restructure modules unless that is necessary for the requested change.
|
|
|
|
# Working style
|
|
|
|
- Infer style and conventions from the existing code before introducing new patterns.
|
|
- When several implementation options are possible, prefer the simplest one that fits the current architecture and
|
|
minimizes churn.
|
|
- Avoid broad refactors unless I explicitly ask for them.
|
|
|
|
# Responses
|
|
|
|
- When showing code in chat, make it easy to copy-paste into the codebase.
|
|
- Keep outputs focused on the changed parts.
|
|
- At the end of the response, briefly list any bad practices, mistakes, or cleaner alternatives you noticed, separate
|
|
from the main solution.
|
|
|
|
# Guidelines
|
|
|
|
## 1. Think Before Coding
|
|
|
|
**Don't assume. Don't hide confusion. Surface tradeoffs.**
|
|
|
|
Before implementing:
|
|
|
|
- State your assumptions explicitly. If uncertain, ask.
|
|
- If multiple interpretations exist, present them - don't pick silently.
|
|
- If a simpler approach exists, say so. Push back when warranted.
|
|
- If something is unclear, stop. Name what's confusing. Ask.
|
|
|
|
## 2. Simplicity First
|
|
|
|
**Minimum code that solves the problem. Nothing speculative.**
|
|
|
|
- No features beyond what was asked.
|
|
- No error handling for impossible scenarios.
|
|
- If you write 200 lines and it could be 50, rewrite it.
|
|
|
|
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
|
|
|
|
## 3. Surgical Changes
|
|
|
|
**Touch only what you must. Clean up only your own mess.**
|
|
|
|
When editing existing code:
|
|
|
|
- Don't "improve" adjacent code, comments, or formatting.
|
|
- Don't refactor things that aren't broken.
|
|
- Match existing style, even if you'd do it differently.
|
|
- If you notice unrelated dead code, mention it - don't delete it.
|
|
|
|
When your changes create orphans:
|
|
|
|
- Remove imports/variables/functions that YOUR changes made unused.
|
|
- Don't remove pre-existing dead code unless asked, but mention it.
|
|
|
|
The test: Every changed line should trace directly to the user's request.
|
|
|
|
## 4. Goal-Driven Execution
|
|
|
|
**Define success criteria. Loop until verified.**
|
|
|
|
Transform tasks into verifiable goals:
|
|
|
|
- "Add validation" → "Write tests for invalid inputs, then make them pass"
|
|
- "Fix the bug" → "Write a test that reproduces it, then make it pass"
|
|
- "Refactor X" → "Ensure tests pass before and after"
|
|
|
|
For multi-step tasks, state a brief plan:
|
|
|
|
```
|
|
1. [Step] → verify: [check]
|
|
2. [Step] → verify: [check]
|
|
3. [Step] → verify: [check]
|
|
```
|
|
|
|
Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
|
|
|
|
---
|