labrodev-corelisted

# Labrodev Core — structure, boundaries, headers, immutability Part of the Labrodev playbook. **The law for this skill lives in the always-on `labrodev-core` guideline** (philosophy, structure, dependency law, golden paths, global code rules, anti-patterns, legacy zones) — this skill holds the craft: structure detail, canonical header templates, and edge cases. Per-file checks are folded into each component's rule file under `rules/`. ## Project structure (canonical) Logical layout. Physically, Core often lives in a separate Composer package checked out next to the app (e.g. `../core/src/Domain/...`) — check `composer.json`. All rules apply to the logical module regardless of physical location. ``` src/Core/ ├── Domain/{Domain}/ business logic, one bounded context per domain │ ├── Actions/ Casts/ Collections/ Data/ Enums/ Events/ Exceptions/ (→ labrodev-exception skill) │ ├── Factories/ Jobs/ Models/ Observers/ Payloads/ │ ├── Pipelines/ Policies/ Queries/ Rules/ Services/ │ └── Traits/ Utilities/ ├── Feature/{FeatureName}/ isolated cross-domain workflows; promote to a Domain when stable ├── Infrastructure/{Integration}/ external adapters (payment, email, ERP, APIs); technical, not business → see the labrodev-infrastructure skill ├── Shared/ generic base abstractions (base models, concerns, traits); no domain nouns └── Support/ technical helpers/utilities only; no business logic, no domain lang