gof-design-patterns
SKILL.md
GoF Design Patterns
Goal
- Choose the simplest design that solves the real change pressure.
- Select one primary pattern (two only if responsibilities are clearly split).
- Keep recommendations language-agnostic and explicit about tradeoffs.
- Support coding tasks with pattern-aligned implementation guidance.
Simple Workflow
- Capture context with three questions: what changes often, what hurts now, and which constraint dominates.
- Shortlist up to three candidates using
references/DECISION_FRAMEWORK.md(canonical source). Usereferences/CATALOG.mdonly for quick intent lookup. - Select one pattern (or
do not use a pattern) based on future change-cost reduction and lower indirection. - If the task includes code changes, always read both:
references/pattern-<selected-pattern>.mdscripts/<selected-pattern>.ts(illustrative reference only)
- Apply the design incrementally, adapted to the project language and constraints.
- Validate with
references/PITFALLS.md, then run a final quality/activation self-check withreferences/TESTS.md, and format the answer withreferences/OUTPUT_TEMPLATES.md.
Core Rules
- Language first: choose by problem forces and context, not by language syntax.
- Simplicity first: if recurring change pressure is weak, explicitly recommend
do not use a pattern. - Script policy: scripts are examples to read and adapt, not mandatory to execute.
Output Contract
- Always provide an explicit decision.
- Always include one simpler alternative and why it was rejected.
- Always include tradeoffs (
ProsandCons). - If code is shown, include a short adaptation note for other languages.
Navigation
Core References
Pattern Cards
Weekly Installs
3
Repository
fede0089/agents-skillsFirst Seen
Feb 22, 2026
Security Audits
Installed on
amp3
github-copilot3
codex3
kimi-cli3
gemini-cli3
cursor3