236 free skills · page 4 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.
4 / 4page
podman-orchestrationakarazhev/crypto-scoutPodman Compose orchestration for crypto-scout services including RabbitMQ, TimescaleDB, and microservicesArchitecture1
architect-reviewaver005/agent-skillsMaster 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.Architecture1
architectureazeznassar/dotnet-optimizely-skillsDesign 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.Architecture1
architecture-decision-recordsdanielnguyenfinhub/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.Architecture1
architecture-decision-recordsdevenkhatri/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.Architecture1
architecture-patternsdevlitus/queryboxSoftware architecture patterns and best practicesArchitecture1
eserstack-monorepoeser/stackMonorepo structure, package conventions, version synchronization, and publishing workflow. Use when adding packages, modifying project structure, or managing versions.Architecture1
architecture-decision-recordsfengjiehzi/skillsCapture 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
monorepo-improverfrontal-labs/agent-skillsFrontal 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.Architecture1
microserviceshacho55/absolutelyskilledWhen this skill is activated, always start your first response with the 🧢 emoji.Architecture1
architecture-decision-recorditzcull/software-skillsCreate, 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.Architecture1
microservices-architectjoaroo/awesome-agnostic-skillsUse when designing distributed system architecture, decomposing monolithic applications into independent microservices, or establishing communication patterns between services at scale.Architecture1
architecture-decision-recordsjord5s/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.Architecture1
architecture-decision-recordsjuaad024/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.Architecture1
microserviceskeohanoi/design-pattern-skillsThis 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.Architecture1
architecture-advisorlirielgozi/liri-skillsHelps solo developers with AI agents choose optimal architecture (monolithic/microservices/hybrid)Architecture1
architecture-decision-recordsloulanyue/awesome-claude-notesCapture 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-decision-recordsmit-network/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.Architecture1
architecture-decision-recordsmitamarcelo/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.Architecture1
microservices-architectmtsatryan/openclaw-ai-agentsDistributed systems architect designing scalable microservice ecosystems. Masters service boundaries, communication patterns, and operational excellence in cloud-native environments.Architecture1
architecture-decision-recordsmturac/everything-openai-codexCapture 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.Architecture1
microservices-architectonedro1d/dark-factoryDesign 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.Architecture1
architecture-decision-recordspcoulbourne/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.Architecture1
event-driven-microservicesrobsonrung/rar-skillsRead-only decision skill. Do not implement the architecture unless the user asks after the brief.Architecture1
microservices-architectthienanthx/skill-web-designDesigns 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.Architecture1
architecture-decision-recordswiti-projects/skillsDocument 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.Architecture1
microservices-architectzroman88/claude-skills-to-cursorDesigns 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.Architecture1
event-driven-architecture0motionguy/gicmPublish-subscribe, event brokers, reactive systems, and loose coupling with events.Architecture1
architecture-decision-records4gentic/obelusComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.Architecture1
microservices-patternsaaaaqwq/agi-super-teamComprehensive microservices patterns skill covering service mesh, traffic management, circuit breakers, resilience patterns, Istio, and production microservices architectureArchitecture1
architecture-decision-recordsabanoub-ashraf/manus-skills-importWrite 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.Architecture1
microservices-designagricidaniel/awesome-claude-code-toolkitMicroservices design patterns including service mesh, event-driven architecture, saga pattern, and API gatewayArchitecture1
product-documentattilaszasz/sdd-pilotTurns 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.Architecture1
architecture-decision-recordsbotteryosuke/e-stationCapture 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-decision-recordsburgebj/claude_everythingCapture 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
css-craftsmancandeploys/claude-skillsModern 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.Architecture1
event-driven-systemseralmansouri/skillsUse 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.Architecture1
architecture-decision-recordfattain-naime/engineering-docsCreate 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.Architecture1
architecture-decision-recordshainamchung/agent-assistantComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.Architecture1
event-driven-waitjcdavis131/cursor-agent-skillsWhen 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.Architecture1event-drivenkeohanoi/design-pattern-skillsThis 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.Architecture1
event-drivenkid-sid/codex-spellbookUse 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.Architecture1
architecture-decision-recordskunanonj/claude-skills-hubComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.Architecture1
architecture-decision-recordslidge-jun/cli-jaw-skillsCapture 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.Architecture1
architecture-decision-recordsmadskruhl12/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.Architecture1
microservices-architectmarttp/my_agent_skills_i_useUse 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"Architecture1
architecture-decision-recordsmrebrahim/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.Architecture1
event-driven-architectnaveedtechlab/skills-libraryDesign 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.Architecture1
architecture-patternsomar-obando/qwen-orchestratorUse 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.Architecture1
architecture-decision-recordspartha7364/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.Architecture1
system-design-generatorpatricio0312rev/skillsetProduces 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".Architecture1
cy-create-techspecpedronauck/kodebase-goCreates 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.Architecture1
architecture-decision-recordspey-sjitech/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.Architecture1
architecture-decision-recordsshalomb/agent-skillsCreate, 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".Architecture1
architecture-decision-recordsthiranon/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.Architecture1
architecturevivekkothari/frontend-engineering-agent-skillsFrontend system design at scale — micro-frontends, monorepo strategy, module federation, feature-sliced design, BFF pattern, migration strategies, and build-time vs. runtime decisions.Architecture1Other tasks
same rules, different job
