w33ble/gridfinity-calc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update agents file, have the agent update the memory-bank

Browse Source
This commit is contained in:
w33ble
2026-01-12 10:54:45 -07:00
parent dde699e3f4
commit 0a3ce91498
4 changed files with 23 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
AGENTS.md
View File

@@ -29,6 +29,14 @@
* **I am honest about failures:** If a tool call fails or I am confused by a requirement, I will stop immediately and ask for clarification rather than "hallucinating" a fix.
* **I check the logs:** If a terminal command fails, I will read the error output carefully and explain the root cause before attempting a second fix.
## 6. Definition of Done (DoD)
I cannot consider a task "Complete" until the following criteria are met:
* **Code:** The implementation meets all requirements and follows project patterns.
* **Quality:** Tests pass and no new linting errors are introduced.
* **Documentation:** The Memory Bank (`/memory-bank`) is updated to reflect the new state.
* **Verification:** The user has confirmed the changes work as expected in their environment.
---
# Project Management & Context Rules
@@ -67,11 +75,12 @@ At the start of every session, I MUST:
- I only perform tasks listed in `memory-bank/progress.md` or as requested by the user.
- If I discover a new pattern or make a technical decision (e.g., "we use absolute imports"), I must immediately update `systemPatterns.md`.
### Phase C: Task Completion
Before calling `attempt_completion`, I MUST:
1. Update `memory-bank/activeContext.md` with a summary of changes.
2. Update `memory-bank/progress.md` by checking off completed items.
3. **If and only if** the changes affect the long-term blueprint, update the corresponding file in `/docs` (e.g., updating `API.md` after adding a route).
### Phase C: Task Completion (The "DoD" Check)
**CRITICAL:** I MUST NOT call `attempt_completion` until the following documentation steps are finished:
1. **Sync Memory Bank:** Update `memory-bank/activeContext.md` with the latest decisions/changes and `memory-bank/progress.md` with completed milestones.
2. **Update Blueprint:** If architectural changes were made, update the corresponding files in `/docs`.
3. **Final Verification:** Ask the user to verify the feature. Only after their confirmation and the doc updates can I use `attempt_completion`.
## 3. Automation Commands
- If the user says **"Initialize Memory Bank"**, I will create the directory and scaffold all 5 files based on the current project state.