Project Memory - Code Quest 專案記憶

To maintain architecture decisions across sessions, use a project memory skill to store TDD rules, RPG conceptual mappings, and technology rationale so the AI retrieves prior conventions automatically.

Isolating parallel AI battles with Git worktree requires documenting the setup in project memory to ensure the AI consistently applies the isolation strategy and cleanup rules across future conversations.

Fixing node-pty PTY permission errors involves loading stored troubleshooting steps from project memory, which provides specific fixes for permission issues and WebSocket reconnection loops.

Preserving project context prevents over-design by keeping user preferences and development rules in a stable instruction set, ensuring the AI adheres to your no over-design guidelines during future tasks.

You can map project concepts like user, Claude AI, skills, and tokens to RPG gameplay elements by encoding these mappings in project memory for consistent future prompt generation.

Your AI loses technical preferences like commit style because it lacks a persistent memory, so loading a project memory skill ensures prior decisions and preferences are readily available.