236 free skills · page 1 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.
architecture-decision-recordswshobson/agentsWrite 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.Architecture15.8kmicroservices-patternswshobson/agentsDesign microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.Architecture11.6k
clickhouse-architecture-advisorclickhouse/agent-skillsMUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.Architecture7.8k
system-designanthropics/knowledge-work-pluginsDesign systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.Architecture6.7karchitectureanthropics/knowledge-work-pluginsCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.Architecture5.8k
architecturemarkdown-viewer/skillsCreate layered system architecture diagrams using HTML/CSS templates with color-coded tiers and grid layouts. Best for technology stacks, microservices topology, and multi-tier application design.Architecture3.6k
human-architect-mindsetbencium/bencium-marketplaceSystematic architectural thinking for irreplaceable human capabilities - domain modeling, systems thinking, constraint navigation, and AI-aware problem decomposition. Use proactively when detecting architectural decisions, system design discussions, or multi-component planning.Architecture2.8k
senior-architectalirezarezvani/claude-skillsThis skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format.Architecture1.4k
architecturesickn33/agentic-awesome-skillsArchitectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.Architecture1.3k
quality-documentation-managerdavila7/claude-code-templatesSenior Quality Documentation Manager for comprehensive documentation control and regulatory document review. Provides document management system design, change control, configuration management, and regulatory documentation oversight. Use for document control system implementation, regulatory document review, change management, and documentation compliance verification.Architecture982cto-advisoralirezarezvani/claude-skillsTechnical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.Architecture868
system-architectaj-geddes/claude-code-bmad-skillsDesigns system architecture, selects tech stacks, defines components and interfaces, addresses non-functional requirements. Trigger words - architecture, system design, tech stack, components, scalability, security, API design, data model, NFR, patterns, microservices, monolithArchitecture809
gomindrally/skillsExpert in Go/Golang development with focus on APIs, microservices, and clean architectureArchitecture671microservicesmindrally/skillsGuidelines for building production-grade microservices with FastAPI/Python and Go, covering serverless patterns, clean architecture, observability, and resilience.Architecture640
system-designjwynia/agent-skillsDiagnose design problems and guide architecture decisions for solo developersArchitecture627
develop-adrproduct-on-purpose/pm-skillsCreates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.Architecture598
fantasy-world-buildingwordflowlab/novel-writer-skillsUse when user mentions fantasy, magic system, or world-building for fantastical settings - provides fantasy genre conventions, magic system design patterns, and world-building frameworksArchitecture540microservices-architectureaj-geddes/useful-ai-promptsComprehensive guide to designing, implementing, and maintaining microservices architectures. Covers service decomposition, communication patterns, data management, deployment strategies, and observability for distributed systems.Architecture499
java-microservicespluginagentmarketplace/custom-plugin-javaBuild microservices - Spring Cloud, service mesh, event-driven, resilience patternsArchitecture468architecture-decisionjwynia/agent-skillsSystematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.Architecture464
ln-120-reference-docs-creatorlevnikolaevich/claude-code-skillsCreates reference docs (ADRs, guides, manuals) for nontrivial tech stack choices. Use when project needs justified architecture decision records.Architecture380microservices-patternssickn33/agentic-awesome-skillsMaster microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.Architecture332
architecture-decision-recordsspencerpauly/awesome-cursor-skillsDocument technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.Architecture314
software-patternsbobmatnyc/claude-mpm-skillsCompare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.Architecture306monorepo-managementsickn33/agentic-awesome-skillsBuild efficient, scalable monorepos that enable code sharing, consistent tooling, and atomic changes across multiple packages and applications.Architecture258
decomposition-planning-roadmaptech-leads-club/agent-skillsCreates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).Architecture258
030-architecture-adr-generaljabrena/plinthUse when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of Plinth ToolkitArchitecture246
trellis-metamindfold-ai/marketplaceMeta-skill for understanding and customizing Mindfold Trellis — the all-in-one AI workflow system for 11 AI coding platforms (Claude Code, Cursor, OpenCode, iFlow, Codex, Kilo, Kiro, Gemini CLI, Antigravity, Qoder, CodeBuddy). Documents the original Trellis system design including architecture, commands, hooks, multi-agent pipelines, monorepo support, and task lifecycle hooks. Use when understanding Trellis architecture, customizing workflows, adding commands or agents, troubleshooting issues, or adapting Trellis to specific projects. Modifications should be recorded in a project-local trellis-local skill, not here.Architecture241
adr-writerpatricio0312rev/skillsCreates Architecture Decision Records documenting key technical decisions with context, alternatives considered, tradeoffs, consequences, and decision owners. Use when documenting "architecture decisions", "technical choices", "design decisions", or "ADRs".Architecture237system-design-generatorpatricio0312rev/skillsProduces 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".Architecture233
backend-architectrmyndharis/antigravity-skillsExpert backend architect specializing in scalable API design,Architecture205
technical-specmajiayu000/spellbookTechnical specification and design document expert. Use when writing design docs, RFCs, ADRs, or evaluating technology choices. Covers C4 model, system design, and architecture documentation.Architecture205
bmad-architecturebmad-code-org/bmad-methodWork out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"Architecture189
microservices-expertpersonamanagmentlayer/pclExpert-level microservices architecture, patterns, service mesh, and distributed systemsArchitecture174design-expertpersonamanagmentlayer/pclExpert-level system design, architecture patterns, scalability, and distributed systemsArchitecture172
architecturevudovn/ag-kitArchitectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.Architecture166
microservices-designrohitg00/awesome-claude-code-toolkitMicroservices design patterns including service mesh, event-driven architecture, saga pattern, and API gatewayArchitecture164
event-driven-architect404kidwiz/claude-supercode-skillsExpert in designing asynchronous, decoupled systems using Event-Driven Architecture (EDA). Specializes in AsyncAPI, Event Mesh, and CloudEvents standards. Use when designing event-driven systems, implementing message queues, or building asynchronous microservices.Architecture154
map-project-monorepoulpi-io/skillsThis skill mutates durable project memory across multiple workspace members. Non-negotiable rules: 1. Discover the real workspace shape before writing any member CLAUDE.md. 2. Document the actual exported or reachable surface, not raw visibility markers alone. 3. Keep each member file self-contained…Architecture150
microservices-architecturetravisjneuman/.claudeMicroservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.Architecture141
interview-preprightnow-ai/openfangTechnical interview preparation expert for algorithms, system design, and behavioral questionsArchitecture134event-driven-architecturetravisjneuman/.claudeThis skill covers designing and implementing event-driven systems that decouple services through asynchronous message passing.Architecture131
adrncklrs/startup-os-skillsExpert Architecture Decision Record (ADR) creation and lifecycle managementArchitecture123
architecture-paradigmsathola/claude-night-marketSelects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.Architecture116
system-designs-hiraoku/synapse-a2aGuide architectural decisions and produce structured design artifacts.Architecture114
event-driventhebeardedbearsas/claude-craftEvent Sourcing, CQRS, Saga patterns, event bus (Kafka, RabbitMQ, AWS EventBridge). Use when implementing event-driven architecture, distributed transactions, or event sourcing.Architecture113architect-reviewrmyndharis/antigravity-skillsMaster software architect specializing in modern architectureArchitecture111architect-reviewer404kidwiz/claude-supercode-skillsUse when user needs system design validation, architectural pattern assessment, or technology stack evaluation.Architecture110
rememberlangchain-ai/deepagentsReview the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.Architecture109
architecture-decisionsjwilger/agent-skillsValue: Communication -- architecture decisions grounded in verified research ensure every contributor understands not just why a choice was made, but that the reasoning reflects reality. Decisions based on assumptions are decisions waiting to fail.Architecture103microservices-architect404kidwiz/claude-supercode-skillsDistributed systems expert specializing in service decomposition, orchestration, and microservices architecture patterns. Use when designing microservices, defining service boundaries, implementing service mesh, or handling distributed system challenges. Triggers include "microservices", "service mesh", "service decomposition", "distributed systems", "API gateway", "event-driven".Architecture102document-writer404kidwiz/claude-supercode-skillsExpert in creating technical documentation, architectural decision records (ADRs), and RFCs. Specializes in structured knowledge management and system documentation. Use when writing technical docs, ADRs, RFCs, or system design documents.Architecture99architecture-reviewathola/claude-night-marketAssesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.Architecture99
ml-system-design-interviewcuriositech/some_claude_skillsCoaches end-to-end ML system design interviews covering inference pipelines, recommendation systems, RAG, feature stores, and monitoring. Use for L6+ design rounds, ML architecture whiteboarding,Architecture98tech-presentation-interviewcuriositech/some_claude_skillsPrepares for "reverse system design" rounds where you present YOUR past technical work. Use for project selection, narrative arc structuring, whiteboard diagrams, depth calibration, and hostileArchitecture98
intent-syncarcblock/iddAfter implementation is complete and tests pass, sync confirmed details back to Intent. Captures finalized interfaces, data structures, naming conventions, and architecture decisions. Use after development is done and user confirms the implementation.Architecture93golang-webmajiayu000/spellbookModern Go Web application architecture guide. Use when creating new Go web projects, APIs, or microservices. Covers project structure, tech stack selection, and best practices based on Go standards.Architecture92legacy-modernizer404kidwiz/claude-supercode-skillsExpert in migrating monolithic, legacy systems to modern architectures using patterns like Strangler Fig, CDC, and Anti-Corruption Layers. Use when modernizing legacy codebases, breaking monoliths, or planning incremental migrations. Triggers include "legacy migration", "modernization", "strangler fig", "monolith to microservices", "legacy rewrite", "incremental migration".Architecture89
event-driven-architecturenickcrew/claude-cortexEvent-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.Architecture88
docs-with-mermaidpranavred/claude-code-documentation-skillCreate excellent technical documentation with Mermaid diagrams. Use when documenting code architecture, API flows, database schemas, state machines, system design, or any technical concept that benefits from visual diagrams. Also use when asked to explain code, create documentation, write README files, or document how systems work.Architecture83Other tasks
same rules, different job
