Skip to content

fix: enforce domain-only business rules #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bnymn merged 1 commit into from
Jun 21, 2026
Merged

fix: enforce domain-only business rules #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion plugins/engineering-playbook/skills/coding-standards/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,11 @@ Follow hexagonal architecture as the baseline.

- Organize each business module in `src` as `Domain`, `Application`, and `Infrastructure`;
dependencies point inward only.
- Put all business rules and decisions in `Domain`.
- Before writing or reviewing any conditional, validation, state transition,
calculation, policy, or workflow decision, ask: "Is this a business rule?"
- If the answer is yes, put it in `Domain`. This is a hard requirement: business
rules must never live in `Application`, `Infrastructure`, framework code,
adapters, controllers, jobs, requests, commands, listeners, or UI glue.
- Use `Application` only for use-case orchestration, transaction boundaries,
authorization handoff, domain calls, ports, and input/output mapping.
- Use `Infrastructure` only for adapters such as persistence, queues, HTTP
Expand Down