236 free skills · page 3 of 4
Architecture skills
Skills for architecture — system design, microservices decomposition, architecture decision records, and scalability planning.
Real files from public repositories — hand-curated, never invented. Sorted by installs.
3 / 4page
architecture-decision-recordsggailabs/synkos-releasesWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.Architecture9
microservices-architecture1mangesh1/dev-skills-collectionMicroservices architecture patterns, trade-offs, and implementation guidance. Use when user asks about service decomposition, bounded contexts, API gateways, distributed transactions, saga pattern, circuit breaker, service mesh, event-driven architecture, CQRS, event sourcing, message brokers, service discovery, distributed tracing, contract testing, strangler fig migration, polyglot persistence, eventual consistency, inter-service communication, or any microservices design, operational concerns, and architectural decisions.Architecture9
gcp-event-driven-architecture-reviewkilo-org/kilo-marketplaceAct as the GCP event-driven architecture reviewer who refuses to treat missing dead-letter topics, untested idempotency, or uncapped retry configurations as acceptable in production.Architecture8
fastapi-architectghalex/skillsAudits a FastAPI project against architecture rules. Use when asked to "review routes", "check architecture", "audit this project", "does this follow fastapi rules", or "review my code structure".Architecture8
architecture-decision-recordsangelmic/everything-claude-code-iosCapture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.Architecture7
managing-monorepocedmandocdoc/awesome-skillsDefines the workspace contract for a TypeScript monorepo with pnpm and Turborepo — folder roles (apps/ vs packages/), cross-package imports (exports, workspace:*), package runners (<dir>:<script>, e.g. pnpm web:dev), and root .gitignore. Use when adding a package, choosing apps vs packages, wiring an import, adding a package script or root runner, or initializing .gitignore.Architecture7
microservices-orchestratorprompt-or-die-labs/hyper-forgeExpert skill for designing, decomposing, and managing microservices architectures. Activates when users need help with microservices design, service decomposition, bounded contexts, API contracts, or transitioning from monolithic to microservices architectures.Architecture7
microservices-architectnicolasestrem/antigravity-gemini-skillsa senior microservices architect specializing in distributed system design with deep expertise in KuArchitecture7architecture-decision-recorderprompt-or-die-labs/hyper-forgeCreate and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.Architecture7
microservices-architectkeez97/claude-architecture-skillsDistributed systems introduce complexity that's not worth paying unless you genuinely need it.Architecture6event-driven-architectprompt-or-die-labs/hyper-forgeDesign event-driven architectures using Kafka, RabbitMQ, event sourcing, CQRS, and saga patterns. Activates when users need help with event-driven design, message queues, event sourcing, or asynchronous communication patterns.Architecture6
architecture-decision-recordskentoshimizu/sw-agent-skillsArchitecture Decision Record workflow for capturing technical decisions, alternatives, trade-offs, and revision triggers over time. Use when decisions materially affect system behavior, cost, or team workflow; do not use for trivial implementation choices.Architecture6architecture-microserviceskentoshimizu/sw-agent-skillsMicroservices architecture workflow for service boundary design, independent deployability, and distributed operational safety. Use when domain and team structure justify independent service evolution; do not use as a default scaling strategy for all systems.Architecture6
architecture-patternsnicholasgriffintn/claude-codeA specialist skill that recognises and applies common software architecture patterns within a codebase. This skill should be used during the design and development phases of a project.Architecture6
kernel-audit-monorepoponti-studios/kernelAudit, simplify, and refactor TypeScript monorepos using Turborepo, pnpm workspaces, Expo/React Native, web apps, Hono API/RPC, Drizzle, Postgres, TanStack Query, and ArkType. Use when reviewing package boundaries, reducing duplicated code, proposing behavior-preserving refactor plans, reorganizing workspace architecture, enforcing layer boundaries, or implementing monorepo-wide structural changes.Architecture5
php-monorepo-builderaaronflorey/agent-skillsUse symplify/monorepo-builder to manage PHP monorepos with vendor/bin/monorepo-builder and monorepo-builder.php. Trigger this skill when the user mentions monorepo-builder, merging package composer.json files into a root composer.json, validating inter-package versions, configuring package directories, propagating dependencies, or automating monorepo releases and release workers.Architecture5
eda-knowledgedykyi-roman/awesome-claude-codeEvent-Driven Architecture knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for EDA audits including messaging, pub/sub, and saga patterns.Architecture5microservices-knowledgedykyi-roman/awesome-claude-codeMicroservices Architecture knowledge base. Provides service decomposition, communication patterns, API gateway, service discovery, and data management guidelines for architecture audits and generation.Architecture5
bootstrapmichaelmerrill/skillsInitialize new codebases — standalone project, monorepo, or new app/package/service within existing repo. Interview + convention inheritance + scaffold + foundation docs. Triggers: 'new project,' 'bootstrap,' 'init,' 'scaffold,' 'add app,' 'add package,' 'new service,' greenfield, empty directory. Not for: adding features (scope), deploying (deploy-to-vercel), hooks on existing repos (setup-pre-commit).Architecture5
architecture-decision-recordssbrudz/agent-skillsUse when making architectural decisions during planning or design sessions, when choosing between technologies, patterns, or system designs that affect multiple components or are hard to reverseArchitecture5
microservices-patternsjonathan0823/opencode-configMicroservices architecture patterns including service discovery, circuit breakers, event-driven architecture, API gateways, and distributed systems. Use when designing microservices, implementing inter-service communication, or managing distributed systems.Architecture4
system-designjwynia/teachDiagnose design problems and guide architecture decisions for solo developersArchitecture4
microservices-patternsafranciny/dev-skillsDesign microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.Architecture4
event-driven-architecturedelorenj/skillsKafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.Architecture4
documentationyknothing/prodcraftUse when a feature, architecture decision, incident, or workflow change needs durable technical documentation such as tutorials, reference docs, ADRs, runbooks, or maintenance guidance instead of ad hoc notes.Architecture4
event-driven-architectureconnorads/dotfilesThis begins where a domain event leaves the process. The architecture skill owns the inside of a bounded context - returning events as values, one aggregate per transaction. This owns the wire: what happens once an event crosses a process or service boundary and someone you don't deploy with…Architecture3
event-driven-architectureffsshhttiikk/opencode-agents-skillsEvent-driven architecture patterns using message queues and event streamingArchitecture3
architecture-decision-recordsisloverhatwhite/eccCapture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.Architecture3
documentationjnpiyush/agentxWrite effective documentation including inline docs, README structure, API documentation, and code comments. Use when writing README files, documenting APIs, creating architecture decision records, adding inline code documentation, or setting up documentation tooling.Architecture3architecture-event-drivenkentoshimizu/sw-agent-skillsEvent-driven architecture workflow for asynchronous integration, decoupled workflows, and failure-tolerant event propagation. Use when temporal decoupling and independent evolution are required; do not use when strict synchronous consistency is mandatory across all steps.Architecture3
architecture-decision-recordskumaran-is/claude-code-onboardingStructured templates and process for capturing Architecture Decision Records (ADRs) — context, decision, consequences, and status. Use when making any significant or irreversible technical decision (framework selection, API design, database schema, infrastructure choice) to ensure every option considered and trade-off made is permanently documented before implementation begins.Architecture3
event-driven-architecturemmondora/claude-skillsEvent-driven systems with CloudEvents and GCP Pub/Sub. Event design, schema evolution, delivery guarantees, idempotency, eventual consistency. Use when designing event systems, publishing/consuming events, or implementing async workflows.Architecture3
microservices-architectneg0diay/opencode-skillsDesigns distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.Architecture3
microservices-architectneonetz/opencode-skillsDesigns distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.Architecture3
event-driven-architectureazeem-2/hackthoniiGeneric Event-Driven Architecture patterns with Kafka, Dapr, and modern messaging systems. Provides reusable patterns for building scalable, resilient event-driven microservices. Framework-agnostic implementation supporting multiple message brokers, state stores, and event patterns. Follows 2025 best practices for distributed systems.Architecture3microservicesffsshhttiikk/opencode-agents-skillsDesign patterns and architectural approaches for MicroservicesArchitecture3
architecture-decision-recordskunanonj/ai-skills-hubComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.Architecture3
architecture-designliuqi1024/matrix-bootDesign business architecture and technical architecture for staged software projects, including Mermaid diagrams, module boundaries, data flows, deployment view, integration points, project structure, and architecture risks. Use when moving from business context to architecture, when documenting module/service boundaries, or when reviewing whether architecture is ready for API/database design and implementation.Architecture3
microservices-protruongnat/simple-skillsSkill text is English; answer in the user’s preferred language when rules or the conversation specify it.Architecture2
event-driven-architecturecamilooscargbaptista/cto-toolkitEvent-Driven Architecture Review: Reviews and designs event-driven systems — Event Sourcing, CQRS, Saga patterns, Domain Events, message brokers, and eventual consistency. Use when the user mentions events, event sourcing, CQRS, saga, choreography vs orchestration, Kafka architecture, event store, projections, read models, domain events, or wants to design or review an event-driven system.Architecture2
principle-event-drivenlugassawan/swe-workbenchEvent-driven architecture — event sourcing, CQRS, sagas, choreography vs orchestration, schema evolution, consumer groups, partitions, ordering, idempotent handlers, outbox pattern, dead letter queues. Auto-load when designing event-driven systems, evaluating event sourcing or CQRS, planning saga workflows, evolving event schemas across consumers, configuring consumer groups or partitions, implementing idempotent consumers or the outbox pattern, managing dead letter queues, or assessing whether event-driven architecture fits the problem.Architecture2
microopenai/pluginsExpert guidance for micro — asynchronous HTTP microservices framework by Vercel. Use when building lightweight HTTP servers, API endpoints, or microservices using the micro library.Architecture2microservices-patternstruongnat/simple-skillsDesign microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.Architecture2
architecture-decision-recordsysyecust/everything-claude-codeCapture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.Architecture2
architecture-decision-recordszeeroiq/agent-powerhouseCapture architectural decisions made during Copilot/Codex/ClaudeCode/Antigravity sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.Architecture2
microservicescohen-liel/hivemindMicroservices architecture patterns. Use when designing service decomposition, inter-service communication, API gateways, service discovery, event-driven architecture, or distributed systems.Architecture2
loom-event-drivencosmix/claude-code-setupEvent-driven architecture patterns including message queues, pub/sub, event sourcing, CQRS, and sagas. Use for async messaging, distributed transactions, event stores, domain/integration events, data streaming, choreography/orchestration, delivery guarantees, or integrating with Kafka, RabbitMQ, Pulsar, SQS/SNS, or NATS.Architecture2
architecture-decision-recordsdirnbauer/webconsulting-skillsCreates and reviews architecture decision records (ADRs), decision logs, and supersession histories using established conventions and verifiable evidence. Use when users ask to write, reconstruct, audit, standardize, validate, or maintain ADRs, architecture decisions, decision logs, or ADR templates in Markdown or reStructuredText.Architecture2
microservices-designerheymoezy/porterDesign service boundaries, bounded contexts, interfaces, data ownership, and migration paths for distributed systems. Use when work involves decomposing monoliths, deciding whether microservices are justified, mapping domain boundaries across teams, choosing synchronous versus asynchronous collaboration patterns, defining API or event contracts, or preventing shared-database and distributed-transaction anti-patterns. Do not use for routine backend coding when service decomposition is not the core challenge.Architecture2
architecture-decision-recordsjamkris/everything-gemini-codeCapture architectural decisions made during Gemini CLI sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.Architecture2
event-driven-patternsmarvinrichter/clarcEvent-Driven Architecture: Kafka deep-dive (partitioning, consumer groups, exactly-once semantics, Schema Registry, DLQ, compacted topics), AWS EventBridge (content filtering, cross-account, archive/replay), Pub/Sub patterns (CloudEvents standard, fan-out, event versioning), and at-least-once delivery with idempotency.Architecture2
note-resource-event-driven-architecturemimichunterz/pocketmindUse when you need to understand or modify PocketMind note save to resource indexing flow, including outbox, MQ hint/DLQ compensation, projector consumption, and consistency boundaries.Architecture2
event-drivenpluginagentmarketplace/custom-plugin-system-designProduction-grade event-driven architecture skill for Kafka, RabbitMQ, event sourcing, CQRS, and message patternsArchitecture2
event-driven-architecturexliang01dev/useful-claude-featuresUse when designing or troubleshooting event-driven systems - guides architectural decisions, scaling analysis, integration patterns, and infrastructure setupArchitecture2
architecture-decision-recordsgetskill-agent/getskill-skillsComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.Architecture1
event-driven-architecturehacho55/absolutelyskilledWhen this skill is activated, always start your first response with the 🧢 emoji.Architecture1
event-driven-archeliranabu/schoolclaudeskillsImplementing event sourcing; Setting up CQRS (Command Query Responsibility Segregation); Solving the dual-write problem with the outbox patternArchitecture1
greenfield-monorepogabriel-f-santos/coding-agentsStand up a new polyglot monorepo: interview → plan → confirm → scaffold a runnable skeleton with the harness, lint, tests, pre-commit, a Docker Compose dev stack (+ seed), dev scripts, and root + per-app AGENTS.md. Two stacks are pinned and curated; any other stack is researched live and scaffolded.Architecture1
architecture-decision-recordsdonganhvuphp/claude-skills-lordCapture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.Architecture1
architecture-patternsaaaaqwq/agi-super-teamSoftware architecture patterns and best practicesArchitecture1Other tasks
same rules, different job
