How do I install the Elct9620 AI Coding Skills Design Patterns skill?

Run npx skillmds@latest add tomevault-io/elct9620-ai-coding-skills-design-patterns in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Elct9620 AI Coding Skills Design Patterns skill do?

Related Skills It is listed under Coding & Dev Tools on SkillMD.

Is Elct9620 AI Coding Skills Design Patterns safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Elct9620 AI Coding Skills Design Patterns?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Elct9620 AI Coding Skills Design Patterns free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Elct9620 AI Coding Skills Design Patterns?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Elct9620 AI Coding Skills Design Patterns by tomevault-io

Name: Elct9620 AI Coding Skills Design Patterns
Author: tomevault-io

File contents

Related Skills

Modeling business concepts (Entity, Value Object)? → Use domain-modeling instead
Restructuring existing code toward a pattern? → Use refactoring for safe migration steps
Deciding if a pattern is even needed (YAGNI)? → Use principles to evaluate first

Applicability Rubric

Condition	Pass	Fail
Multi-component change	Feature affects multiple components	Single component change
Recognizable problem	Matches known design problem	Unique/novel problem
Flexibility needed	Requires extensible solution	Fixed requirements
Recurring challenge	Solving common design issue	One-off implementation

Apply when: Any condition passes

Core Principles

Pattern Selection Process

1. Identify the problem
   ↓
2. Match problem to pattern category
   ↓
3. Evaluate pattern candidates
   ↓
4. Consider trade-offs
   ↓
5. Apply pattern minimally

Pattern Categories

Category	Purpose	Common Patterns
Creational	Object creation	Factory, Builder, Singleton
Structural	Object composition	Adapter, Decorator, Facade
Behavioral	Object interaction	Strategy, Observer, Command

Pattern Quick Reference

Category	Pattern	Use When	Example
Creational	Factory Method	Object creation varies by context	`createLogger(type)`
Creational	Builder	Complex object with many optional parts	Fluent configuration
Creational	Singleton	Single instance needed globally	Configuration manager
Structural	Adapter	Interface incompatibility	Wrap legacy API
Structural	Decorator	Add behavior dynamically	Logging wrapper
Structural	Facade	Simplify complex subsystem	Unified API client
Structural	Composite	Tree structures	UI components
Behavioral	Strategy	Algorithm varies at runtime	Payment methods
Behavioral	Observer	One-to-many notifications	Event system
Behavioral	Command	Encapsulate operations	Undo/redo actions
Behavioral	State	Behavior changes with state	Order status

Completion Rubric

Before Applying

Criterion	Pass	Fail
Problem identification	Problem clearly defined	Vague problem statement
Real need	Solves actual problem	Hypothetical/speculative
Simpler alternatives	Considered simpler options first	Jumped to pattern
Team familiarity	Team understands pattern	Pattern is obscure

During Implementation

Criterion	Pass	Fail
Minimal application	Pattern applied minimally	Over-applied
Clear naming	Names reflect pattern intent	Generic/unclear names
Intent preservation	Pattern intent maintained	Pattern misused
Appropriate complexity	Complexity justified	Over-engineered

After Implementation

Criterion	Pass	Fail
Flexibility gained	Code more flexible	Same or less flexible
Documented	Pattern documented if not obvious	Undocumented complexity
Tested	Tests cover pattern behavior	Pattern untested

Anti-Pattern Warning

Pattern Fever: Applying patterns everywhere

Signs:

Patterns for trivial problems
Multiple patterns where one suffices
Code harder to understand than before

Cure: YAGNI - Use patterns only when they solve real problems

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: elct9620-ai-coding-skills-design-patternsdescription: Related Skills---## Related Skills- Modeling business concepts (Entity, Value Object)? → Use **domain-modeling** instead- Restructuring existing code toward a pattern? → Use **refactoring** for safe migration steps- Deciding if a pattern is even needed (YAGNI)? → Use **principles** to evaluate first## Applicability Rubric| Condition | Pass | Fail ||-----------|------|------|| Multi-component change | Feature affects multiple components | Single component change || Recognizable problem | Matches known design problem | Unique/novel problem || Flexibility needed | Requires extensible solution | Fixed requirements || Recurring challenge | Solving common design issue | One-off implementation |**Apply when**: Any condition passes## Core Principles### Pattern Selection Process```1. Identify the problem ↓2. Match problem to pattern category ↓3. Evaluate pattern candidates ↓4. Consider trade-offs ↓5. Apply pattern minimally```### Pattern Categories| Category | Purpose | Common Patterns ||----------|---------|-----------------|| Creational | Object creation | Factory, Builder, Singleton || Structural | Object composition | Adapter, Decorator, Facade || Behavioral | Object interaction | Strategy, Observer, Command |## Pattern Quick Reference| Category | Pattern | Use When | Example ||----------|---------|----------|---------|| Creational | Factory Method | Object creation varies by context | `createLogger(type)` || Creational | Builder | Complex object with many optional parts | Fluent configuration || Creational | Singleton | Single instance needed globally | Configuration manager || Structural | Adapter | Interface incompatibility | Wrap legacy API || Structural | Decorator | Add behavior dynamically | Logging wrapper || Structural | Facade | Simplify complex subsystem | Unified API client || Structural | Composite | Tree structures | UI components || Behavioral | Strategy | Algorithm varies at runtime | Payment methods || Behavioral | Observer | One-to-many notifications | Event system || Behavioral | Command | Encapsulate operations | Undo/redo actions || Behavioral | State | Behavior changes with state | Order status |## Completion Rubric### Before Applying| Criterion | Pass | Fail ||-----------|------|------|| Problem identification | Problem clearly defined | Vague problem statement || Real need | Solves actual problem | Hypothetical/speculative || Simpler alternatives | Considered simpler options first | Jumped to pattern || Team familiarity | Team understands pattern | Pattern is obscure |### During Implementation| Criterion | Pass | Fail ||-----------|------|------|| Minimal application | Pattern applied minimally | Over-applied || Clear naming | Names reflect pattern intent | Generic/unclear names || Intent preservation | Pattern intent maintained | Pattern misused || Appropriate complexity | Complexity justified | Over-engineered |### After Implementation| Criterion | Pass | Fail ||-----------|------|------|| Flexibility gained | Code more flexible | Same or less flexible || Documented | Pattern documented if not obvious | Undocumented complexity || Tested | Tests cover pattern behavior | Pattern untested |## Anti-Pattern Warning**Pattern Fever**: Applying patterns everywhereSigns:- Patterns for trivial problems- Multiple patterns where one suffices- Code harder to understand than beforeCure: YAGNI - Use patterns only when they solve real problems---> Converted and distributed by [TomeVault](https://tomevault.io/claim/elct9620) — claim your Tome and manage your conversions.

Frequently asked questions

Elct9620 AI Coding Skills Design Patterns