From design-patterns
Find and compare reusable design patterns from a problem statement.
How this skill is triggered — by the user, by Claude, or both
Slash command
/design-patterns:pattern-finder [problem-statement]When to use
Use when the user describes a design force, smell, language constraint, integration flow, or architecture problem and needs a short pattern shortlist rather than a known pattern explanation.
[problem-statement]inheritThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to turn a problem statement into a short, practical pattern shortlist.
Use this skill to turn a problem statement into a short, practical pattern shortlist.
Start by identifying the forces in the user's request:
Lookup workflow:
patterns search "$ARGUMENTS" when the user names a pattern, force, or term.patterns list object-design --language <language> for object design problems or patterns list integration-design --language <language> for messaging and integration problems when the language is known.data/patterns before making a recommendation.Response shape:
Keep the shortlist tight. A good recommendation is usually one pattern, one backup, and one "do not use a pattern yet" option.
npx claudepluginhub bytedeskai/design-pattern-references --plugin design-patternsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.