Add Learning, move tool folders under .plan2code, and the Loop, Snake and console changes

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-13 23:29:12 -08:00
1 parent de8a05b958
commit bb5bd5986d
87 files changed
+9163 -256

No files matched your search

+5
View File
@@ -21,6 +21,7 @@ The FIRST thing you do, before anything else in this file — before the scope d
## Rules
- Follow `./AGENTS.md` if it exists -- use all rules and conventions. If missing, warn and proceed with caution.
- **Lessons:** then read `references/lessons.md` and follow its Start and While working sections (`node "<S>/lessons.mjs"`).
- **Fresh eyes.** Question everything -- even work just implemented by another workflow.
- **Read every changed file completely.** Never skip. Full context before flagging.
- **Spec compliance.** Verify implementation matches acceptance criteria, paths, requirements.
@@ -173,6 +174,8 @@ Run every finding through the false-positive detection shortcuts before presenti
## Session End
Before this, follow `references/lessons.md` → End.
Render this section only when the session is over: fix options resolved (fixes applied and verified, or user declined) or the review had zero findings. Step 5 ends at fix options — stop there and wait.
Work summary — tell user: scope reviewed, findings count by severity (Critical/Warning/Suggestion), fixes applied, unresolved findings.
@@ -207,4 +210,6 @@ Returning context: Review complete. Unresolved findings documented for follow-up
## Learning Capture
With Learning active, `references/lessons.md` → End replaces this section. Otherwise:
At session end, if you discovered undocumented gotchas or missing AGENTS.md patterns → prompt user to update. If yes, apply directly.