software-design-plugin
v1.2.0Software design methodology - deep modules, design by contract, GoF pattern selection, legacy code seams, and design by pseudocode
58 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Sep 15, 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 software-design-plugin for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install software-design-plugin@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/laurigates/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is software-design-plugin/.
Plugin files
├── .claude-plugin/plugin.json├── skills/design-by-contract/SKILL.md├── skills/design-deep-modules/SKILL.md├── skills/design-diy-vs-dependency/SKILL.md├── skills/design-legacy-seams/SKILL.md├── skills/design-patterns/SKILL.md└── skills/design-pseudocode/SKILL.md
Included Skills6
Design with explicit contracts — preconditions, postconditions, invariants, guard clauses. Use when designing a function/class, hardening a boundary, or adding assertions.
Judge interface depth — deep modules hide complexity behind small interfaces. Use when designing a module/API, reviewing a class boundary, or reducing complexity.
Evaluate a transparent DIY reimplementation before depending on a heavy single-purpose tool — GUI wrapper, bundled runtime, unaudited or non-cross-platform binary. Use when a task is about to install such a tool, or when auditing an existing dependency for removal.
Get legacy code under test before changing it — find seams, write characterization tests. Use when changing untested code, breaking dependencies, or taming legacy.
Select a design pattern from a symptom — strategy, observer, factory, adapter, decorator. Use when a structure resists change, or choosing between Gang-of-Four patterns.
Design a routine by stepwise refinement — pseudocode the intent before coding, then promote it to comments. Use when designing a complex function or non-trivial algorithm.
Plugin manifests1
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "software-design-plugin",
"version": "1.2.0",
"description": "Software design methodology - deep modules, design by contract, GoF pattern selection, legacy code seams, and design by pseudocode",
"keywords": [
"software-design",
"deep-modules",
"information-hiding",
"design-by-contract",
"preconditions",
"invariants",
"design-patterns",
"gang-of-four",
"legacy-code",
"characterization-tests",
"seams",
"pseudocode",
"stepwise-refinement"
]
}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.
[software-design-plugin on Agent Plugins Marketplace](https://pluginsmp.com/plugins/software-design-plugin)