Menu
Agent memory files with grep-based scoped recall.
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
Use when building, running, testing, or debugging Dora engine games with the Dora CLI, including TypeScript, TSX/DoraX, Lua, YueScript, Teal, XML, Wa, Yarn, Rust WASM, Web IDE service recovery, and in-engine validation.
Use when developing the Dora-SSR engine itself, including C++ engine code, Lua/YueScript dev services, generated bindings, DoraX runtime, Web IDE integration, docs, tests, local validation, and release-facing engine changes.
Dora SSR coding rules for game/workspace projects; prevents browser DOM/Canvas/Node.js code in Dora engine scripts and forces Dora API lookup before using unfamiliar engine APIs.
Use this skill when designing, creating, or polishing UI/screens/HUDs/menus so the result is visually refined, coherent, responsive, and implemented with the correct Dora UI APIs.
Rules and examples for using execute_command with Lua and Git safely inside the Dora Agent runtime.
Guide the agent to create a new project skill with correct placement, required metadata, and a practical SKILL.md template.
| name | memory |
| description | Agent memory files with grep-based scoped recall. |
| always | true |
.agent/main/MEMORY.md — Core memory: user preferences, stable facts, decisions, known issues..agent/main/PROJECT_MEMORY.md — Project facts, build/run notes, files/architecture, project decisions and issues..agent/main/SESSION_SUMMARY.md — Current goal, recent progress, and open issues..agent/main/HISTORY.jsonl — Consolidated action history. Search it when older details are needed..agent/main/SESSION.jsonl — Crash-safe session tail. Do not edit manually.Sub-agents use .agent/subagents/<id>/... for scoped memory.
Write important facts immediately using edit_file:
Put transient task state in SESSION_SUMMARY.md, not MEMORY.md.
Old conversations are automatically summarized into HISTORY.jsonl and the memory markdown files when the session grows large. You usually don't need to manage this.