Workflow lets Claude remember your entire Unity project structure automatically
A developer shared a two-part system called Hades & Asphodel that maps out how Unity code files connect to each other and keeps that map available to Claude across every new conversation. Instead of re-explaining the project every session, Claude can immediately answer questions about how the code fits together. Solo game developers who lean on AI coding assistants will find this saves significant time.
When a Unity game project grows large, it can contain hundreds of scripts that reference each other in complicated ways. Claude normally has no way to know this structure unless you paste it in each time — which is tedious and eats into your context window. The Hades component automatically builds a dependency graph: a diagram showing which files rely on which other files. The Asphodel component stores that graph as persistent memory, so Claude can load it at the start of any new chat without the developer having to paste anything manually. With this in place, Claude can accurately answer questions like "what breaks if I change this script?" or "where is this function actually used?" — the kinds of questions that normally require the developer to mentally trace through the whole codebase. The approach is shared openly and can be adapted for any project where files are heavily interconnected, not just Unity games.
Key points
- Hades automatically generates a map of how all project files connect to each other
- Asphodel stores that map so Claude remembers the project structure in every new chat session
- Eliminates the need to re-explain your project to Claude at the start of each conversation
- Helps Claude give accurate answers about which files are affected by a code change
- The workflow is open-source and adaptable to non-Unity projects with complex file structures
Quick term guide
- developers
- Developers are people who build software, apps, or websites.
- reference
- Using a source to find information or confirm facts while working.
- context window
- The amount of text an AI tool can remember and use in one chat.
- dependency graph
- A diagram that shows which code files rely on which other files, like a family tree for your code.
- dependency
- An external library or package that your program needs in order to run.
- persistent memory
- A way to save information so an AI can recall it even after a conversation ends and a new one begins.
- workflow
- A repeatable set of steps for getting a task done.
- open-source
- Software whose code is shared publicly so others can inspect, use, or change it.