19 architecture skills from Fundamentals of Software Architecture by Mark Richards & Neal Ford
19 skills · hooks
15 design pattern skills from Design Patterns: Elements of Reusable Object-Oriented Software
Plugin design-patterns-gof from marketplace bookforge-skills in bookforge-ai/bookforge-skills. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
abstract-factory-implementorImplement the Abstract Factory pattern to create families of related objects without specifying their concrete classes. Use when a system must be independent of how its products are created, when it must work with multiple product families, when products are designed to be used together and you need
behavioral-pattern-selectorChoose the right behavioral design pattern from the 11 GoF behavioral patterns. Use when someone asks "how do I make this algorithm swappable?", "should I use Strategy or State?", "how do I decouple senders from receivers?", "what's the difference between Observer and Mediator?", "how do I add undo/
bridge-pattern-implementorImplement the Bridge pattern to decouple an abstraction from its implementation so both can vary independently. Use when you want to avoid a permanent binding between abstraction and implementation, when both abstractions and implementations should be extensible by subclassing, when implementation c
command-pattern-implementorImplement the Command pattern to encapsulate requests as objects, enabling parameterized operations, queuing, logging, and undo/redo. Use when you need to decouple UI elements from operations, implement multi-level undo with command history, support macro recording, queue or schedule requests, or lo
composite-pattern-implementorImplement the Composite pattern to compose objects into tree structures representing part-whole hierarchies, letting clients treat individual objects and compositions uniformly. Use when building file systems, UI component trees, organization charts, document structures, or any recursive containment
creational-pattern-selectorChoose the right creational design pattern (Abstract Factory, Builder, Factory Method, Prototype, or Singleton) for an object creation problem. Use when someone asks "which factory pattern should I use?", "should I use Abstract Factory or Factory Method?", "how do I create objects without specifying
decorator-pattern-implementorImplement the Decorator pattern to attach additional responsibilities to objects dynamically, providing a flexible alternative to subclassing. Use when you need to add behaviors like logging, caching, validation, authentication, compression, or UI embellishments without creating a subclass for every
design-pattern-selectorSelect the right GoF design pattern for a specific object-oriented design problem. Use when facing any of these situations: object creation inflexibility (too many concrete class references), tight coupling between classes, subclass explosion from trying to extend behavior, inability to modify a cla
multi-pattern-system-designerDesign a system using multiple coordinated design patterns, moving beyond single-pattern application to pattern composition. Use when facing a complex system with multiple design problems — object creation inflexibility, structural rigidity, and behavioral coupling occurring simultaneously. Guides t
observer-pattern-implementorImplement the Observer pattern to establish one-to-many dependencies where changing one object automatically notifies and updates all dependents. Use when a spreadsheet model needs to update multiple chart views, when UI components must react to data changes, when event systems need publish-subscrib
oo-design-principle-evaluatorEvaluate object-oriented designs against the two foundational GoF principles: 'Program to an interface, not an implementation' and 'Favor object composition over class inheritance.' Use when reviewing class hierarchies, assessing reuse strategies, or deciding between inheritance and composition for
oo-design-smell-detectorDetect common OO design smells in a codebase and recommend corrective design patterns. Use when reviewing code for design quality, investigating why changes are difficult, or auditing coupling and inheritance depth. Scans for 8 categories of design fragility — hardcoded object creation, operation de
strategy-pattern-implementorImplement the Strategy pattern to encapsulate a family of interchangeable algorithms behind a common interface. Use when you have multiple conditional branches selecting between algorithm variants, when algorithms need different space-time trade-offs, when a class has multiple behaviors expressed as
structural-pattern-selectorChoose the right structural design pattern (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, or Proxy) for a structural design problem. Use when you need to adapt interfaces between incompatible classes, decouple an abstraction from its implementation so both can vary independently, build p
visitor-pattern-implementorImplement the Visitor pattern to define new operations on an object structure without changing the classes of the elements it operates on. Use when you have a stable class hierarchy but frequently add new operations, when many unrelated operations need to be performed on an object structure, or when
"${CLAUDE_PLUGIN_ROOT}/hooks/session-start"
19 architecture skills from Fundamentals of Software Architecture by Mark Richards & Neal Ford
19 skills · hooks
16 skills for enterprise application architecture: pattern-family selectors, pattern implementers, and audit skills — extracted from Patterns of Enterprise Application Architecture by Martin Fowler.
16 skills · hooks
16 legacy code skills from Working Effectively with Legacy Code by Michael C. Feathers — the Legacy Code Change Algorithm, seam type selection, characterization test writing, dependency-breaking techniques, monster method decomposition, big class extraction, and more
16 skills · hooks
14 agent skills for building secure and reliable systems — threat modeling, secure design, least-privilege access, blast radius containment, code review, deployment pipelines, incident response, and disaster recovery. From Building Secure and Reliable Systems by Adkins, Beyer, Blankinship, Lewandowski, Oprea, Stubblefield.
14 skills · hooks
14 data systems skills from Designing Data-Intensive Applications by Martin Kleppmann
14 skills · hooks
14 skills for outbound prospecting, pipeline filling, and sales conversation opening, extracted from Fanatical Prospecting by Jeb Blount
14 skills · hooks
ADK software engineer for creating production-ready Agent Development Kit agents with clean structure, testability, safe tool usage, and deployment automation
1 skill
Twelve FSE-specific skills for the ACM Foundations of Software Engineering conference and its PACMSE journal-style publication model, grounded in the FSE 2026/2027 researchr calls, PACMSE journal pages, ACM Digital Library, and dblp.
12 skills
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field symbols, data references, exception handling, or ABAP unit testing. Covers both classic ABAP and modern ABAP for Cloud Development patterns.
1 skill · 1 command
Run Specification, Pseudocode, Architecture, Refinement, and Completion as a deterministic, resumable workflow with immutable evidence and traceable phase gates.
3 skills · 1 MCP server
Use when you need to review, improve, or refactor Java code for object-oriented design quality — including applying SOLID, DRY, and YAGNI principles, improving class and interface design, fixing OOP concept misuse (encapsulation, inheritance, polymorphism), identifying and resolving code smells (God Class, Feature Envy, Data Clumps), or improving object creation patterns, method design, and exception handling.
1 skill
19 software engineering skills from Code Complete, APOSD, GoF, and Clean Architecture, driving a research → plan → build workflow: a quiet build loop that asks only at one-way doors, batched cross-phase review on a configurable cadence by a single sonnet reviewer, wave-parallel phase execution in isolated worktrees, and orchestrated per-phase commits.
22 skills · 4 commands · 2 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.