System Design
Skill ActiveDesign 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.
Design complex systems, services, and architectures, aiding users in making informed decisions about API contracts, data modeling, and service boundaries.
Features
- System and service architecture design
- API contract and data model design
- Evaluation of non-functional requirements
- Trade-off analysis for architectural decisions
- Structured design document generation
Use Cases
- When needing to design a new system or service.
- When evaluating architectural decisions and trade-offs.
- When requiring assistance with API design or data modeling.
- When needing help defining service boundaries and non-functional requirements.
Non-Goals
- Implementing or coding the system.
- Providing detailed low-level code implementation.
- Managing project timelines or team resources.
Trust
- warning:Issues AttentionThere are 29 open issues and 4 closed issues in the last 90 days, indicating a low closure rate and potentially slow maintainer response.
Installation
First, add the marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install engineering@knowledge-work-pluginsQuality Score
Trust Signals
Similar Extensions
Backend Api Design
99Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.
System Design
99Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
Design Serialization Schema
97Design serialization schemas using JSON Schema, Protocol Buffer definitions, or Apache Avro. Covers schema versioning, backwards compatibility, validation rules, and evolution strategies for long-lived data formats. Use when defining a new API contract or data interchange format, adding fields to an existing schema without breaking consumers, migrating between schema versions, choosing between schema systems, or documenting data validation rules for automated enforcement.
Sdk Dx
100Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
Pathfinder
100Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.