236 free skills
Architecture skills
Skills for architecture — system design, microservices decomposition, architecture decision records, and scalability planning.
Sourced from real, public repositories — synced daily, never invented.
236 free skills
Skills for architecture — system design, microservices decomposition, architecture decision records, and scalability planning.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
microservices-architecture
1mangesh1/dev-skills-collection
Microservices 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.
architecture-decision-records
ggailabs/synkos-releases
Write 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.
fastapi-architect
ghalex/skills
Audits 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".
gcp-event-driven-architecture-review
kilo-org/kilo-marketplace
>-
microservices-orchestrator
prompt-or-die-labs/hyper-forge
Expert 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.
microservices-architect
nicolasestrem/antigravity-gemini-skills
a senior microservices architect specializing in distributed system design with deep expertise in Ku
architecture-decision-records
angelmic/everything-claude-code-ios
Capture 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.
architecture-decision-recorder
prompt-or-die-labs/hyper-forge
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.
managing-monorepo
cedmandocdoc/awesome-skills
Defines 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`.
microservices-architect
keez97/claude-architecture-skills
>
event-driven-architect
prompt-or-die-labs/hyper-forge
Design 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.
architecture-patterns
nicholasgriffintn/claude-code
A 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.
architecture-microservices
kentoshimizu/sw-agent-skills
Microservices 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.
architecture-decision-records
kentoshimizu/sw-agent-skills
Architecture 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.
microservices-knowledge
dykyi-roman/awesome-claude-code
Microservices Architecture knowledge base. Provides service decomposition, communication patterns, API gateway, service discovery, and data management guidelines for architecture audits and generation.
architecture-decision-records
sbrudz/agent-skills
Use 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 reverse
kernel-audit-monorepo
ponti-studios/kernel
Audit, 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.
php-monorepo-builder
aaronflorey/agent-skills
Use `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.
bootstrap
michaelmerrill/skills
Initialize 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).
eda-knowledge
dykyi-roman/awesome-claude-code
Event-Driven Architecture knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for EDA audits including messaging, pub/sub, and saga patterns.
microservices-patterns
jonathan0823/opencode-config
Microservices 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.
event-driven-architecture
delorenj/skills
Kafka, 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.
microservices-patterns
afranciny/dev-skills
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
system-design
jwynia/teach
Diagnose design problems and guide architecture decisions for solo developers
documentation
yknothing/prodcraft
Use 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.
microservices
ffsshhttiikk/opencode-agents-skills
Design patterns and architectural approaches for Microservices
microservices-architect
neg0diay/opencode-skills
Designs 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.
microservices-architect
neonetz/opencode-skills
Designs 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.
event-driven-architecture
ffsshhttiikk/opencode-agents-skills
Event-driven architecture patterns using message queues and event streaming
event-driven-architecture
connorads/dotfiles
>
event-driven-architecture
mmondora/claude-skills
Event-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.
event-driven-architecture
azeem-2/hackthonii
Generic 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.
architecture-event-driven
kentoshimizu/sw-agent-skills
Event-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.
architecture-design
liuqi1024/matrix-boot
Design 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.
architecture-decision-records
kumaran-is/claude-code-onboarding
Structured 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.
architecture-decision-records
isloverhatwhite/ecc
Capture 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.
architecture-decision-records
kunanonj/ai-skills-hub
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
documentation
jnpiyush/agentx
Write 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.
microservices-designer
heymoezy/porter
Design 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.
microservices-pro
truongnat/simple-skills
>+
architecture-decision-records
jamkris/everything-gemini-code
Capture 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.
architecture-decision-records
ysyecust/everything-claude-code
Capture 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.
architecture-decision-records
dirnbauer/webconsulting-skills
Creates 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.
architecture-decision-records
zeeroiq/agent-powerhouse
Capture 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.
event-driven-architecture
xliang01dev/useful-claude-features
Use when designing or troubleshooting event-driven systems - guides architectural decisions, scaling analysis, integration patterns, and infrastructure setup
event-driven-architecture
camilooscargbaptista/cto-toolkit
**Event-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.
note-resource-event-driven-architecture
mimichunterz/pocketmind
Use 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.
event-driven
pluginagentmarketplace/custom-plugin-system-design
Production-grade event-driven architecture skill for Kafka, RabbitMQ, event sourcing, CQRS, and message patterns
loom-event-driven
cosmix/claude-code-setup
Event-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.
principle-event-driven
lugassawan/swe-workbench
Event-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.
microservices
cohen-liel/hivemind
Microservices architecture patterns. Use when designing service decomposition, inter-service communication, API gateways, service discovery, event-driven architecture, or distributed systems.
microservices-patterns
truongnat/simple-skills
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
event-driven-patterns
marvinrichter/clarc
Event-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.
micro
openai/plugins
Expert guidance for micro — asynchronous HTTP microservices framework by Vercel. Use when building lightweight HTTP servers, API endpoints, or microservices using the micro library.
microservices-architect
joaroo/awesome-agnostic-skills
Use when designing distributed system architecture, decomposing monolithic applications into independent microservices, or establishing communication patterns between services at scale.
microservices
keohanoi/design-pattern-skills
This skill should be used when the user asks about "microservices architecture", "when to use microservices", "distributed services", "service decomposition", "independent deployable", or mentions needing to split an application into small, independent services.
microservices-architect
mtsatryan/openclaw-ai-agents
Distributed systems architect designing scalable microservice ecosystems. Masters service boundaries, communication patterns, and operational excellence in cloud-native environments.
architecture-advisor
lirielgozi/liri-skills
Helps solo developers with AI agents choose optimal architecture (monolithic/microservices/hybrid)
microservices
hacho55/absolutelyskilled
>
microservices-architect
marttp/my_agent_skills_i_use
Use when user needs microservices architecture help. Examples: "decompose a monolith into microservices", "design service boundaries", "implement event sourcing and CQRS", "set up service mesh with Istio", "design saga patterns"