skills.rest
joleques
jolequesCOMMUNITY
Explore all skills by this author →
GitHub

design-patterns-specialist

Identify GoF design pattern applicability in Go codebases for reviews and refactoring.

Updated Apr 5, 2026
Search Tags:#refactoring#simplicity#design-patterns#pragmatic#code-design#GoF#pattern-usage
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill design-patterns-specialist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-patterns-specialist
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/design-patterns
Command: npx skills add https://github.com/joleques/northstar-ai --skill design-patterns-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides pragmatic guidance on when to apply or avoid GoF design patterns, helping developers prevent over-engineering and maintain code simplicity.

Core Features & Use Cases

  • Analyzes GoF creational, structural, and behavioral patterns to determine necessity.
  • Delivers actionable recommendations for applying or omitting patterns based on real-world scenarios.
  • Refers to related knowledge (e.g., GRASP) and supports code reviews, refactoring decisions, and architecture guidance.

Quick Start

Assess a GoF pattern usage in a codebase and provide a pragmatic recommendation on whether to apply, simplify, or avoid it.

Frequently Asked Questions about design-patterns-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I apply GoF design patterns to my Go codebase?▼

Apply GoF design patterns during code reviews or refactoring when they demonstrably simplify code and satisfy practical usage criteria. Pragmatic guidance helps determine necessity by analyzing creational, structural, and behavioral patterns against real-world scenarios to prevent over-engineering.

How do I know if a design pattern is over-engineering my code?▼

A design pattern is over-engineering if it violates simplicity and fails practical usage criteria. Pragmatic pattern analysis evaluates whether applying or omitting patterns maintains code simplicity, providing actionable recommendations to simplify or avoid unnecessary implementations during refactoring.

What is the best way to evaluate design pattern usage during code review?▼

Evaluate design pattern usage in code review by assessing necessity against pragmatic criteria and anti-pattern avoidance guidelines. This approach delivers actionable recommendations on whether to apply, simplify, or omit patterns based on real-world scenarios and architectural goals.

Does this approach to design patterns work with GRASP principles?▼

Yes, pragmatic design pattern evaluation refers to related knowledge like GRASP principles. It analyzes pattern necessity alongside GRASP to support refactoring decisions and architectural guidance, ensuring pattern usage aligns with broader code design objectives.

When should I avoid applying GoF creational and structural patterns?▼

Avoid applying GoF creational and structural patterns when they introduce unnecessary complexity and fail practical usage criteria. Pragmatic guidance helps identify anti-patterns, recommending omission or simplification to maintain code simplicity over rigid pattern adherence.

Related Skills

Explore More Software Engineering Skills→
deepeshBodhdeepeshBodh
35

analysis-codebase

Analyze codebases to extract tech stack, patterns, and collision risks.

Community
Advanced
markpittmarkpitt
22

markdown-formatter

Formats Markdown documents to enforce consistent style and structure.

Community
Intermediate
huaxelhuaxel

software-design-principles

Analyzes code against YAGNI, DRY, KISS, SOLID, GRASP, and GoF design principles.

Community
Intermediate
CarbonTailsCarbonTails

karpathy-guidelines

Enforce coding guidelines for clarity, simplicity, and goal-driven execution.

Official
Advanced