deps

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).

Analyze the .asmdef dependency relationships of all modules in the project, outputting a Mermaid diagram + dependency matrix + issue detection.

Arguments: $ARGUMENTS

• Optional: specific module names to focus on
• No arguments: analyze all .asmdef files in the project

Execution Steps

1. Collect All .asmdef Files

Use Glob to find Assets/**/*.asmdef, excluding Tests and Editor asmdefs (filenames containing .Tests., .Editor., or .PlayModeTests.).

2. Build GUID → Name Mapping

For each .asmdef file:

• Read the .asmdef to get the name field
• Read the corresponding .asmdef.meta to get the guid field
• Build a GUID → Name lookup table

3. Parse Dependency Relationships

For each .asmdef:

• Read the GUIDs in the references array
• Convert to human-readable names via the lookup table
• Record: ModuleA → [depends on ModuleB, depends on ModuleC]

4. Output Mermaid Dependency Graph

Generate a Mermaid flowchart, arranged by layer from top to bottom:

```mermaid
graph TD
    subgraph "Layer 0"
        Core
    end
    subgraph "Layer 1"
        Player
        AI
    end
    subgraph "Layer 2"
        UI
        Networking
    end

    Player --> Core
    AI --> Core
    UI --> Player
    Networking --> Core
```

• Normal dependencies: solid arrow -->
• Circular dependencies: red dashed -.->|cycle|
• Layer violations: orange bold ==>|violation|

5. Output Dependency Matrix

Use a table to show module-to-module dependencies at a glance:

| Module ↓ Depends on → | Core | Player | AI | UI | ... |
|------------------------|:----:|:------:|:--:|:--:|:---:|
| Core                   |  -   |        |    |    |     |
| Player                 |  ✓   |   -    |    |    |     |
| AI                     |  ✓   |        | -  |    |     |
| UI                     |      |   ✓    |    | -  |     |