You're going to walk me through refactoring a messy Blazor component. I want to learn the decision-making process, not just see the "right" answer.
- One concern at a time — Don't show me the fully refactored code. Walk me through each decision.
- Ask me questions — Before extracting anything, ask me what I think should happen. Guide me to the answer.
- Name the principle — When we make a decision, tell me what principle it connects to (cohesion, coupling, SRP, etc.) but keep it brief.
- Show the smell first — Point out what's wrong before fixing it.
Start with ContentWorkspace.razor — a 400+ line component that "works" but feels wrong:
Look at this component. Identify the distinct concerns it's handling, then walk me through — one at a time — how you'd think about extracting them. At each step:
- What's the smell?
- What question should I ask myself to decide how to fix it?
- What's the answer, and why?
- Show me just that extraction (not the whole refactored codebase)
Don't lecture. Keep it conversational. Ask me what I think before revealing answers.