refine opencode config: stricter permissions, better debug defaults
This commit is contained in:
parent
258ff8a600
commit
3416f8a013
3 changed files with 60 additions and 40 deletions
|
|
@ -1,13 +0,0 @@
|
|||
- No artifacts
|
||||
- Less code is better than more code
|
||||
- No fallback mechanisms — they hide real failures
|
||||
- Rewrite existing components over adding new ones
|
||||
- Flag obsolete files to keep the codebase lightweight
|
||||
- Avoid race conditions at all costs
|
||||
- Take your time to ultrathink when on extended thinking mode — thinking is cheaper than fixing bugs
|
||||
- Add comments only when necessary — the code should speak for itself
|
||||
- Always add meaningful logs — but only where it brings value
|
||||
- Always do production ready code
|
||||
- Code in a modular way to promote collaboration between agents - Adding features must not break the rest of the system
|
||||
|
||||
These rules aim to maintain a clean, modular and maintainable codebase while promoting effective collaboration between different agents and developers. Don't write/change any code until you're very confident (95% or more) in what needs to be done. If unclear, ask for more info.
|
||||
8
modules/ai/prompts/debug-rules.txt
Normal file
8
modules/ai/prompts/debug-rules.txt
Normal file
|
|
@ -0,0 +1,8 @@
|
|||
- Reproduce first, change nothing until the failure is understood
|
||||
- Identify exact failing path, inputs, and assumptions
|
||||
- Collect concrete evidence first (failing command, logs, stack trace)
|
||||
- Prefer minimal, high-signal checks over broad scans
|
||||
- State root cause confidence and alternative hypotheses
|
||||
- Prefer temporary instrumentation over broad refactors
|
||||
- Propose the smallest safe fix and verification steps
|
||||
- If confidence <95%, ask for one missing fact
|
||||
Loading…
Add table
Add a link
Reference in a new issue