What problem does it solve? Writing triggers, validation logic, and multi-object transactions in an fflib-based Salesforce org requires knowing exactly where each piece of logic belongs; this Skill provides the dispatch tables, API signatures, and anti-patterns for the write side of Apex Enterprise Patterns. ## Core Features & Use Cases - Domain Layer Guidance: One-line trigger dispatch via fflib_SObjectDomain.triggerHandler, onApplyDefaults/onValidate overrides, Configuration flags, and Constructor inner class requirements. - Service Layer Patterns: Interface plus implementation plus static shim structure, bulk-first signatures, transaction ownership rules, and thin @AuraEnabled/@InvocableMethod entry points. - Unit of Work Mastery: registerNew/registerDirty/registerRelationship chains, platform event publishing after success or failure, custom IDML with USER_MODE access, and commit ordering. - Use Case: When an Opportunity closes won, build a service that creates a Project and child tasks in one transaction, publishes a platform event only on commit, and exposes the same logic to LWC and Flow. ## Quick Start Ask the assistant to write an fflib trigger, domain class, and service with a Unit of Work that creates Projects from closed-won Opportunities.