How does it handle project growth over time?

The skill includes an 'Upgrade Path' framework that suggests specific technical additions (like Redis or DI containers) only when moving from one tier to the next.

Will this skill prevent me from using advanced architectures?

It serves as a guardrail to prevent 'overkill' patterns, suggesting simpler alternatives for lower tiers while requiring justification for high-complexity patterns like CQRS or Microservices.

How does the skill detect which tier my project belongs to?

It analyzes signals like README keywords, file structure (e.g., presence of K8s or Docker), dependency counts in package.json, and the presence of contributing guidelines.

What are the 6 project tiers included in this skill?

The tiers include Interview/Take-home, Hackathon/Prototype, Startup/MVP, Growth-stage, Enterprise, and Open Source, each with specific architectural constraints.

Scope-Appropriate Architecture

Name: Scope-Appropriate Architecture
Author: yonatangross

byyonatangross

•

116

•

생산성 및 워크플로

Right-sizes architectural patterns to project scale to prevent over-engineering and maximize development velocity.

This skill provides an intelligent framework for selecting the right architectural complexity for any software project by classifying development efforts into six distinct tiers. From quick interview take-homes to massive enterprise systems, it constrains technology choices and design patterns—such as CQRS, Microservices, or DDD—to what is actually necessary for the current project scope. By using auto-detection signals from the codebase, it helps developers adhere to YAGNI (You Ain't Gonna Need It) principles while providing a clear roadmap for incremental architectural upgrades as a project grows.

주요 기능

016-Tier Project Classification from Interview to Enterprise scale

02Build vs. Buy decision trees for high-velocity MVP development

03Technology Quick-Reference for DB, Auth, and CI/CD per tier

04Automated Tier Detection using README, CI, and dependency signals

05116 GitHub stars

06Pattern Appropriateness Matrix for identifying overkill architectures

사용 사례

01Ensuring a take-home assignment is focused on logic rather than boilerplate

02Validating if a project needs complex patterns like Hexagonal Architecture

03Determining the right infrastructure for a new startup MVP

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add yonatangross/orchestkit scope-appropriate-architecture

For use in Claude.ai and ChatGPT

Download Skill