What problem does it solve? Salesforce teams routinely over-build: custom Apex where a validation rule would do, custom LWC forms duplicating lightning-record-edit-form, custom REST endpoints duplicating Composite and Bulk API 2.0, and second trigger frameworks beside existing ones. This Skill walks a seven-rung decision ladder that challenges the requirement, searches the repo and org for existing solutions, and prefers declarative configuration, base components, and standard APIs before any custom code is written. ## Core Features & Use Cases - Seven-rung decision ladder: Challenges whether the requirement needs to exist, checks the repo and org for existing artefacts, prefers validation rules, formula fields, roll-up summaries, Flows, and sharing rules over Apex, prefers base Lightning components and LDS wire adapters over custom components, and prefers standard REST/Composite/Bulk API 2.0 endpoints over custom Apex REST. - Non-negotiable correctness floor: Enforces CRUD/FLS (WITH USER_MODE at API 67.0+), sharing declarations, bulkification, tests, accessibility, idempotency, and no secrets in metadata, so minimal never means incomplete. - Over-build catalogue and review checklist: Maps common over-builds (wrapper components, single-caller interfaces, config flags nobody flips) to their smaller alternatives, with verification commands and PR review questions. - Use Case: Before implementing "show total open pipeline on Account", the ladder finds Opportunity-to-Account is a lookup, selects a record-triggered Flow instead of an Apex rollup, and records the rejected alternatives in the decision log. ## Quick Start Ask the assistant to apply the minimal-change ladder to decide the smallest Salesforce implementation for a new requirement before writing any Apex, LWC, or Flow.
