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-architect
onedro1d/dark-factory
Design and architect microservices following Chris Richardson's Microservices Patterns. Use when designing services, APIs, data flows, or evaluating architecture decisions. Guides full workflow from feature intake to production-ready design with observability, async patterns, security, testing, and deployment strategies.
architecture
azeznassar/dotnet-optimizely-skills
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering. USE FOR: .NET architecture choices; layer and domain boundary review; service decomposition; clean architecture, vertical slice, DDD, CQRS, and modular monolith decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
microservices-architect
thienanthx/skill-web-design
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
zroman88/claude-skills-to-cursor
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-design
agricidaniel/awesome-claude-code-toolkit
Microservices design patterns including service mesh, event-driven architecture, saga pattern, and API gateway
architecture-decision-record
itzcull/software-skills
Create, revise, or review Architecture Decision Records (ADRs). Use when documenting architectural decisions, eliciting decision rationale, comparing options, recording trade-offs, superseding previous decisions, or setting up ADR practices and templates.
architecture-decision-record
fattain-naime/engineering-docs
Create a standalone Architecture Decision Record (ADR) for a single significant architectural decision. Captures context, decision, alternatives considered, and consequences. ADRs are immutable - once accepted, they are never edited, only superseded by a new ADR.
architecture-decision-records
botteryosuke/e-station
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
donganhvuphp/claude-skills-lord
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
devenkhatri/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
fengjiehzi/skills
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
juaad024/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
madskruhl12/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
mit-network/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
mturac/everything-openai-codex
Capture architectural decisions made during OpenAI Codex 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
burgebj/claude_everything
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
partha7364/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
pcoulbourne/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
thiranon/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
loulanyue/awesome-claude-notes
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
danielnguyenfinhub/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
mitamarcelo/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
lidge-jun/cli-jaw-skills
Capture architectural decisions made during coding 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
abanoub-ashraf/manus-skills-import
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.
architecture-decision-records
pey-sjitech/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
shalomb/agent-skills
Create, update, and review Architecture Decision Records (ADRs) using the Y-Statement format. Use when making a significant architectural decision, choosing between implementation approaches, or documenting a trade-off that future maintainers should understand. Triggers include "write an ADR", "document this decision", "architecture decision", "Y-statement", or "record this trade-off".
architecture-decision-records
witi-projects/skills
Document technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale. Use when the user says "/architecture-decision-records", "architecture decision records", or asks about architecture decision records.
architecture-decision-records
getskill-agent/getskill-skills
>
architecture-decision-records
kunanonj/claude-skills-hub
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
architecture-decision-records
4gentic/obelus
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
monorepo-improver
frontal-labs/agent-skills
Frontal SDK monorepo specialist with expertise in TypeScript monorepo optimization, package dependency management, build system enhancement, and development workflow improvements. Use when optimizing @frontal/* monorepo structure, improving build performance, or managing package dependencies.
architecture
vivekkothari/frontend-engineering-agent-skills
Frontend system design at scale — micro-frontends, monorepo strategy, module federation, feature-sliced design, BFF pattern, migration strategies, and build-time vs. runtime decisions.
greenfield-monorepo
gabriel-f-santos/coding-agents
>
event-driven-architecture
0motionguy/gicm
Publish-subscribe, event brokers, reactive systems, and loose coupling with events.
event-driven-architecture
hacho55/absolutelyskilled
>
event-driven
keohanoi/design-pattern-skills
This skill should be used when the user asks about "event driven architecture", "when to use event driven", "event sourcing", "message broker", "publish subscribe", "async communication", or mentions needing loosely coupled communication via events.
event-driven-architect
naveedtechlab/skills-library
Design and implement event-driven cloud architectures with Kafka topics, Dapr pub/sub, and scalable microservice patterns. Use when designing distributed systems, implementing async messaging, creating event-based workflows, or building loosely coupled services. Covers fault-tolerant, cloud-portable architectures.
event-driven-arch
eliranabu/schoolclaudeskills
>
event-driven-microservices
robsonrung/rar-skills
>
event-driven
kid-sid/codex-spellbook
Use when designing or debugging an event-driven system — choosing Kafka partitioning strategies, implementing the outbox pattern, handling dead-letter queues, ensuring idempotent consumers, or making event sourcing decisions.
architecture-patterns
devlitus/querybox
Software architecture patterns and best practices
event-driven-systems
eralmansouri/skills
Use for event-driven or message-driven architecture, commands and events, queues, pub/sub, Kafka, choreography, orchestration, sagas, outbox, idempotency, retries, ordering, backpressure, consumer lag, and messaging operations.
architecture-patterns
omar-obando/qwen-orchestrator
Use when designing system architecture, selecting architectural patterns, making trade-off decisions, and implementing scalable, maintainable systems. Includes layered architecture, microservices, domain-driven design, and cloud architecture patterns. Based on software architecture certifications and industry-standard architecture patterns.
event-driven-wait
jcdavis131/cursor-agent-skills
When waiting on a specific observable event — a file appearing, a log line matching, a git ref advancing, a directory growing, a port opening — arm a watcher that wakes on that event instead of polling on a timer. Use when the wait condition is observable as a filesystem, log, or ref change, especially for long waits where blind polling wastes tokens and can miss the moment.
architect-review
aver005/agent-skills
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
microservices-patterns
aaaaqwq/agi-super-team
Comprehensive microservices patterns skill covering service mesh, traffic management, circuit breakers, resilience patterns, Istio, and production microservices architecture
architecture-decision-records
jord5s/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
hainamchung/agent-assistant
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
architecture-decision-records
mrebrahim/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-patterns
aaaaqwq/agi-super-team
Software architecture patterns and best practices
eserstack-monorepo
eser/stack
Monorepo structure, package conventions, version synchronization, and publishing workflow. Use when adding packages, modifying project structure, or managing versions.
system-design-generator
patricio0312rev/skillset
Produces comprehensive system architecture plans for features and products including component breakdown, data flow diagrams, system boundaries, API contracts, and scaling considerations. Use for "system design", "architecture planning", "feature design", or "technical specs".
cy-create-techspec
pedronauck/kodebase-go
Creates a Technical Specification by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, or when technical architecture decisions need documentation. Do not use for PRD creation, task breakdown, or direct code implementation.
podman-orchestration
akarazhev/crypto-scout
Podman Compose orchestration for crypto-scout services including RabbitMQ, TimescaleDB, and microservices
css-craftsman
candeploys/claude-skills
Modern CSS including Grid, Subgrid, container queries, CSS custom properties, animations, and CSS architecture patterns. Trigger for complex CSS layouts, animation design, responsive patterns, or CSS architecture decisions.
product-document
attilaszasz/sdd-pilot
Turns a rough product idea into a project-level Product Requirements Document (`specs/prd.md`) and registers it as the canonical Product Document. Use when running /sddp-prd or when a product needs structured discovery before system design.