claude

architecture-skills

Domain-driven design, vertical slices, service boundaries, event-driven systems, persistence, event sourcing, codebase design, and design review

9 on GitHubby Essam Almansouriv1.0.0updated 29 days ago
/

Plugin architecture-skills from marketplace my-skills in eralmansouri/skills. Commands read from the repo's manifest — 29 days ago.

What it installs

Skills (8)

  • codebase-design

    Use for code-level module design, deep modules, interfaces, seams, adapters, testability, refactoring shallow modules, and finding architecture improvements in an existing codebase.

  • design-review

    Design review of a codebase area, branch, or PR. Maps its bounded contexts, vertical slices, and modules, then judges where rules live and whether flexibility sits where change actually happens. Use when the user asks for a design or architecture review, or when a review should judge structure rathe

  • domain-driven-design

    Use for domain-driven design, domain modeling, ubiquitous language, bounded contexts, aggregates, invariants, entities, value objects, domain services, domain events, and deciding whether a rich domain model is warranted.

  • event-driven-systems

    Use for event-driven or message-driven architecture, commands and events, queues, pub/sub, Kafka, choreography, orchestration, sagas, outbox, idempotency, retries, ordering, backpressure, consumer lag, and messaging operations.

  • event-sourcing

    Use for event sourcing, event streams, event-sourced aggregates, business intent events, projections, replay, snapshots, optimistic stream concurrency, event schema evolution, and deciding whether event sourcing fits.

  • persistence-design

    Use for database and persistence design, data ownership, transaction boundaries, repositories, CQRS read models, query performance, optimistic concurrency, caching, projections, schema migrations, partitioning, and multi-tenancy.

  • service-boundaries

    Use for service boundaries, bounded capabilities, modular monoliths, microservices, monolith decomposition, data ownership, shared databases, API coupling, anti-corruption layers, and architecture topology decisions.

  • vertical-slice-architecture

    Use for vertical slice architecture, feature folders, task-based APIs and UI, CQRS commands and queries, handlers, request pipelines, controller design, code structure, cohesion, and feature-level testing.

View source on GitHub

Maintain architecture-skills?

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