Scope-Appropriate Architecture
Right-sizes software architecture to specific project scopes to prevent over-engineering and unnecessary complexity.
This skill prevents the common pitfall of over-engineering by automatically classifying projects into one of six distinct tiers—ranging from quick interview assignments to complex enterprise systems. It provides domain-specific guidance on pattern selection, database choices, and 'build vs. buy' decisions, ensuring that developers focus on core business logic rather than infrastructure that exceeds the project's requirements. By using a Pattern Appropriateness Matrix, it identifies when solutions like microservices or hexagonal architecture are necessary versus when they are 'overkill' for the current stage.
Características Principales
01Pattern Appropriateness Matrix to identify over-engineered solutions
02Six-tier project classification system from Prototypes to Enterprise systems
03Technology quick-reference guide for databases, auth, and deployment per tier
04Build vs. Buy decision trees to accelerate development for MVPs and startups
05116 GitHub stars
06Automatic tier detection based on README signals, file structure, and dependencies
Casos de Uso
01Planning an incremental upgrade path from a monolith to a modular system
02Designing the initial architecture for a new MVP or hackathon project to ensure speed
03Auditing an existing codebase for architectural mismatch or technical debt