Backend
InsForge/InsForge
A skill your agent uses when contributing to InsForge's backend package.
Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering.
Install Scope Appropriate Architecture
$ npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yonatangross/orchestkit scope-appropriate-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/scope-appropriate-architecture .claude/skills/scope-appropriate-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scope-appropriate-architecture" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architecture into .claude/skills/scope-appropriate-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-appropriate-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yonatangross/orchestkit scope-appropriate-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/skills/scope-appropriate-architecture .agents/skills/scope-appropriate-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scope-appropriate-architecture" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architecture into .agents/skills/scope-appropriate-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-appropriate-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yonatangross/orchestkit scope-appropriate-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/skills/scope-appropriate-architecture .cursor/skills/scope-appropriate-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scope-appropriate-architecture" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architecture into .cursor/skills/scope-appropriate-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-appropriate-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yonatangross/orchestkit.git --path src/skills/scope-appropriate-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yonatangross/orchestkit scope-appropriate-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/skills/scope-appropriate-architecture .gemini/skills/scope-appropriate-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scope-appropriate-architecture" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architecture into .gemini/skills/scope-appropriate-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-appropriate-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yonatangross/orchestkit scope-appropriate-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/skills/scope-appropriate-architecture .github/skills/scope-appropriate-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scope-appropriate-architecture" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architecture into .github/skills/scope-appropriate-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-appropriate-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yonatangross/orchestkit scope-appropriate-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/skills/scope-appropriate-architecture .opencode/skills/scope-appropriate-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scope-appropriate-architecture" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/scope-appropriate-architecture into .opencode/skills/scope-appropriate-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-appropriate-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
scope-appropriate-architecture- GitHub stars
- 290
- Token cost
- ~1.7k tokens
- SKILL.md length
- 641 words
- Files
- 10 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering.
- Designing architecture
- SKILL.md covers The 6 Project Tiers, Auto-Detection Signals, Pattern Appropriateness Matrix and Technology Quick-Reference by…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Selecting patterns
What it does
Scope Appropriate Architecture is an agent skill from yonatangross/orchestkit. Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/enterprise.md`, `references/interview-takehome.md` and `references/open-source.md`). Compatibility notes: Claude Code 2.1.277+
It sits in Development, covering Code simplification. It works with PostgreSQL. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.
When your agent uses it
- Designing architecture
- Selecting patterns
- Detecting a project tier
Example prompts
- “/scope-appropriate-architecture”
Requirements
- Docker
- Compatibility (from SKILL.md): Claude Code 2.1.277+
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch
What it can do on your machine
Read from SKILL.md and the folder at commit 02bbf9a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWebFetchWebSearch
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Claude Code 2.1.277+
From compatibility in the SKILL.md frontmatter.
Context cost
Scope Appropriate Architecture loads about 1.7k tokens when it runs, and up to ~6.1k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 641 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yonatangross/orchestkit at commit 02bbf9a, republished under its MIT licence (© yonatangross). 641 words, ~1,698 tokens.
Download SKILL.mdSave it as
.claude/skills/scope-appropriate-architecture/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- scope-appropriate-architecture
- description
- Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.
- allowed-tools
- Read, Glob, Grep, WebFetch, WebSearch
- compatibility
- Claude Code 2.1.277+
- license
- MIT
- user-invocable
- false
- context
- inherit
- effort
- low
- model
- haiku
- metadata.category
- architecture
- metadata.version
- 1.0.0
- metadata.author
- OrchestKit
- metadata.complexity
- low
- metadata.tags
- architecture, yagni, over-engineering, scope, patterns
Scope-Appropriate Architecture
Right-size every architectural decision to the project's actual needs. Not every project needs hexagonal architecture, CQRS, or microservices.
Core principle: Detect the project tier first, then constrain all downstream pattern choices to that tier's complexity ceiling.
The 6 Project Tiers
| Tier | LOC Ratio | Architecture | DB | Auth | Tests |
|---|---|---|---|---|---|
| 1. Interview/Take-home | 1.0-1.3x | Flat files, no layers | SQLite / JSON | None or basic | 8-15 focused |
| 2. Hackathon/Prototype | 0.8-1.0x | Single file if possible | SQLite / in-memory | None | Zero |
| 3. Startup/MVP | 1.0-1.5x | MVC monolith | Managed Postgres | Clerk/Supabase Auth | Happy path + critical |
| 4. Growth-stage | 1.5-2.0x | Modular monolith | Postgres + Redis | Auth service | Unit + integration |
| 5. Enterprise | 2.0-3.0x | Hexagonal/DDD | Postgres + queues | OAuth2/SAML | Full pyramid |
| 6. Open Source | 1.2-1.8x | Minimal API surface | Configurable | Optional | Exhaustive public API |
LOC Ratio = total lines / core business logic lines. Higher ratio = more infrastructure code relative to business value.
Auto-Detection Signals
| Signal | Tier Indicator |
|---|---|
| README contains "take-home", "assignment", "interview" | Tier 1 |
| Time limit mentioned (e.g., "4 hours", "weekend") | Tier 1-2 |
| < 10 files, no CI, no Docker | Tier 1-2 |
.github/workflows/ present | Tier 3+ |
package.json with 20+ dependencies | Tier 3+ |
| Kubernetes/Terraform files present | Tier 4-5 |
CONTRIBUTING.md, CODE_OF_CONDUCT.md | Tier 6 |
Monorepo with packages/ or apps/ | Tier 4-5 |
When confidence is low: Ask the user with AskUserQuestion.
Pattern Appropriateness Matrix
| Pattern | Interview | Hackathon | MVP | Growth | Enterprise |
|---|---|---|---|---|---|
| Repository pattern | OVERKILL | OVERKILL | BORDERLINE | APPROPRIATE | REQUIRED |
| Event-driven arch | OVERKILL | OVERKILL | OVERKILL | SELECTIVE | APPROPRIATE |
| DI containers | OVERKILL | OVERKILL | LIGHT ONLY | APPROPRIATE | REQUIRED |
| Separate DTO layers | OVERKILL | OVERKILL | 1 EXTRA | 2 LAYERS | ALL LAYERS |
| Microservices | NEVER | NEVER | NEVER | EXTRACT ONLY | APPROPRIATE |
| CQRS | OVERKILL | OVERKILL | OVERKILL | OVERKILL | WHEN JUSTIFIED |
| Hexagonal architecture | OVERKILL | OVERKILL | OVERKILL | BORDERLINE | APPROPRIATE |
| DDD (bounded contexts) | OVERKILL | OVERKILL | OVERKILL | SELECTIVE | APPROPRIATE |
| Message queues | OVERKILL | OVERKILL | BORDERLINE | APPROPRIATE | REQUIRED |
| API versioning | SKIP | SKIP | URL prefix | Header-based | Full strategy |
| Error handling | try/catch | console.log | Error boundary | Error service | RFC 9457 |
| Logging | console.log | none | Structured JSON | Centralized | OpenTelemetry |
Rule of thumb: If a pattern shows OVERKILL for the detected tier, do NOT use it. Suggest the simpler alternative instead.
Technology Quick-Reference by Tier
| Choice | Interview | Hackathon | MVP | Growth | Enterprise |
|---|---|---|---|---|---|
| Database | SQLite / JSON file | In-memory / SQLite | Managed Postgres | Postgres + Redis | Postgres + queues + cache |
| Auth | Hardcoded / none | None | Clerk / Supabase Auth | Auth service | OAuth2 / SAML / SSO |
| State mgmt | useState | useState | Zustand / Context | Zustand + React Query | Redux / custom + cache |
| CSS | Inline / Tailwind | Tailwind | Tailwind | Tailwind + design tokens | Design system |
| API | Express routes | Single file handler | Next.js API routes | FastAPI / Express | Gateway + services |
| Deployment | localhost | Vercel / Railway | Vercel / Railway | Docker + managed | K8s / ECS |
| CI/CD | None | None | GitHub Actions basic | Multi-stage pipeline | Full pipeline + gates |
| Monitoring | None | None | Error tracking only | APM + logs | Full observability stack |
Show full SKILL.md (215 more words)Show less
Build vs Buy Decision Tree (Tiers 1-3)
For Interview, Hackathon, and MVP tiers, always prefer buying over building:
| Capability | BUY (use SaaS) | BUILD (only if) |
|---|---|---|
| Auth | Clerk, Supabase Auth, Auth0 | Core product IS auth |
| Payments | Stripe | Core product IS payments |
| Resend, SendGrid | Core product IS email | |
| File storage | S3, Cloudflare R2 | Compliance requires on-prem |
| Search | Algolia, Typesense Cloud | > 10M docs or custom ranking |
| Analytics | PostHog, Mixpanel | Unique data requirements |
Time savings: Auth alone is 2-4 weeks build vs 2 hours integrate.
Upgrade Path
When a project grows beyond its current tier, upgrade incrementally:
Tier 2 (Prototype) → Tier 3 (MVP)
Add: Postgres, basic auth, error boundaries, CI
Tier 3 (MVP) → Tier 4 (Growth)
Add: Redis cache, background jobs, monitoring, module boundaries
Tier 4 (Growth) → Tier 5 (Enterprise)
Add: DI, bounded contexts, message queues, full observability
Extract: First microservice (only the proven bottleneck)Key insight: You can always add complexity later. You cannot easily remove it.
When This Skill Activates
This skill is loaded by:
brainstormPhase 0 (context discovery)implementStep 0 (context discovery)quality-gatesYAGNI check- Any skill that needs to right-size a recommendation
The detected tier is passed as context to constrain downstream decisions.
Related Skills
ork:brainstorm- Uses tier detection in Phase 0 to constrain ideasork:implement- Uses tier detection in Step 0 to constrain architectureork:quality-gates- YAGNI gate references this skill's tier matrixork:architecture-patterns- Architecture validation (constrained by tier)
References
Load on demand with Read("references/<file>"):
| File | Content |
|---|---|
interview-takehome.md | Tiers 1-2 in detail |
startup-mvp.md | Tier 3 patterns and decisions |
enterprise.md | Tiers 4-5 patterns and justification criteria |
open-source.md | Tier 6 unique considerations |
© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (references) in src/skills/scope-appropriate-architecture of yonatangross/orchestkit.
- SKILL.md
- references/enterprise.md
- references/interview-takehome.md
- references/open-source.md
- references/startup-mvp.md
- rules/_sections.md
- rules/deferred-debt-marker.md
- rules/over-engineering-flag.md
- rules/tier-detection-evidence.md
- test-cases.json
Open the folder on GitHubat commit 02bbf9a
Compare with similar skills
Scope Appropriate Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scope Appropriate Architecture this skillyonatangross/orchestkit | 290 | — | ~1.7k | Automated safety check: Pass | MIT | |
| BackendInsForge/InsForge | 13k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Windmill Rust Backend Patternswindmill-labs/windmill | 18k | — | ~869 | Automated safety check: Pass | Custom licence | |
| Dhhmarckohlbrugge/37signals-skills | 724 | — | ~2.2k | Automated safety check: Pass | None | |
| Claimable Postgreshenryalouf/ruflow | 157 | — | ~2.4k | Automated safety check: Notes | MIT | |
| Architecturemanagedcode/dotnet-skills | 486 | — | ~659 | Automated safety check: Pass | MIT |
Similar skills
Windmill Rust Backend Patterns
windmill-labs/windmill
Sets Rust conventions for the Windmill backend: error types, SQLx queries, JSON handling, async rules, module layout and rust-analyzer navigation.
Dhh
marckohlbrugge/37signals-skills
Review Ruby/Rails code like DHH would - direct, opinionated, allergic to over-engineering.
Claimable Postgres
henryalouf/ruflow
Provision instant temporary Postgres databases via Claimable Postgres by Neon (pg.new).
Architecture
managedcode/dotnet-skills
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
Ponytail
DavidObando/gsharp
Forces the laziest solution that actually works, simplest, shortest, most minimal.
More from yonatangross/orchestkit
All 108 skills in this repoAPI Design
yonatangross/orchestkit
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.
Architecture Decision Record
yonatangross/orchestkit
ADR templates in the Nygard format with context, decision, consequences, and alternatives.
Audit Full
yonatangross/orchestkit
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.
Code Review Playbook
yonatangross/orchestkit
Structured review processes, conventional comments, language-specific checklists, and feedback templates.
Create PR
yonatangross/orchestkit
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.
Explore
yonatangross/orchestkit
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.
Related
Works with
Categories
Questions about Scope Appropriate Architecture
What does Scope Appropriate Architecture do?
Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Scope Appropriate Architecture is an agent skill from yonatangross/orchestkit. Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering.
When should I use Scope Appropriate Architecture?
Scope Appropriate Architecture fits situations like: designing architecture; selecting patterns; detecting a project tier.
How do I install Scope Appropriate Architecture in Claude Code?
Run `npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a claude-code`. Or copy the skill folder (src/skills/scope-appropriate-architecture in yonatangross/orchestkit) into .claude/skills/scope-appropriate-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Scope Appropriate Architecture in Codex?
Run `npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a codex`. Or copy the skill folder (src/skills/scope-appropriate-architecture in yonatangross/orchestkit) into .agents/skills/scope-appropriate-architecture in your project. Codex loads it when a task matches its description.
Can I use Scope Appropriate Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yonatangross/orchestkit --skill scope-appropriate-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scope-appropriate-architecture, .gemini/skills/scope-appropriate-architecture, .github/skills/scope-appropriate-architecture and .opencode/skills/scope-appropriate-architecture in your project.
What does Scope Appropriate Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Scope Appropriate Architecture is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+.
Does Scope Appropriate Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Scope Appropriate Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Scope Appropriate Architecture use?
Scope Appropriate Architecture is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scope Appropriate Architecture use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.
What are the alternatives to Scope Appropriate Architecture?
Skills that share tags, products or a category with Scope Appropriate Architecture: Backend (InsForge/InsForge, 13k stars), Windmill Rust Backend Patterns (windmill-labs/windmill, 18k stars), Dhh (marckohlbrugge/37signals-skills, 724 stars) and Claimable Postgres (henryalouf/ruflow, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scope Appropriate Architecture?
yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 290 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.
Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.