agentleFS
AhmedHabibaAhmedHabiba/architor/.claude/skills/architecture-patterns/SKILL.md

architecture-patterns

Skill6 starsChanged 8 months agoMITView on GitHub

Knowledge base for architecture patterns, trade-offs, and selection criteria. Activates when recommending or evaluating architecture patterns like microservices, monolith, serverless, event-driven, CQRS, or hybrid approaches.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use python-resource-management, error-handling-patterns and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Aver005Skill

    python-resource-management

    Python resource management with context managers, cleanup patterns, and streaming. Use when managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state.

    Also in 3 projects that use this

  • xfstudioSkill

    error-handling-patterns

    Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

    Also in 6 projects that use this

  • CodeWithBehnamSkill

    python-type-safety

    Python type safety with type hints, generics, protocols, and strict type checking. Use when adding type annotations, implementing generic classes, defining structural interfaces, or configuring mypy/pyright.

    Also in 3 projects that use this

  • Aver005Skill

    python-project-structure

    Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.

    Also in 3 projects that use this

  • xfstudioSkill

    python-testing-patterns

    Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

    Also in 6 projects that use this

  • +2 more from Aver005
  • +5 more from xfstudio

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When recommending a pattern, evaluate against these criteria:

    line 10
  2. Distinctive:

    No DevOps/Platform team → Avoid Kubernetes-heavy architectures

    line 16
  3. Distinctive:

    No dedicated DBA → Avoid polyglot persistence

    line 21
  4. Distinctive:

    Read/write asymmetry → CQRS

    line 29
  5. Distinctive:

    Best for: Read-heavy systems, different read/write models, event sourcing

    line 61

“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Architecture Patterns Knowledge

Pattern Selection Framework

When recommending a pattern, evaluate against these criteria:

Team Fit

  • Team size < 5 → Strongly favor monolith or modular monolith
  • Team size 5-15 → Modular monolith or bounded microservices
  • Team size 15+ → Microservices viable if org supports it
  • No DevOps/Platform team → Avoid Kubernetes-heavy architectures
  • Junior-heavy team → Favor simpler patterns with clear boundaries

Operational Reality

  • 1 DevOps engineer → Cannot sustain >3 independently deployed services
  • No dedicated DBA → Avoid polyglot persistence
  • Limited monitoring experience → Start with monolith + good observability
  • Budget constrained → Serverless for spiky loads, monolith for steady

Requirement Signals

  • Independent scaling needs → Microservices or serverless
  • Strong consistency requirements → Monolith or synchronous microservices
  • Event-heavy domain → Event-driven architecture
  • Read/write asymmetry → CQRS
  • Rapid experimentation needed → Modular monolith (fastest to change)
  • Regulatory isolation → Service per compliance boundary

Pattern Comparison Quick Reference

Monolith

  • Best for: Small teams, rapid development, strong consistency needs
  • Risks: Scaling bottleneck, deployment coupling, team scaling limits
  • Migrate to: Modular monolith → microservices (progressive)

Modular Monolith

  • Best for: Teams 3-10, need clear boundaries without operational overhead
  • Risks: Module coupling creep, single deployment unit
  • Migrate to: Extract modules to services as needed

Microservices

  • Best for: Large teams, independent scaling, polyglot needs
  • Risks: Distributed system complexity, data consistency, operational overhead
  • Prerequisite: CI/CD maturity, monitoring, team autonomy

Event-Driven

  • Best for: Async workflows, decoupled services, audit trails
  • Risks: Eventual consistency complexity, debugging difficulty, event schema evolution
  • Prerequisite: Team comfort with async patterns, good monitoring

Serverless-First

  • Best for: Spiky workloads, cost optimization at low scale, rapid prototyping
  • Risks: Cold starts, vendor lock-in, debugging difficulty, cost at scale
  • Prerequisite: Cloud-native comfort, stateless design skills

CQRS

  • Best for: Read-heavy systems, different read/write models, event sourcing
  • Risks: Complexity, eventual consistency, increased codebase size
  • Prerequisite: Strong domain modeling skills

Red Flags by Pattern

  • Microservices with shared database → "You have a distributed monolith"
  • Event sourcing without replay testing → "You'll lose data"
  • Serverless with persistent connections → "Wrong pattern for this workload"
  • CQRS for simple CRUD → "Over-engineered"
  • Monolith with 50+ developers → "Deployment bottleneck incoming"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.