Software Design Plugin

Software design methodology - deep modules, design by contract, GoF pattern selection, legacy code seams, and design by pseudocode

by @laurigates 6 skills

Install

npx skillmds@latest add plugin:laurigates/software-design-plugin

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 6 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install laurigates-software-design-plugin@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 6
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Design Patterns · laurigates bundle
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.

0 installs
▌
Design Pseudocode · laurigates
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.

0 installs
▌
Design By Contract · laurigates
Design with explicit contracts — preconditions, postconditions, invariants, guard clauses. Use when designing a function/class, hardening a boundary, or adding assertions.

0 installs
▌
Design Deep Modules · laurigates
Judge interface depth — deep modules hide complexity behind small interfaces. Use when designing a module/API, reviewing a class boundary, or reducing complexity.

0 installs
▌
Design Legacy Seams · laurigates
Get legacy code under test before changing it — find seams, write characterization tests. Use when changing untested code, breaking dependencies, or taming legacy.

0 installs
▌
Design Diy Vs Dependency · laurigates
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.

0 installs