Agent skill

Architecture Patterns

by yonatangross in yonatangross/orchestkit

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing.

MITAuto-check passedDevelopment

Install Architecture Patterns

skills CLI
$ npx skills add yonatangross/orchestkit --skill architecture-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yonatangross/orchestkit architecture-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/architecture-patterns .claude/skills/architecture-patterns && rm -rf skills-src

Use ~/.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/

Facts

Skill name
architecture-patterns
GitHub stars
289
Token cost
~3.4k tokens
SKILL.md length
982 words
Files
25 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing.

  • Works in 4 steps: Read project tier from… → If no tier set, auto-detect using… → Apply tier-based enforcement matrix —… → …
  • Designing system boundaries
  • SKILL.md covers Quick Reference, Quick Start, Clean Architecture and Project Structure, plus 7 more sections
  • Enforcing layered architecture

What it does

Architecture Patterns is an agent skill from yonatangross/orchestkit. Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 27 other files, including scripts and reference files (for example `checklists/solid-checklist.md`, `metadata.json` and `references/naming-conventions.md`). Compatibility notes: Claude Code 2.1.277+.

It sits in Development, covering Design patterns and Software architecture. 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 system boundaries
  • Enforcing layered architecture
  • Validating project structure
  • Defining test standards

Example prompts

  • “/architecture-patterns”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Claude Code 2.1.277+.
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read project tier from scope-appropriate-architecture context (set during brainstorm/implement Step 0)
  2. If no tier set, auto-detect using signals in Read("rules/right-sizing-tiers.md")
  3. Apply tier-based enforcement matrix — skip rules marked OFF for detected tier
  4. Security rules are tier-independent — always enforce SQL parameterization, input validation, auth checks

What it can do on your machine

Read from SKILL.md and the folder at commit 0ef71d2. 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:

    • Read
    • Glob
    • Grep
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • cosmicpython.com
    • fastapi.tiangolo.com
    • alistair.cockburn.us
    • typing.python.org
    • github.com
    • nextjs.org
    • docs.pytest.org
    • vitest.dev

    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

Architecture Patterns loads about 3.4k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 982 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 0ef71d2, republished under its MIT licence (© yonatangross). 982 words, ~3,389 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-patterns/SKILL.md (or your agent's skills folder). This skill also uses 24 other files; get the full folder from GitHub.
name
architecture-patterns
description
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.
allowed-tools
Read, Glob, Grep, WebFetch, WebSearch
compatibility
Claude Code 2.1.277+.
license
MIT
skills
scope-appropriate-architecture
user-invocable
false
disable-model-invocation
false
effort
high
metadata.owner-agent
backend-system-architect
metadata.category
document-asset-creation
metadata.version
2.1.0
metadata.author
OrchestKit
metadata.complexity
high
<!-- directive-density: intentional (teaches anti-patterns; NEVER markers describe real layering violations, not aspirational guidance) -->

Architecture Patterns

Consolidated architecture validation and enforcement patterns covering clean architecture, backend layer separation, project structure conventions, and test standards. Each category has individual rule files in rules/ loaded on-demand. House scars and dated decisions rescued from retired reference tutorials live in references/ork-delta.md; the tutorials themselves are upstream's job (see "Upstream coverage" below).

Quick Reference

CategoryRulesImpactWhen to Use
Clean Architecture3HIGHSOLID principles, hexagonal architecture, ports & adapters, DDD
Project Structure2HIGHFolder conventions, nesting depth, import direction, barrel files
Backend Layers3HIGHRouter/service/repository separation, DI, file naming
Test Standards3MEDIUMAAA pattern, naming conventions, coverage thresholds
Right-Sizing2HIGHArchitecture tier selection, over-engineering prevention, context-aware enforcement

Total: 13 rules across 5 categories

Quick Start

python
# Clean Architecture: Dependency Inversion via Protocol
class IUserRepository(Protocol):
    async def get_by_id(self, id: str) -> User | None: ...

class UserService:
    def __init__(self, repo: IUserRepository):
        self._repo = repo  # Depends on abstraction, not concretion

# FastAPI DI chain: DB -> Repository -> Service
def get_user_service(db: AsyncSession = Depends(get_db)) -> UserService:
    return UserService(PostgresUserRepository(db))
# Project Structure: Unidirectional Import Architecture
shared/lib  ->  components  ->  features  ->  app
(lowest)                                    (highest)

# Backend Layers: Strict Separation
Routers (HTTP) -> Services (Business Logic) -> Repositories (Data Access)

Clean Architecture

SOLID principles, hexagonal architecture, ports and adapters, and DDD tactical patterns for maintainable backends.

RuleFileKey Pattern
Hexagonal Architecturerules/clean-hexagonal.mdDriving/driven ports, adapter implementations, layer structure
SOLID & Dependency Rulerules/clean-dependency-rule.mdProtocol-based interfaces, dependency inversion, FastAPI DI
DDD Tactical Patternsrules/clean-ports-adapters.mdEntities, value objects, aggregate roots, domain events

Design review checklist: checklists/solid-checklist.md. Domain entity scaffold: scripts/domain-entity-template.py.

Key Decisions
DecisionRecommendation
Protocol vs ABCProtocol (structural typing)
Dataclass vs PydanticDataclass for domain, Pydantic for API
Repository granularityOne per aggregate root
Transaction boundaryService layer, not repository
Event publishingCollect in aggregate, publish after commit

Project Structure

Feature-based organization, max nesting depth, unidirectional imports, and barrel file prevention.

RuleFileKey Pattern
Folder Structure & Nestingrules/structure-folders.mdReact/Next.js and FastAPI layouts, 4-level max nesting, barrel file rules
Import Direction & Locationreferences/structure-import-direction.mdUnidirectional imports, cross-feature prevention, component/hook placement
Blocking Rules
RuleCheck
Max NestingMax 4 levels from src/ or app/
No Barrel FilesNo index.ts re-exports (tree-shaking issues)
Component LocationReact components in components/ or features/ only
Hook LocationCustom hooks in hooks/ or features/*/hooks/ only
Import DirectionUnidirectional: shared -> components -> features -> app

Backend Layers

FastAPI Clean Architecture with router/service/repository layer separation and blocking validation.

RuleFileKey Pattern
Layer Separationrules/backend-layers.mdRouter/service/repository boundaries, forbidden patterns, async rules
Dependency Injectionrules/backend-di.mdDepends() chains, blocked DI patterns, violation detection
File Naming & Exceptionsrules/backend-repository.mdNaming conventions, async rules, domain exceptions

House scars for this category (exception-to-HTTP status map, import-level violation greps, DI override teardown): references/ork-delta.md.

Layer Boundaries
LayerResponsibilityForbidden
RoutersHTTP concerns, request parsing, auth checksDatabase operations, business logic
ServicesBusiness logic, validation, orchestrationHTTPException, Request objects
RepositoriesData access, queries, persistenceHTTP concerns, business logic

Test Standards

Testing best practices with AAA pattern, naming conventions, isolation, and coverage thresholds.

RuleFileKey Pattern
AAA Pattern & Isolationrules/testing-aaa.mdArrange-Act-Assert, test isolation, parameterized tests
Naming Conventionsreferences/testing-naming-conventions.mdDescriptive behavior-focused names for Python and TypeScript
Coverage & Locationrules/testing-coverage.mdCoverage thresholds, fixture scopes, and (per references/ork-delta.md) the no-co-location rule
Coverage Requirements
AreaMinimumTarget
Overall80%90%
Business Logic90%100%
Critical Paths95%100%
New Code100%100%

Right-Sizing

Context-aware backend architecture enforcement. Rules adjust strictness based on project tier detected by scope-appropriate-architecture.

Enforcement procedure:

  1. Read project tier from scope-appropriate-architecture context (set during brainstorm/implement Step 0)
  2. If no tier set, auto-detect using signals in Read("rules/right-sizing-tiers.md")
  3. Apply tier-based enforcement matrix — skip rules marked OFF for detected tier
  4. Security rules are tier-independent — always enforce SQL parameterization, input validation, auth checks
RuleFileKey Pattern
Architecture Sizing Tiersrules/right-sizing-tiers.mdInterview/MVP/production/enterprise sizing matrix, LOC estimates, detection signals
Right-Sizing Decision Guiderules/right-sizing-decision.mdORM, auth, error handling, testing recommendations per tier, over-engineering tax
Show full SKILL.md (421 more words)Show less
Tier-Based Rule Enforcement
RuleInterviewMVPProductionEnterprise
Layer separationOFFWARNBLOCKBLOCK
Repository patternOFFOFFWARNBLOCK
Domain exceptionsOFFOFFBLOCKBLOCK
Dependency injectionOFFWARNBLOCKBLOCK
OpenAPI documentationOFFOFFWARNBLOCK

Manual override: User can set tier explicitly to bypass auto-detection (e.g., "I want enterprise patterns for this take-home to demonstrate skill").

Decision Flowchart
Is this a take-home or hackathon?
  YES --> Flat architecture. Single file or 3-5 files. Done.
  NO  -->

Is this a prototype or MVP with < 3 months runway?
  YES --> Simple layered. Routes + services + models. No abstractions.
  NO  -->

Do you have > 5 engineers or complex domain rules?
  YES --> Clean architecture with ports/adapters.
  NO  --> Layered architecture. Add abstractions only when pain appears.

When NOT to Use

Not every project needs architecture patterns. Match complexity to project tier:

PatternInterviewHackathonMVPGrowthEnterpriseSimpler Alternative
Repository patternOVERKILL (~200 LOC)OVERKILLBORDERLINEAPPROPRIATEREQUIREDDirect ORM calls in service (~20 LOC)
DI containersOVERKILL (~150 LOC)OVERKILLLIGHT ONLYAPPROPRIATEREQUIREDConstructor params or module-level singletons (~10 LOC)
Event-driven archOVERKILL (~300 LOC)OVERKILLOVERKILLSELECTIVEAPPROPRIATEDirect function calls between services (~30 LOC)
Hexagonal architectureOVERKILL (~400 LOC)OVERKILLOVERKILLBORDERLINEAPPROPRIATEFlat modules with imports (~50 LOC)
Strict layer separationOVERKILL (~250 LOC)OVERKILLWARNBLOCKBLOCKRoutes + models in same file (~40 LOC)
Domain exceptionsOVERKILL (~100 LOC)OVERKILLOVERKILLBLOCKBLOCKBuilt-in ValueError/HTTPException (~5 LOC)

Rule of thumb: If a pattern shows OVERKILL for the detected tier, do NOT use it. Use the simpler alternative. A take-home with hexagonal architecture signals over-engineering, not skill.

Anti-Patterns (FORBIDDEN)

python
# CLEAN ARCHITECTURE
# NEVER import infrastructure in domain layer
from app.infrastructure.database import engine  # In domain layer!

# NEVER leak ORM models to API layer
@router.get("/users/{id}")
async def get_user(id: str, db: Session) -> UserModel:  # Returns ORM model!

# NEVER have domain depend on framework
from fastapi import HTTPException
class UserService:
    def get(self, id: str):
        raise HTTPException(404)  # Framework in domain!

# PROJECT STRUCTURE
# NEVER create files deeper than 4 levels from src/
# NEVER create barrel files (index.ts re-exports)
# NEVER import from higher layers (features importing from app)
# NEVER import across features (use shared/ for common code)

# BACKEND LAYERS
# NEVER use database operations in routers
# NEVER raise HTTPException in services
# NEVER instantiate services without Depends()

# TEST STANDARDS
# NEVER mix test files with source code
# NEVER use non-descriptive test names (test1, test, works)
# NEVER share mutable state between tests without reset

Upstream coverage (do not restate)

Long-form tutorials on these topics were removed from this skill (2026-07-31 wrap-plus-delta campaign). Read them at the first-party source; only floors, scars, and house decisions belong here (see references/ork-delta.md).

TopicFirst-party source
Hexagonal architecture, ports and adapters walkthroughAlistair Cockburn, https://alistair.cockburn.us/hexagonal-architecture/ and Architecture Patterns with Python, https://www.cosmicpython.com/
SOLID principles tutorial (Protocol-based)Architecture Patterns with Python, https://www.cosmicpython.com/ and Python Protocol spec, https://typing.python.org/en/latest/spec/protocol.html
DDD tactical patterns (entities, value objects, aggregates, domain events)Architecture Patterns with Python, https://www.cosmicpython.com/
FastAPI dependency injection, auth dependencies, DI test overridesFastAPI docs (context7: /tiangolo/fastapi), https://fastapi.tiangolo.com/tutorial/dependencies/ and skill ork:python-backend
Router/service/repository layer walkthroughFastAPI bigger applications, https://fastapi.tiangolo.com/tutorial/bigger-applications/ and skill ork:python-backend
Full FastAPI clean-architecture example appFastAPI full-stack template, https://github.com/fastapi/full-stack-fastapi-template
Next.js folder layout and structure-violation catalogNext.js project structure docs, https://nextjs.org/docs/app/getting-started/project-structure (skill vercel:nextjs)
AAA pattern, isolation, parameterized tests, fixture scoping, coverage configSkill ork:testing-unit; pytest docs, https://docs.pytest.org/en/stable/ and Vitest coverage, https://vitest.dev/config/#coverage
  • ork:scope-appropriate-architecture - Project tier detection that drives right-sizing enforcement
  • ork:quality-gates - YAGNI gate uses tier context to validate complexity
  • ork:distributed-systems - Distributed locking, resilience, idempotency patterns
  • ork:api-design - REST API design, versioning, error handling
  • ork:testing-unit - Unit testing: AAA pattern, fixtures, mocking, factories
  • ork:testing-e2e - E2E testing: Playwright, page objects, visual regression
  • ork:testing-integration - Integration testing: API endpoints, database, contracts
  • ork:python-backend - FastAPI, SQLAlchemy, asyncio patterns
  • ork:database-patterns - Schema design, query optimization, migrations

© 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 24 other files (scripts, references) in src/skills/architecture-patterns of yonatangross/orchestkit.

  • SKILL.md
  • checklists/solid-checklist.md
  • metadata.json
  • references/naming-conventions.md
  • references/ork-delta.md
  • references/structure-import-direction.md
  • references/testing-naming-conventions.md
  • rules/_sections.md
  • rules/_template.md
  • rules/backend-di.md
  • rules/backend-layers.md
  • rules/backend-repository.md
  • rules/clean-dependency-rule.md
  • rules/clean-hexagonal.md
  • rules/clean-ports-adapters.md
  • rules/right-sizing-decision.md
  • rules/right-sizing-tiers.md
  • rules/structure-conventions.md
  • … and 7 more

Open the folder on GitHubat commit 0ef71d2

Compare with similar skills

Architecture Patterns 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.

Architecture Patterns compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Patterns this skillyonatangross/orchestkit289—~3.4kAutomated safety check: PassMIT
Architecture PatternsKartikLabhshetwar/better-shot2.4k2 repos~1.4kAutomated safety check: PassCustom licence
Java Architecture Reviewdecebals/claude-code-java7511 repos~2.2kAutomated safety check: PassMIT
Brooks Audithyhmrright/brooks-lint1.5k1 repos~537Automated safety check: PassMIT
Adopt a Design PatternTotoro-jam/battle-tested-patterns344—~4.9kAutomated safety check: PassMIT
Akka.Hosting Actor PatternsAaronontheweb/dotnet-skills1.2k1 repos~5kAutomated safety check: PassMIT

Similar skills

  • Architecture Patterns

    KartikLabhshetwar/better-shot

    Deep dive into software architecture for macOS. An agent skill from KartikLabhshetwar/better-shot.

    2.4k GitHub starsUsed in 2 repos~1.4k tokens
    DevelopmentAuto-check passed
  • Java Architecture Review

    decebals/claude-code-java

    Reviews a Java project's architecture at the macro level: package structure, module boundaries, dependency direction and layering.

    751 GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed
  • Brooks Audit

    hyhmrright/brooks-lint

    Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.

    1.5k GitHub starsUsed in 1 repo~537 tokens
    DevelopmentAuto-check passed
  • Adopt a Design Pattern

    Totoro-jam/battle-tested-patterns

    Matches a coding problem to one of 46 documented systems patterns, checks that it really fits, then adapts it into your codebase with a test for its invariant.

    344 GitHub stars~4.9k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Akka.Hosting Actor Patterns

    Aaronontheweb/dotnet-skills

    Shows how to build entity actors with Akka.Hosting so the same code runs in local unit tests and in a sharded cluster in production.

    1.2k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check passed
  • Pattern Conformance Audit

    Totoro-jam/battle-tested-patterns

    Audits a codebase's existing patterns, such as rate limiters, circuit breakers and caches, against canonical invariants and flags mislabeled or divergent ones.

    344 GitHub stars~1.6k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from yonatangross/orchestkit

All 108 skills in this repo
  • API 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.

    289 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    289 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    289 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    289 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    289 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    289 GitHub stars~3.9k tokensUpdated today
    Auto-check: notes

Categories

Questions about Architecture Patterns

What does Architecture Patterns do?

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Architecture Patterns is an agent skill from yonatangross/orchestkit. Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing.

When should I use Architecture Patterns?

Architecture Patterns fits situations like: designing system boundaries; enforcing layered architecture; validating project structure; defining test standards.

How do I install Architecture Patterns in Claude Code?

Run `npx skills add yonatangross/orchestkit --skill architecture-patterns -a claude-code`. Or copy the skill folder (src/skills/architecture-patterns in yonatangross/orchestkit) into .claude/skills/architecture-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Patterns in Codex?

Run `npx skills add yonatangross/orchestkit --skill architecture-patterns -a codex`. Or copy the skill folder (src/skills/architecture-patterns in yonatangross/orchestkit) into .agents/skills/architecture-patterns in your project. Codex loads it when a task matches its description.

Can I use Architecture Patterns 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 architecture-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-patterns, .gemini/skills/architecture-patterns, .github/skills/architecture-patterns and .opencode/skills/architecture-patterns in your project.

What does Architecture Patterns need to run?

SKILL.md names no scripts, command-line tools or credentials: Architecture Patterns is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+..

Does Architecture Patterns access the network?

SKILL.md names 8 domains. As links in the text: cosmicpython.com, fastapi.tiangolo.com, alistair.cockburn.us, typing.python.org, github.com, nextjs.org, docs.pytest.org and vitest.dev. This is read from the text; nothing was executed.

Is Architecture Patterns 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Architecture Patterns use?

Architecture Patterns 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 Architecture Patterns use?

About 3.4k tokens (SKILL.md is roughly 14k 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 3.5k tokens, read only when the agent opens those files.

What are the alternatives to Architecture Patterns?

Skills that share tags, products or a category with Architecture Patterns: Architecture Patterns (KartikLabhshetwar/better-shot, 2.4k stars), Java Architecture Review (decebals/claude-code-java, 751 stars), Brooks Audit (hyhmrright/brooks-lint, 1.5k stars) and Adopt a Design Pattern (Totoro-jam/battle-tested-patterns, 344 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Patterns?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 289 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 7, 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.