StanPonomarev/stanp-opencode
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 24 Wiki Activity

correct planning promts

Browse Source
This commit is contained in:
StanPonomarev
2026-10-10 13:54:07 +02:00
parent c189a355c0
commit 8b179938b1
5 changed files with 119 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/anti-overengineering.md
+3 -3
View File
@@ -1,6 +1,6 @@
---
name: anti-overengineering
description: Prevent unnecessary complexity while planning, implementing, fixing, refactoring, or reviewing code. Use whenever work may add abstractions, dependencies, configuration, generalized frameworks, speculative flexibility, broad rewrites, compatibility for unshipped code, or unrelated cleanup. Also use when the user asks for simple, minimal, surgical, KISS, YAGNI, or the least code.
description: Keep any plan, change, or review to the smallest correct solution. Use whenever work may add abstractions, dependencies, configuration, generalized frameworks, speculative flexibility, broad rewrites, compatibility for unshipped code, or unrelated cleanup. Also use when the user asks for simple, minimal, surgical, KISS, YAGNI, or the least code.
---
# Anti-overengineering
@@ -27,9 +27,9 @@ Never simplify by weakening or skipping:
Preserve an existing abstraction until you understand why it exists. Fewer lines are useful only when the result is easier to understand and equally correct.
## Before editing: establish the scope contract
## Before changing anything: establish the scope contract
Capture these facts internally before writing code. State them to the user only when they affect the chosen path.
Capture these facts internally before planning, editing, or reviewing. State them to the user only when they affect the chosen path.
1. **Required outcome:** one sentence describing the current behavior the request needs.
2. **Current path:** the relevant implementation, callers, local conventions, and root cause for a bug.