Stats
Actions
Available In
Tags
Plugin
coding
Guides large-scale feature implementation and codebase maintenance by applying systematic software design (DDD, Clean Architecture, GoF patterns), safe refactoring, test-driven development, security threat modeling, and a spec-to-implementation roadmap tracker.
What's Inside
Slash Commands5
fix
/fix
Fix bugs by diagnosing root cause, reproducing with tests, and applying minimal fixes.
refactor
/refactor
Clean up legacy code issues by identifying code smells and applying safe refactoring techniques.
--deep scans the entire target scope holistically, not just recent diffs
/review
The `<execute name="main">ARGUMENTS</execute>` is entry point for this command.
--deep only applies to init and update, ignored for status
/roadmap
The `<execute name="main">ARGUMENTS</execute>` is entry point for this command.
write
/write
Implement features based on the agent skills.
Skills9
architecture
/architecture
Plan how a system is structured — which layers, modules, or contexts exist and how code is laid out — driven by the forces at play, not by a fixed pattern. The default is to add no extra structure; structure is introduced only when complexity calls for it, and the chosen shape (Clean Architecture, DDD, DCI, or another) is judged in the moment. Use this skill when following a recorded structure in docs/architecture.md, or when deciding the structural shape for a non-trivial feature, a new module, or a restructuring — especially after a design-forces memo recommends a layered or partitioned structure.
design-forces
/design-forces
Surface design forces and lay out the option space — including framework defaults, scaffolds, and deferring — before committing to Clean Architecture, DDD, or any heavier pattern. Produces a Design Analysis Memo at the start of /write, /refactor, or non-trivial /fix. Make sure to use this skill whenever the user starts a non-trivial feature, restructures code, or asks "do we really need Clean Architecture / DDD / pattern X here".
design-patterns
/design-patterns
Select and apply GoF design patterns: Factory, Builder, Strategy, Observer, Adapter, Decorator. Use when solving recurring design problems or structuring multi-component changes. Make sure to use this skill whenever the user needs to decouple components, wrap legacy APIs, handle multiple algorithm variants, build complex objects step by step, or asks which pattern fits their situation.
domain-modeling
/domain-modeling
Model business domains using DDD patterns: Entity, Value Object, Aggregate, Domain Event. Use when implementing business logic, defining domain concepts, or designing aggregate boundaries. Make sure to use this skill whenever the user works on business rules, creates domain objects, discusses bounded contexts, models workflows or processes, or asks about entity vs value object distinctions — even for simple CRUD features that involve domain invariants.
principles
/principles
Apply SOLID, KISS, DRY, YAGNI principles to code design decisions. Use when building new features from scratch and need to decide on class structure, interface boundaries, or dependency direction. Make sure to use this skill when the user faces design trade-offs, asks about SOLID principles, debates whether to abstract or keep things simple, or needs to evaluate competing design approaches — but not for code smell detection (use refactoring skill instead).
The plugin manifest points to a different repository than the source indexed by ClaudePluginHub.
Stats
Version0.8.1
Released
Stars5
MaintenanceExcellent
LicenseApache-2.0
Last Commit
Added
Available In
Tags
