system-design
v0.4.2System-level design: service boundaries on data ownership, scaling paths, cache placement, sync vs async integration and its failure modes, single points of failure, plus domain modeling (bounded contexts, aggregates, ubiquitous language) and an event-driven skill (delivery semantics, outbox, sagas, DLQ) — firing system-design, domain-modeling, and event-driven skills, a /system-design:review command, and a system-architect worker + system-design-reviewer pair. Complements code-architecture (code-level structure) without overlapping it.
By Ivan-WG1 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 5, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install system-design for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install system-design@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/galaykos/cc-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/system-design/.
Plugin files
├── .claude-plugin/plugin.json├── skills/domain-modeling/SKILL.md├── skills/event-driven/SKILL.md└── skills/system-design/SKILL.md
Included Skills3
Use when modeling a business domain — bounded contexts, ubiquitous language, entities vs value objects, aggregates and roots, domain events, context mapping. The DDD toolkit for domains that earn it, not CRUD.
Use when designing or reviewing message-driven architecture — brokers/queues, topics and partitions, event schema versioning, delivery semantics, outbox, sagas, dead-letter queues, consumer idempotency. In-process framework queues belong to the stack plugin.
Use when shaping system-level structure, before or during implementation — service boundaries, data ownership, scaling, caching, sync vs async integration, single points of failure. Code modules are code-architecture; the domain model is domain-modeling.
Plugin manifests1
{
"name": "system-design",
"version": "0.4.2",
"description": "System-level design: service boundaries on data ownership, scaling paths, cache placement, sync vs async integration and its failure modes, single points of failure, plus domain modeling (bounded contexts, aggregates, ubiquitous language) and an event-driven skill (delivery semantics, outbox, sagas, DLQ) — firing system-design, domain-modeling, and event-driven skills, a /system-design:review command, and a system-architect worker + system-design-reviewer pair. Complements code-architecture (code-level structure) without overlapping it.",
"author": {
"name": "Ivan-WG",
"email": "[email protected]"
},
"keywords": [
"process",
"review",
"worker"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[system-design on Agent Plugins Marketplace](https://pluginsmp.com/plugins/system-design)