jh3ady/claude-plugins

Clean code craftsmanship applied pragmatically: naming, small focused functions, intent-revealing comments, and disciplined error handling. Composable with your own conventions.

The gitmoji + Conventional Commits standard for commit messages: subject-based scopes, the 50/72 rule, and lower-case-verb casing. Composable with your own conventions.

Command Query Responsibility Segregation applied pragmatically: the command/query split promoted to the model level, command and query handlers, the write model versus read models and projections, the levels of separation from a shared store to separate stores, the consistency trade-off, and the relationship to CQS, event sourcing, and domain-driven design. Composable with your own conventions.

Dependency injection applied pragmatically: Pure DI (manual constructor injection) first, the composition root, object lifetimes, and the anti-pattern catalogue, with DI containers referenced as a justified option. Composable with your own conventions.

Domain-driven design applied pragmatically, in three skills: EventStorming (collaborative domain discovery, the three formats, the orange-sticky notation), strategic design (ubiquitous language, bounded contexts, subdomains, context mapping), and tactical design (entities, value objects, aggregates, domain events, repositories, domain services, factories), with TypeScript specifics. Composable with your own conventions.

Event sourcing applied pragmatically: an append-only event store as the system of record, event-sourced aggregates rehydrated by replaying their events, snapshots, projections and read models, schema versioning and upcasting, idempotency, and the relationship to CQRS and domain-driven design. Composable with your own conventions.

Hexagonal architecture (ports and adapters) applied pragmatically: the dependency rule, primary and secondary ports and adapters, the application core, composition-root wiring, and its relationship to Onion and Clean Architecture, with TypeScript specifics. Composable with your own conventions.

The modular monolith applied pragmatically: one deployable unit, strictly bounded modules with public APIs, isolated data, and TypeScript-ecosystem boundary enforcement. Composable with your own conventions.

The Conventional Comments standard for pull and merge request reviews: labelled, decorated, actionable comments. Composable with your own conventions.

The simplicity cluster KISS, DRY, and YAGNI applied pragmatically: do-less heuristics, the rule of three, and the trade-offs such as duplication versus the wrong abstraction. Composable with your own conventions.

The five SOLID principles applied pragmatically: recognizable smells, focused refactorings, and guardrails against speculative abstraction. Composable with your own conventions.

Symfony's HTTP layer applied pragmatically, in three skills: the HttpKernel request-to-response lifecycle and its events, routing and URL generation, and thin controllers with value resolvers. Framework-faithful and architecture-agnostic. Composable with your own conventions.

Doctrine persistence in Symfony applied pragmatically, in three skills: the Doctrine ORM (mapping, associations, repositories, the unit of work, the N+1 pitfall, lifecycle events), the DBAL layer beneath it (the connection, the query builder, custom types and platforms), and database migrations (the schema lifecycle and schema strategy). Framework-faithful and architecture-agnostic. Composable with your own conventions.