What problem does it solve? Salesforce DX projects fail in predictable ways: metadata files placed in the wrong directory become invisible to the CLI, .forceignore entries silently drop components from deploys, source-tracking conflicts overwrite teammates' work, and monolithic force-app trees make ownership and packaging impossible. This Skill provides the authoritative rules for structuring, configuring, and maintaining a DX repository so deploys, retrieves, and team workflows behave predictably. ## Core Features & Use Cases - Project configuration: Full sfdx-project.json schema coverage including packageDirectories, sourceApiVersion, namespace, replacements, and sourceBehaviorOptions, with validation commands for each property. - Metadata placement and manifests: A complete metadata-type-to-directory map, .forceignore syntax and precedence rules, and package.xml / destructiveChangesPre/Post.xml manifest generation with sf project generate manifest. - Source tracking and team conventions: Conflict resolution with --ignore-conflicts scoped per component, sf project delete source for real deletions, branch-per-story models, path ownership for parallel agents, and metadata XML diff review checklists. - Use Case: When splitting a monolithic force-app into domain-aligned package directories, use this Skill to configure sfdx-project.json correctly, sequence the deploys explicitly, and verify with sf project deploy preview that nothing is silently ignored. ## Quick Start Ask the assistant to structure a new Salesforce DX project or audit where a specific metadata file belongs in an existing repository.
