PranavNagrecha/AwesomeSalesforceSkills / skills/admin/custom-field-creation
custom-field-creation
VerifiedUse when creating a new custom field on any Salesforce object: choosing field type, setting API name, configuring Field-Level Security, adding to page layouts, and deploying. Triggers: 'add a field', 'new custom field', 'what field type should I use', 'FLS not working', 'field not showing on page layout'. NOT for creating the object itself - use admin/object-creation-and-design. NOT for formula field logic - use admin/formula-fields. NOT for picklist value set management - use admin/picklist-and-value-sets. Also covers: field-meta.xml, CustomField metadata, deleteConstraint, externalId, unique, precision and scale, relationshipOrder, writeRequiresMasterRead, fieldPermissions, package.xml for fields.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.0 KB |
| references/examples.md | markdown | 8.1 KB |
| references/gotchas.md | markdown | 22.6 KB |
| references/llm-anti-patterns.md | markdown | 9.3 KB |
| references/metadata-examples.md | markdown | 33.8 KB |
| references/well-architected.md | markdown | 7.5 KB |
| scripts/check_custom_field_creation.pyexecutable | script | 16.1 KB |
| templates/custom-field-creation-template.md | markdown | 2.7 KB |
templates/custom-field-creation-template.md
View on GitHub# Custom Field Creation — Output Template
Use this template to document a custom field being created. Fill in each section before submitting the field for admin review or including it in a deployment.
---
## Field Summary
| Property | Value |
|----------|-------|
| **Object** | (e.g., Account, Opportunity, Case, My_Custom_Object__c) |
| **Field Label** | (user-facing name shown in the UI) |
| **Field API Name** | (e.g., Sales_Region__c — includes __c suffix) |
| **Field Type** | (Text / Picklist / Number / Date / Lookup / Master-Detail / etc.) |
| **Required** | Yes / No |
| **Unique** | Yes / No |
| **External ID** | Yes / No |
---
## Business Requirement
**What data does this field store?**
(One sentence describing what the field captures and why it exists.)
**Who enters or uses this data?**
(Which user roles, integrations, or automated processes write to this field.)
**How is this data used downstream?**
(Reports, flows, validation rules, Apex, integrations that read this field.)
---
## Field Type Rationale
**Why this field type was chosen:**
(Reference the decision guide in SKILL.md. E.g., "Picklist chosen because values are a fixed set of regions; enforces data consistency without validation rules.")
**Alternatives considered:**
(E.g., "Text was rejected because inconsistent user input would break report filters.")
---
## Field-Level Security (FLS)
| Profile / Permission Set | Read | Edit |
|--------------------------|------|------|
| (Profile or Perm Set name) | Yes / No | Yes / No |
| (Profile or Perm Set name) | Yes / No | Yes / No |
| (Profile or Perm Set name) | Yes / No | Yes / No |
---
## Page Layout Placement
| Page Layout | Section | Position |
|-------------|---------|----------|
| (Layout name) | (Section name, e.g., "Field Details") | (e.g., Left column, Row 3) |
| (Layout name) | (Section name) | |
**Dynamic Forms pages affected:**
(List any Lightning record pages using Dynamic Forms where the field must also be added to the Dynamic Form component.)
---
## Picklist Values (if applicable)
| API Value | Label | Default? |
|-----------|-------|----------|
| | | |
| | | |
**Global Value Set used?** Yes / No — (If yes, name of the Global Value Set)
---
## Deployment Checklist
- [ ] Field definition (`CustomField` metadata) included in change set or SFDX manifest.
- [ ] Page layout(s) (`Layout` metadata) included in the same deployment.
- [ ] Permission set FLS settings included if FLS is managed via Permission Sets.
- [ ] Deployment tested in a lower sandbox first (verify field visible to test user).
- [ ] Production deployment validated: field visible and editable for target users.
---
## Notes
(Any deviations from the standard creation process, known limitations, or follow-up actions.)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |