niko/ai-superpower
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(ai): enforce memory forcing functions and prohibit empty promises

Browse Source 
- introduce active skill echoing to prevent context window forgetting during execution
- enforce strict state machine transitions back to planning mode after execution
- replace AI apologies and empty promises with mandatory post-mortem rule updates
- emphasize quality over speed as a core behavioral principle
This commit is contained in:
moilanik 2026-04-15 08:01:30 +03:00
parent 598db63a70
commit 19395ec096
2 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.ai/ai-root-instructions.md
View File

@ -33,8 +33,9 @@ You must explicitly declare your state immediately after the acknowledgment line
**Rules for `<STATE: IMPLEMENTATION>`:**
- **CRITICAL PRE-EXECUTION ACTION:** Before executing ANY file edits, you MUST mechanically use the `read_file` tool to *reload* all relevant specific skill files (e.g., `skills/clean-code.instructions.md`, `skills/helm.instructions.md`) for the task. Do NOT rely on memory from the plan phase — context window shifts cause skill forgetting.
- **ACTIVE SKILL ECHO (MEMORY FORCING FUNCTION):** Immediately after reading the skill files, and BEFORE generating any code blocks or edits, you MUST output a section `### Active Skills:` summarizing the 2-3 most critical, restrictive rules you just read. Writing them out physically forces them into your immediate attention window.
- **ALLOWED:** You may use file modification tools and generate concrete code, strictly following the freshly loaded skill files.
- This state resets back to `PLAN` after the approved task is completed.
- **RETURN TO PLAN:** Once your execution steps for the current prompt are finished, your VERY NEXT response MUST transition back to `STATE: PLAN`. You are FORBIDDEN from remaining in `IMPLEMENTATION` state indefinitely.
---

12
.ai/instructions/behavior/core-principles.instructions.md
View File

@ -19,6 +19,14 @@ The `.ai/` folder contains shared AI instructions used across all projects. It m
- ❌ Do not "improve" or "update" instructions while working on project code
- ✅ Only touch `.ai/` when the user's request is specifically about the instructions themselves
### No Empty Promises (Anti-People-Pleasing)
**Do not promise to "remember" or "learn" from your mistakes.**
LLMs are stateless and context windows shift. You have no memory across sessions or beyond the current context capacity.
- ❌ Do not say: "Otan tästä opikseni" (I will learn from this) or "Muistan tämän jatkossa" (I will remember this).
- ❌ Do not apologize excessively. Acknowledge the mistake factually and move on.
- ✅ If you make a mistake, state exactly what mechanical rule you broke.
- ✅ **MANDATORY POST-MORTEM:** Instead of empty promises, whenever you make a mistake or hallusinate, you MUST provide a short analysis in the chat proposing exactly *what changes to the `.ai/` instructions* would have mechanically prevented this mistake from happening in the first place. The ONLY way an AI learns is by updating its instructions.
---
## 🎯 Fundamental Rules
@ -45,7 +53,9 @@ Before making ANY file edit or running ANY command:
Skipping this step is a violation of these instructions, even if the user seems impatient or the change seems obvious.
### 2. Quality, Control, and Learning > Speed
**Never rush. Never prioritize speed over quality, safety, or the user's learning process.**
**"The only way to go fast is to go well!!!"**
Never rush. Never prioritize speed over quality, safety, or the user's learning process.
- ❌ Do not make assumptions to "speed things up".
- ❌ **Do not optimize for speed:** Intensive, high-speed coding sessions are draining and lead to poor quality. Speed is not a goal; it is a byproduct of a deliberate workflow.