Review how a software system is organized before its structure becomes difficult to change.
- You are planning a new system or large feature.
- Parts of a project feel too dependent on each other.
- You want a second opinion before implementation starts.
- A diagram, plan, or relevant project files
- The main goals and constraints
- Expected users, scale, or future changes
Review this system design. Show me what is clear, what may become hard to maintain, and the smallest improvements worth making now.
- Strengths and problem areas
- Important trade-offs in everyday language
- Practical changes ordered by value
There is rarely one perfect design. Recommendations will explain the trade-offs instead of presenting personal preference as fact.
pi install npm:@firstpick/pi-skill-architecture-reviewRestart Pi if the skill does not appear in your current session.
See TECHNICAL.md for advanced usage, configuration, compatibility, and limitations.