From billy-milligan
System design patterns for distributed systems: monolith vs microservices decision, modular monolith, event-driven, strangler fig, CQRS, cell-based architecture. Use when choosing architecture, scaling systems, decomposing services.
npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganThis skill is limited to using the following tools:
- Choosing between monolith, modular monolith, and microservices
Adapts content for unique crossposting to X, LinkedIn, Threads, and Bluesky using platform constraints and voice preservation. For multi-platform launches, essays, or announcements.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Assists writing, fixing, configuring C++ tests with GoogleTest/GoogleMock and CMake/CTest. Diagnoses flaky tests, failures, and adds coverage/sanitizers.
Load these on demand — ONLY when the specific subtopic is being discussed:
references/monolith-vs-microservices.md — decision matrix with team size/traffic thresholds, when to splitreferences/modular-monolith.md — module structure, inter-module communication, import rulesreferences/event-driven-patterns.md — outbox pattern, idempotent consumers, saga, DLQ, schema versioningreferences/strangler-fig-migration.md — phased migration from legacy, facade rules, timelinereferences/scaling-reference.md — concrete numbers: RPM thresholds, cell-based architecture, CQRS triggersscripts/detect-architecture.sh — analyzes project structure to identify current architectural patternassets/architecture-review-checklist.md — reusable checklist for reviewing system design decisions