236 free skills · page 2 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.
2 / 4page
architecture-reviewoimiragieo/agent-studioArchitecture review and design validation. Evaluates system designs against best practices, identifies anti-patterns, and ensures architectural decisions align with non-functional requirements.Architecture83
designing-systemsdralgorhythm/claude-agentic-frameworkProduces this framework's ADR and system-design artifacts from bundled templates with trade-off analysis. Use when designing a system or component, choosing between architectures, or recording an architecture decision in the planning flow.Architecture81
arch-upkeephairyf/skillsArchitecture health-check and upgrade orchestrator. Use to detect a repo’s current shape (lib/cli/monorepo/webext/vscode/...) and migrate it onto the canonical tsdown-based starter architectures.Architecture76
markdown-doc-writeryennanliu/cs_basicsTechnical documentation writer specializing in creating clear, well-structured markdown documents for algorithms, system design, interview preparation, and code documentation. Use when writing README files, algorithm explanations, system design docs, or technical guides.Architecture75
laravel-event-driven-architectureiserter/laravel-claude-agentsBest practices for Laravel events and listeners including event discovery, queued listeners, subscribers, and model events for decoupled architecture.Architecture73
architecture-decision-recordvalidkeys/sherpyExtracts key architectural decisions from technical-requirements.yaml and formalizes them as individual ADR markdown files in an adrs/ directory. Each ADR captures context, the decision made, alternatives considered, and consequences — creating a durable record of why the system is built the way it is.Architecture71
python-monorepo-architecturebm629/agent-skillsThis skill is about the cross-package layer of a Python monorepo: a single repository holding several installable packages (members) managed by a uv workspace — typically one shared library plus one or more application or CLI members that build on it.Architecture70
graphrag-system-designlyndonkl/claudeDesigns complete GraphRAG systems integrating graph databases, vector stores, orchestration frameworks, and LLM reasoning. Guides through pattern selection, technology stack decisions, integration pipeline design, and domain-specific customizations. Use when designing GraphRAG systems, choosing technology stacks for graph-augmented retrieval, combining Neo4j with LLM, using LangChain/LlamaIndex knowledge graphs, applying community detection for RAG, building hybrid symbol-vector pipelines, or deploying production or domain-specific GraphRAG.Architecture70
oci-eventsacedergren/oci-agent-skillsUse when implementing event-driven automation, setting up CloudEvents rules, troubleshooting event delivery failures, or integrating with Functions/Streaming/Notifications. Covers event rule patterns, filter syntax, action types, dead letter queue configuration, and event-driven architecture anti-patterns.Architecture67
accelint-architecture-docgohypergiant/agent-skillsCreate or update a living ARCHITECTURE.md for a codebase. Use when the user wants to write, refresh, restructure, or maintain an architecture document; document how the system is organized across tech stack, deployment model, services, components, and data stores; or turn codebase findings into durable architecture docs for engineers or agents. Trigger on requests such as write an architecture doc, document this system, create or update ARCHITECTURE.md, give me a technical overview of this repo, or map out how this app is put together, even when the file is not named. Prefer this skill for file-producing architecture documentation, not for generic architecture advice, implementation planning, or diagram-only brainstorming unless that work is clearly part of updating the document.Architecture62
create-adrmajesticlabs-dev/majestic-marketplaceCreate Architecture Decision Records (ADRs) to document significant technical decisions, their context, alternatives considered, and consequences. Use when making architectural choices, selecting libraries/frameworks, or designing system components.Architecture59
blueprint-adr-listlaurigates/claude-pluginsList ADRs as a markdown table with title, status, date, domain. Use when generating an ADR index, auditing ADR status, or reviewing all architecture decisions.Architecture57
senior-solution-architectericgandrade/claude-superskillsThis skill should be used when the user needs to design, review, or document complex software architectures. Use when creating C4 diagrams, writing Architecture Decision Records (ADRs), applying Clean, Hexagonal, or Domain-Driven Design patterns, or conducting system design reviews.Architecture55
microservices-patternsnickcrew/claude-cortexComprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monoliths, or implementing service-to-service communication.Architecture54
write-adrexistential-birds/beagleUse when you want to generate Architecture Decision Records from this session. Triggers on \"write ADRs\", \"document our decisions\", \"create decision records\", \"record the choices we made\". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.Architecture52
architecture-decision-recordmohitagw15856/pm-claude-skillsCreate an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.Architecture51
nerd-specdanangjoyoo/nerdUse when defining requirements, observable behavior, boundaries, or system design and stopping before implementation planning or execution.Architecture50
adrjellydn/my-ai-toolsRecord architecture decisions with ADRs — captures why, alternatives considered, and consequencesArchitecture49
decisionsmaragudk/skillsGuide for recording significant architectural and design decisions in docs/decisions.md. Use this skill when clearly significant architectural decisions are made (database choices, frameworks, core design patterns) or when explicitly asked to document a decision. Be conservative - only suggest for major decisions, not minor implementation details.Architecture49figma-spacing-systemmohitagw15856/pm-claude-skillsDesign a spacing and layout token system for a Figma design system. Use when asked to create a spacing system, define layout tokens, set up a grid system, build a spacing scale, or establish layout foundations for a Figma file. Produces a complete spacing scale, grid definition, component spacing conventions, and Figma implementation guide.Architecture48
quality-documentation-managerovachiever/droid-tingsSenior 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.Architecture48
senior-architectinfrasity-labs/dev-gtm-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.Architecture41
system-designnoobygains/godmodeUse when making technology or structural decisions - selecting databases, APIs, auth strategies, caching layers, file organization, or weighing monolith against servicesArchitecture41
senior-architectaaaaqwq/agi-super-teamThis 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.Architecture41
ddd-architecture-selectorfull-stack-skills/ddd-skillsArchitecture selection decision guide — help users choose from 5 DDD architectures (Layered/Onion/Hexagonal/Clean/COLA) with decision matrix, team size mapping, domain classification (core/generic/supporting), microservice splitting recommendation, and CQRS level suggestion. Use when user asks about architecture selection, 架构选型, COLA vs 六边形, cleaner architecture vs onion, 微服务拆分, or which architecture to use.Architecture41
project-plannersilvainfm/claude-skillsComprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.Architecture40
golang-gin-architecthenriqueatila/golang-gin-best-practicesSoftware architect for Go Gin APIs. Use when making architecture decisions, evaluating complexity, designing systems, choosing patterns, or coordinating across gin skills.Architecture40retention-systemmajesticlabs-dev/majestic-marketplaceDesign customer retention systems with health scoring, churn prediction, and proactive engagement workflows. Use when reducing churn or maximizing LTV.Architecture39microservices-decompositionmohitagw15856/pm-claude-skillsDesign a microservices decomposition for a monolith or new system, defining service boundaries, ownership, communication patterns, and migration plan. Use when asked to decompose a monolith, define service boundaries, design a microservices architecture, or plan a strangler-fig migration. Produces a bounded context map, service inventory table, communication pattern decisions, data ownership matrix, migration roadmap, and risk register.Architecture36
event-driven-architectwyattowalsh/agentsDesign asynchronous systems built around durable events, explicit contracts, and operationally safe consumers.Architecture36
conceptscontextvm/cvmiUnderstand ContextVM core concepts, architecture decisions, and frequently asked questions. Use when users need clarification on what ContextVM is, why it uses Nostr, decentralization benefits, public vs private servers, network topology, or comparisons with traditional MCP.Architecture35
oma-architecturegracefullight/stock-checkerArchitecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.Architecture33
event-driven-architecturedaemon-blockint-tech/agentic-enteprises-skillDefine event types, producers/consumers, sync vs async boundaries, and non-goals.Architecture31
domain-driven-designjoaquimscosta/arkhe-claude-pluginsExpert guidance for Domain-Driven Design architecture and implementation. Use when designing complex business systems, defining bounded contexts, structuring domain models, choosing between modular monolith vs microservices, implementing aggregates/entities/value objects, or when users mention "DDD", "domain-driven design", "bounded context", "aggregate", "domain model", "ubiquitous language", "event storming", "context mapping", "domain events", "anemic domain model", strategic design, tactical patterns, or domain modeling. Helps make architectural decisions, identify subdomains, design aggregates, and avoid common DDD pitfalls.Architecture31microservice-researcherdaemon-blockint-tech/agentic-enteprises-skillResearch domain decomposition, bounded contexts, and candidate service boundaries; Compare microservices vs modular monolith (or other styles) with explicit trade-offs; Analyze sync vs async integration, data ownership, and consistency models at decision levelArchitecture29
architecture-decision-recordsakindu23/my-agent-skillsCanonical owner for ADR creation in a project: detect or accept invocation, draft, get approval, write the ADR, initialize scaffolding if needed, and update the index.Architecture28microservices-developerdaemon-blockint-tech/agentic-enteprises-skillMap domains, define service APIs, and document non-goals.Architecture28
recording-architecture-decisionsganyuanran/aegisUse when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.Architecture28microservices-analystdaemon-blockint-tech/agentic-enteprises-skillDefine analysis boundary (product line, region, cluster namespace, business capability), data sources, and audience (exec brief vs engineering backlog). List non-goals and hand off greenfield design to microservice-researcher when appropriate.Architecture28architecture-decision-recordsaaaaqwq/agi-super-teamWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...Architecture27
portfolio-positioningrealjaymes/marketingagentskillsCreates positioning, messaging, and brand architecture frameworks for multi-product companies. Use when the user wants to 'position a product suite,' 'multi-product positioning,' 'portfolio positioning,' 'brand architecture,' 'core narrative,' 'house of brands vs branded house,' 'product portfolio messaging,' 'launch a second product,' 'launch a new product into our suite,' 'audit our portfolio messaging,' or 'are our products fighting each other.' Sits above product-positioning and product-messaging in the hierarchy. Forces a brand architecture decision first, then builds the layered framework that single-product skills run inside of.Architecture26turborepoacedergren/agentic-toolsUse when making Turborepo monorepo architecture decisions: choosing between monorepo vs polyrepo, deciding when to split packages, debugging cache misses, setting package boundaries, or avoiding circular dependencies. NOT for basic CLI syntax. Triggers on: turborepo, turbo cache miss, package boundaries, monorepo architecture. Triggers on "debug turbo cache" or "design monorepo boundaries".Architecture25
architecture-decision-recordsdavila7/claude-code-templatesComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.Architecture25
microservices-patternsrmyndharis/antigravity-skillsDesign microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.Architecture22
turborepo-architecturedobroslavradosavljevic/skillsPortable monorepo house style for Turborepo + Bun/pnpm workspaces. Use this skill alone — it does not depend on other skills.Architecture21
architecture-pattern-selectoralirezarezvani/claude-cto-teamRecommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints. Use when cto-architect needs to select the right architectural approach for a new system or migration.Architecture20
monorepo-masteryuniorglez/gemini-elite-coreSenior Monorepo Architect & Platform Engineer for 2026. Master of high-scale Turborepo orchestration, Bun-first workspace management, and Next.js 16/Tailwind 4 modular architectures. Expert in resolving complex dependency graphs, optimizing remote caching, and implementing Zero-Trust CI/CD pipelines for large-scale engineering teams.Architecture20architectural-analysisnickcrew/claude-cortexUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).Architecture19
architecture-designeralexander-danilenko/cortex-ai-skillsUse when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.Architecture18
mono-repo-typescriptbeecode-rs/claude-skillsExpert in TypeScript monorepo architecture using pnpm workspaces. Helps with structuring packages (microservices, web apps, mobile apps, shared libs), configuring ES modules with path aliases, centralized config, Docker Compose orchestration, and inter-package dependencies. Use when user mentions monorepo, pnpm workspace, packages folder, shared libraries, common libs, multi-package project, microservices architecture, Docker Compose development environment, workspace setup, monorepo structure, package organization, shared config. Also use when starting a new TypeScript project that might grow to multiple services/apps, when splitting a service into smaller pieces, when asking about code sharing between frontend and backend, or when setting up any project with more than one deployable unit.Architecture18architectdralgorhythm/claude-agentic-frameworkDesign systems and record architecture decisions as ADRs — a user-invoked Principal Architect workflow.Architecture17
outbox-patternyonatangross/orchestkitTransactional outbox pattern for reliable event publishing. Use when implementing atomic writes with event delivery, ensuring exactly-once semantics, or building event-driven microservices.Architecture16
ddd-architecture-selectorfull-statck-skills/ddd-skillsArchitecture selection decision guide — help users choose from 5 DDD architectures (Layered/Onion/Hexagonal/Clean/COLA) with decision matrix, team size mapping, domain classification (core/generic/supporting), microservice splitting recommendation, and CQRS level suggestion. Use when user asks about architecture selection, 架构选型, COLA vs 六边形, cleaner architecture vs onion, 微服务拆分, or which architecture to use.Architecture15
architecturecarlheath/ogmiosArchitecture Specialist is your Technical Architect specializing in system design, architecture decisions, and strategic technical planning. This skill handles all architecture-related tasks from initial design through migration planning and technical debt assessment.Architecture14
aws-serverless-edacommandcodeai/agent-skillsAWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions, EventBridge, SQS, SNS, and serverless patterns. Essential when user mentions serverless, Lambda, API Gateway, event-driven, async processing, queues, pub/sub, or wants to build scalable serverless applications with AWS best practices.Architecture14
architecture-decision-recordariegoldkin/ai-agent-hubUse this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Helps teams maintain architectural memory and rationale for backend systems, API designs, database choices, and infrastructure decisions.Architecture14
init-agent-docstada5hi/skillsInitialize a project with AI agent documentation (CLAUDE.md, AGENTS.md, .agents/*.md). Use when the user asks to "init agent docs", "create Claude docs", "set up for AI coding", or when setting up a new repository for AI-assisted development.Architecture13
event-driven-patternsvibeeval/vibecosystemMessage queue patterns with BullMQ, Kafka, RabbitMQ - saga, outbox, dead letter queue, exactly-once semantics.Architecture11
loom-event-drivencosmix/loomEvent-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.Architecture11
event-driven-architecture-on-google-cloudecliptic-ai/architectureA short guide to one shape of application: a user submits data, a few steps run on it — often a Gemini call among them — and a result returns to the browser.Architecture10Other tasks
same rules, different job
