Prompt Details
Model
(claude-4-6-sonnet)
Token size
2,194
Example input
[TECH_STACK]: C# / .NET 8
[ANALYSIS_SCOPE]: src/
[INPUT_AVAILABLE]: tree
[ENTRY_POINTS]: src/Api/Program.cs, src/Services/OrderService.cs
Example output
**OPERATING MODE: 1 — Tree-First**
User provided `[INPUT_AVAILABLE]: tree`, but no actual tree output is present in the message — only the system prompt document and configuration fields. No file contents, no directory listing, no uploaded files are in context.
**GRANULARITY: Deferred** — cannot be declared until the tree is visible and scope is confirmed.
---
## ⚠ FALLBACK MODE TRIGGERED
I cannot begin analysis because the tree output was not included in your message. The `[INPUT_AVAILABLE]: tree` field indicates you intend to provide one, but nothing was attached or pasted.
**What I can see right now:**
- Tech stack: C# / .NET 8
- Intended scope: `src/`
- Declared entry points: `src/Api/Program.cs`, `src/Services/OrderService.cs`
- No directory listing, no file contents, no uploads
Proceeding without the tree would mean fabricating structure — which this protocol explicitly prohibits.
---
## What I Need From You
Please provide **one of the following**:
### Option A — Tree Output (recommended for Mode 1)
Run this from your repo root and paste the output:
```bash
# Linux / macOS
find src/ -type f -name "*.cs" | sort
# Windows (PowerShell)
Get-ChildItem -Path src -Recurse -Filter "*.cs" | Select-Object FullName
# Or if you have `tree` installed
tree src/ -I "bin|obj" --prune
```
### Option B — Paste Key Files Directly (switches to Mode 3)
Paste the contents of at least:
1. `src/Api/Program.cs`
2. `src/Services/OrderService.cs`
3. 2–3 other files you suspect are heavily coupled
### Option C — Upload Files (switches to Mode 2)
Upload source files directly if you're on Claude Pro.
---
Once I have the tree, I will immediately proceed with **Phase 1**: declare granularity, confirm scope coverage, and identify the **5–10 highest-priority files** to request for full Phase 2–8 analysis.
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-6-SONNET
**Finally understand why changing one file breaks five others.**
Tangled dependencies are the silent killer of developer velocity. This prompt maps your file relationships, identifies problematic coupling patterns, and gives you a concrete plan to untangle the mess.
✅ **Visual dependency mapping** - See how files connect at a glance
✅ **Circular dependency detection** -
✅ **Coupling metrics** -
✅ Decoupling strategies
✅Safe migration paths
...more
Updated 1 week ago
