Architecture skills for AI coding agents
Skills for software architecture, patterns, and system design. Each skill is a packaged set of instructions you install into Cursor, Claude Code, GitHub Copilot, Windsurf or any other supported agent, so the agent follows the same workflow every time.
14 skills in this category.
Skills in Architecture
Finds duplicate business logic spread across multiple components and suggests consolidation.
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level.
Maps architectural components in a codebase and measures their size to identify what should be extracted first.
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design".
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications.
Groups existing components into logical business domains to plan service-based architecture.
Guides design and implementation of evolutionary modular-monolith platforms with DDD (strategic + tactical), flat-by-aggregate organization, an Anti-Corruption Layer for vendor independence, a transactional outbox for events, smart resilience (backoff with jitter, circuit breakers, idempotency), and a polished architecture HTML document with elegant SVG diagrams.
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity.
Use when planning legacy system migrations, codebase modernization, monolith decomposition, microservices consolidation, cross-language rewrites, or framework upgrades. Invoke for strangler fig pattern, incremental migration strategy, or refactoring roadmaps. Do NOT use for domain analysis (use domain-analysis), component sizing (use component-identification-sizing), or step-by-step decomposition plans (use decomposition-planning-roadmap).
Runs a sequenced monolith-to-modular pipeline that sizes and inventories components, finds shared domain duplication, addresses flattening and hierarchy issues, analyzes coupling, then groups components into candidate domain-aligned units, with optional embedded DDD strategic analysis for bounded contexts.
Technology-agnostic guidance for modular systems: bounded contexts, clear boundaries, composability, state isolation, explicit contracts, failure containment, scaffolding workflows, split/merge criteria, sub-units inside a context, and compliance review signals.
React composition patterns that scale.
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design.
Detects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Services, Domain Events).