claude

ddd

Domain-driven design commands: analyze codebases and recommend applications of DDD tactical patterns, supple design, and hexagonal (ports-and-adapters) architecture.

1 on GitHubby Rafael Azevedov0.3.0updated 5 months ago
/

Plugin ddd from marketplace rafael-ddd in RPAzevedo/DDD-Plugin. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (6)

  • hexagonal-architecture-review

    Analyzes a codebase and recommends applications of hexagonal (ports-and-adapters) architecture, read pragmatically: the database is treated as an integral part of the domain model, and ports are reserved for genuinely variable external systems. Use when reviewing whether framework code has bled into

  • hexagonal-architecture

    Alistair Cockburn's hexagonal (ports-and-adapters) architecture, read pragmatically: the database is treated as an integral part of the domain model, and ports are reserved for genuinely variable external systems. Use when reviewing where framework code has bled into the domain core, whether control

  • supple-design-review

    Analyzes a codebase and recommends applications of Eric Evans' supple design patterns. Use when reviewing a domain model for clarity, expressiveness, and ease of change; identifying where intention-revealing interfaces, side-effect-free functions, assertions, conceptual contours, standalone classes,

  • supple-design

    Eric Evans' supple design patterns (Domain-Driven Design, Ch. 10). Use when reviewing code for domain-model clarity, designing value objects, assessing whether operations compose cleanly, or reasoning about intention-revealing interfaces, side-effect-free functions, assertions, conceptual contours,

  • tactical-patterns-review

    Analyzes a codebase and recommends applications of Eric Evans' DDD tactical patterns. Use when reviewing a domain model for proper aggregate boundaries, entity vs. value object separation, domain event design, domain service responsibilities, repository contracts, factory usage, or module structure

  • tactical-patterns

    Eric Evans' DDD tactical patterns (Domain-Driven Design, Chs. 5–6): Value Object, Entity, Aggregate, Domain Event, Domain Service, Repository, Factory, Module. Use when reviewing aggregate boundaries, distinguishing entities from value objects, identifying missing domain events, evaluating repositor

View source on GitHub

Maintain ddd?

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.

claude & codex pluginslisted