This is a routing layer that helps you decide whether Domain-Driven Design is worth the complexity, then points you to the right specialist skill for strategic modeling, tactical patterns, or event-driven architecture. It starts with a viability checklist (complex rules, team collisions, unstable contracts), produces artifacts like bounded contexts and glossaries, then hands off to skills like ddd-strategic-design, cqrs-implementation, or saga-orchestration. The honest take is that this prevents you from cargo-culting DDD onto simple CRUD apps while giving you a clear path when the domain actually justifies it. It won't replace real workshops with domain experts, but it will keep you from skipping steps or over-engineering.
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill domain-driven-design