Menu
minmaxing 5-tier memory system management
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | memory |
| description | minmaxing 5-tier memory system management |
Manage the 5-tier memory system and taste system.
Use when: User says "show memory", "check memory", "memory stats", "log decision", "how's memory".
Commands:
bash scripts/memory.sh stats — Show memory counts per tierbash scripts/memory.sh list — List recent memoriesbash scripts/memory.sh add episodic "what happened" — Log episodicbash scripts/taste.sh review — Show taste.memory recent entriesbash scripts/taste.sh log APPROVE "task" "reasoning" — Log a verdictThe 5 tiers:
| Tier | Storage | Retention |
|---|---|---|
| Episodic | .taste/sessions/*.jsonl | 90 days |
| Semantic | taste.md + Decisions/ | Indefinite |
| Procedural | Patterns/ | Indefinite |
| Error-Solution | Errors/ | Indefinite |
| Graph | Stories/ | Indefinite |
Create a taste-to-artifact visualization package for a project, task, draft SPEC, UI, backend, agent runtime, dashboard, game, or product idea without implementing it. Use when the user asks to visualize taste.md, taste.vision, what the model thinks is being built, a product experience, UI mockup, architecture schematic, operator journey, or comprehension check before execution.
Run an approval-first variant of the minmaxing workflow: research, audit, plan, estimate, draft SPEC, visualize the intended product or operator experience, then stop with WAITING_FOR_VISUAL_APPROVAL before implementation. Use when the user wants to see and approve the model's understanding before code changes, or wants to continue or revise a saved visualization workflow.
Use this as the definitive workflow command for mutating work: default Opus 4.7 high planning and review with MiniMax-M2.7-highspeed Token Plan execution, plus explicit governed model profiles such as sonnetminimax for Sonnet 4.6 judgment with MiniMax execution. It must drive to a verified result, partial result, or blocked repair path; /opusminimax is the advanced engine underneath, not a competing daily command.
Run the power-user Sonnet 4.6 judgment plus MiniMax-M2.7-highspeed Token Plan executor route. Use when the operator wants to preserve Opus quota or has exhausted Opus, while keeping the same governed /opusworkflow lifecycle and MiniMax bounded execution.
Advanced engine behind /opusworkflow for provider split, packet, repair, and benchmark work, including the explicit sonnetminimax profile for Sonnet 4.6 judgment plus MiniMax-M2.7-highspeed execution. Normal build/fix/refactor work should use /opusworkflow.
Run the optional all-Opus sibling of /opusworkflow. Use when the operator explicitly wants Opus 4.7 as planner, executor, reviewer, and final judge with default high effort and optional max effort.