Design Patterns¶
Workflow¶
- Identify the repeated problem and the actual consumers before choosing a pattern.
- Compare a direct function or module with the proposed abstraction.
- Apply the smallest useful form and keep ownership and dependencies obvious.
- Test substitution and behavior; remove the abstraction if it adds indirection without a demonstrated benefit.
Completion¶
Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.
Focused references¶
- Detailed examples: load only the section relevant to the task.
Canonical source: skills/software-engineering/design-patterns.md.