skills.rest
mopeyjellyfish
mopeyjellyfishCOMMUNITY
Explore all skills by this author →
GitHub

pattern-recognition

Identify existing repository patterns and recommend reuse, extension, or new patterns.

1|Updated Apr 18, 2026
Search Tags:#architecture#code-quality#domain-driven-design#pattern-recognition#design-decision#repo-patterns#pattern-families
One-click install
npx skills add https://github.com/mopeyjellyfish/flywheel --skill pattern-recognition-mopeyjellyfish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pattern-recognition
Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/pattern-recognition
Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill pattern-recognition-mopeyjellyfish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams decide when existing repo patterns fit a given problem and when to reuse, extend, or introduce new patterns, grounding decisions in the actual repo truth.

Core Features & Use Cases

  • Ground current truth to identify existing pattern families and boundaries.
  • Map problems to named pattern families or anti-patterns with concrete trade-offs.
  • Provide actionable recommendations (reuse, extend, net-new, or stay local) and guardrails for verification.

Quick Start

Describe the pattern question and invoke $fw:pattern-recognition to map the repo to patterns and decide the best approach.

Frequently Asked Questions about pattern-recognition

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

FAQPage Schema
How do I decide whether to reuse an existing repository pattern or create a new one?▼

Repository pattern recognition evaluates your codebase's current architectural boundaries against the specific problem to recommend reuse, extension, net-new implementation, or staying local.

What is the best way to map a new feature request to existing domain-driven design boundaries?▼

Mapping features to domain-driven design boundaries involves identifying existing pattern families in your repo, evaluating trade-offs, and providing actionable recommendations with guardrails for verification.

When should I introduce a new architectural pattern instead of extending DTOs or builders?▼

Introducing a new architectural pattern is warranted when existing DTOs, repositories, ports, or builders cannot fit the problem, requiring a net-new pattern with defined guardrails rather than extending current designs.

Does pattern recognition work with domain-driven design and port patterns?▼

Yes, pattern recognition explicitly scopes domain-driven design, ports, DTOs, repositories, and builders to ground decisions in the actual repo truth and determine architectural fit.

How to identify anti-patterns when planning a codebase extension?▼

Identify anti-patterns during codebase extension by mapping the problem to named pattern families, evaluating concrete trade-offs, and verifying if existing architectural boundaries fit the new requirements.

What are the limitations of extending existing repo patterns for new features?▼

Extending existing repo patterns risks violating architectural boundaries if the problem requires a net-new pattern; guardrails and verification hooks are provided to prevent misaligned design decisions.

Related Skills

Explore More Software Engineering Skills→
petrSimonidesXartpetrSimonidesXart

codebase-scan

Generate a codebase tree and key files list from a repository.

Community
Intermediate
wpankwpank
11

architecture-patterns

Explain backend architectural patterns with Python code examples.

Community
Advanced
haginothaginot

architecture-guardian

Validate TypeScript layer dependencies and report import violations.

Community
Advanced
verselesverseles
179

desloppify

Scan codebases across 28 languages for technical debt metrics.

Official
Advanced