Branded pattern collections: executable software design patterns as skill sets

[krisrowe]

Insight

Skills are executable patterns. A skill doesn't describe a pattern — it makes an agent apply it. This means echoskill can do what GoF, Fowler, and other pattern catalogs did, but as agent-executable collections rather than reference books.

What this looks like

A pattern collection is a curated set of skills that share a design philosophy. Examples:

• Refactoring Patterns — Fowler-style refactorings as skills. The agent identifies code smells and applies named refactorings (Extract Method, Replace Conditional with Polymorphism, etc.)
• Creational / Structural / Behavioral Patterns — GoF patterns as skills. The agent recognizes when code would benefit from Observer, Strategy, Factory, etc. and applies them.
• Anti-pattern Defense — skills that detect and remediate known anti-patterns (God Object, Spaghetti Code, Premature Abstraction)
• Domain-Driven Design — skills for bounded contexts, aggregates, value objects, domain events
• Clean Architecture — skills that enforce dependency rules, layer separation, port/adapter patterns
• Security Patterns — OWASP-informed skills that catch and fix common vulnerabilities

How collections work

A collection is:

1. A set of skills in the echoskill marketplace, grouped by a shared prefix or tag
2. A marketplace.json that curates the collection (the many-to-many curation model from echoskill#23)
3. A branded name and description (e.g., "echoskill/refactoring" or "echoskill/clean-arch")
4. Installable as a set: eskill install --collection refactoring

Individual skills within a collection are also installable standalone.

Why this matters

• GoF and Fowler patterns were prized because they codified expertise. Skills do the same but are executable — the agent doesn't just know the pattern, it applies it.
• Collections bring coherence. A random bag of skills is noise. A curated collection with a design philosophy is a product.
• Branding creates trust. "echoskill/refactoring" carries meaning the way "Gang of Four" did. Users install a collection because they trust the curation.
• Defense against anti-patterns is as valuable as pattern application. A collection that says "don't do this, do this instead" with automated detection is immediately useful.

Considerations

• Each skill in a collection must work standalone — no hidden dependencies between skills in a set
• Collections should be opinionated — that's the value. "Here's how WE think about refactoring" not "here's every possible approach"
• Start with one collection, get it right, then expand
• The identify-best-practices skill is already adjacent to this — it evaluates approaches against established practice. Pattern collections would be the established practice it evaluates against.

Related

• echoskill#23 — eskill CLI with marketplace curation model
• claude-coding-plugin#3 — product-design agent exploration
• The echoskill marketplace already has skill groupings (coding/, consulting/, prompting/) but these are organizational, not branded collections