kugamon/salesforce-core-skills / plugins/salesforce-core/skills/sf-metadata
sf-metadata
VerifiedSalesforce metadata operations expert. Use when creating custom objects, fields, validation rules, record types, permission sets, or querying org metadata structures via a Salesforce MCP server. Do NOT use for comparing metadata across two orgs (use sf-orgdiff), Named or External Credentials and Platform Events (use sf-integration), or querying and loading records (use sf- data). Usage: /sf-metadata [create|update|delete|describe] {ObjectName|FieldName|type} ...
assets/layouts/page-layout.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<!--
Page Layout Template
Usage: Define field arrangement and sections for record pages
Placeholders:
- {{LAYOUT_NAME}} - Full name (Object-Layout Name, e.g., "Account-Business Account Layout")
Notes:
- Page layouts are complex XML structures
- Consider using Lightning Record Pages instead for modern UIs
- Layout determines:
- Field arrangement in sections
- Related lists
- Actions/buttons
- Canvas apps, Visualforce pages
-->
<Layout xmlns="http://soap.sforce.com/2006/04/metadata">
<!--
═══════════════════════════════════════════
LAYOUT SECTIONS
═══════════════════════════════════════════
-->
<layoutSections>
<customLabel>false</customLabel>
<detailHeading>false</detailHeading>
<editHeading>true</editHeading>
<label>Information</label>
<layoutColumns>
<layoutItems>
<behavior>Required</behavior>
<field>Name</field>
</layoutItems>
<layoutItems>
<behavior>Edit</behavior>
<field>Type</field>
</layoutItems>
</layoutColumns>
<layoutColumns>
<layoutItems>
<behavior>Edit</behavior>
<field>OwnerId</field>
</layoutItems>
</layoutColumns>
<style>TwoColumnsTopToBottom</style>
</layoutSections>
<layoutSections>
<customLabel>true</customLabel>
<detailHeading>true</detailHeading>
<editHeading>true</editHeading>
<label>Additional Information</label>
<layoutColumns>
<layoutItems>
<behavior>Edit</behavior>
<field>Description</field>
</layoutItems>
</layoutColumns>
<layoutColumns/>
<style>TwoColumnsLeftToRight</style>
</layoutSections>
<layoutSections>
<customLabel>true</customLabel>
<detailHeading>true</detailHeading>
<editHeading>true</editHeading>
<label>System Information</label>
<layoutColumns>
<layoutItems>
<behavior>Readonly</behavior>
<field>CreatedById</field>
</layoutItems>
</layoutColumns>
<layoutColumns>
<layoutItems>
<behavior>Readonly</behavior>
<field>LastModifiedById</field>
</layoutItems>
</layoutColumns>
<style>TwoColumnsLeftToRight</style>
</layoutSections>
<!--
═══════════════════════════════════════════
RELATED LISTS
═══════════════════════════════════════════
-->
<relatedLists>
<fields>FULL_NAME</fields>
<fields>CONTACT.TITLE</fields>
<fields>CONTACT.EMAIL</fields>
<fields>CONTACT.PHONE1</fields>
<relatedList>RelatedContactList</relatedList>
</relatedLists>
<relatedLists>
<fields>OPPORTUNITY.NAME</fields>
<fields>OPPORTUNITY.STAGE_NAME</fields>
<fields>OPPORTUNITY.AMOUNT</fields>
<fields>OPPORTUNITY.CLOSE_DATE</fields>
<relatedList>RelatedOpportunityList</relatedList>
</relatedLists>
<!--
═══════════════════════════════════════════
QUICK ACTIONS
═══════════════════════════════════════════
-->
<quickActionList>
<quickActionListItems>
<quickActionName>FeedItem.TextPost</quickActionName>
</quickActionListItems>
<quickActionListItems>
<quickActionName>NewTask</quickActionName>
</quickActionListItems>
<quickActionListItems>
<quickActionName>NewEvent</quickActionName>
</quickActionListItems>
<quickActionListItems>
<quickActionName>LogACall</quickActionName>
</quickActionListItems>
</quickActionList>
<!--
═══════════════════════════════════════════
DISPLAY OPTIONS
═══════════════════════════════════════════
-->
<showEmailCheckbox>false</showEmailCheckbox>
<showHighlightsPanel>false</showHighlightsPanel>
<showInteractionLogPanel>false</showInteractionLogPanel>
<showRunAssignmentRulesCheckbox>false</showRunAssignmentRulesCheckbox>
<showSubmitAndAttachButton>false</showSubmitAndAttachButton>
</Layout>
<!--
LAYOUT BEHAVIOR OPTIONS
════════════════════════════════════════════
Field behaviors:
- Required: Field must have value (red bar)
- Edit: Field is editable
- Readonly: Field is read-only
- Hidden: Field not shown (rare in layout)
Section styles:
- TwoColumnsTopToBottom
- TwoColumnsLeftToRight
- OneColumn
- CustomLinks
PAGE LAYOUT VS LIGHTNING RECORD PAGE
════════════════════════════════════════════
Page Layout (Classic + Lightning):
├── Controls field arrangement
├── Controls related lists
├── Works in Classic and Lightning
└── Assigned via Profile
Lightning Record Page (Lightning only):
├── Drag-and-drop App Builder
├── Controls page structure
├── Supports components, tabs, accordions
└── More flexible than page layouts
RECOMMENDATION: Use Lightning Record Pages for modern UIs,
Page Layouts for field organization and related lists.
FILE NAMING
════════════════════════════════════════════
Location: force-app/main/default/layouts/
Format: [ObjectName]-[Layout Name].layout-meta.xml
Examples:
- Account-Account Layout.layout-meta.xml
- Account-Business Account Layout.layout-meta.xml
- Custom_Object__c-Custom Object Layout.layout-meta.xml
-->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |