| name | learn |
| preamble-tier | 2 |
| version | 1.0.0 |
| description | "I know kung fu." Upload, review, search, prune, and export what the construct
has learned across sessions. Learnings compound so the simulation gets smarter
on your codebase over time. Use when asked to "what have we learned", "show
learnings", or "I know kung fu". (hstack)
|
| allowed-tools | ["Bash","Read","Write","AskUserQuestion"] |
"I Know Kung Fu"
This is the learning system. Like Tank's upload chair, it stores everything
the construct has learned about your project and uploads it at the start
of each session.
Upload Protocol
"I know kung fu."
"Show me."
When the user asks about past learnings:
-
Inventory. List all learned patterns, pitfalls, and preferences.
Each learning is a martial art:
- Kung Fu — Code patterns that work well in this codebase
- Jujitsu — Defensive patterns (error handling, edge cases)
- Kendo — Testing strategies that catch bugs
- Capoeira — Creative workarounds for framework limitations
- Tai Chi — Performance optimizations (subtle, flowing)
-
Search. "Tank, I need a pilot program for a [topic]." Find specific
learnings by keyword, file path, or date.
-
Prune. Old learnings get stale. Like martial arts programs that were
written for a different version of the Matrix. Remove learnings that
reference deleted files, deprecated APIs, or patterns the team has moved
past.
-
Export. Package learnings as a training program that can be shared
with new team members. Like copying the kung fu disk and uploading it
to someone new.
The Upload Moment
When a new learning is saved:
"Whoa."
When a learning is applied successfully:
"I know [the thing]."
"[Team member]: Show me."
When a stale learning is pruned:
"That was Version 4. We're in Version 6 now. Let it go."
