This is the architectural guardrail you need when you're about to add hexagonal architecture to a weekend hackathon project. It classifies projects into six tiers (interview, hackathon, MVP, growth, enterprise, open source) by scanning for signals like README mentions of "take-home", presence of CI configs, or Kubernetes files, then constrains pattern choices to match. The pattern matrix is blunt: repository pattern shows "OVERKILL" for tier 1-2, microservices show "NEVER" for tier 1-3. It's invoked automatically by brainstorm and implement skills during context discovery to right-size decisions before you waste time building OAuth2 for a coding assignment. The LOC ratio column (infrastructure code divided by business logic) is a nice reality check on whether your 200-line feature really needs 600 lines of abstraction.
npx skills add https://github.com/yonatangross/orchestkit --skill scope-appropriate-architecture