Domain-Driven Design — Pragmatic Laravel

Restructure Laravel applications into domain-based organisation. Business objectives first — increase revenue, reduce OPEX, ship faster. Not academic DDD, but practical domain separation that your team can maintain.

Philosophy

"Kita orang meniaga nak increase sales, kurangkan OPEX. Bukan nak berfilasuf pasal kod."

This skill applies DDD where it creates real business value:

• Clear ownership — each domain maps to a business capability, team knows what they own
• Independent velocity — domains can evolve without breaking each other
• Reduced OPEX — less accidental complexity, faster onboarding, fewer cross-cutting bugs
• Business alignment — code structure mirrors how the business actually works

Command Reference