platform-custom-object-generate

Generate Salesforce Custom Object metadata with sharing models and validation rules.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-custom-object-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-custom-object-generate
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/platform-custom-object-generate
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-custom-object-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork and rework from Salesforce custom object creation, validation, and updates so teams can produce deployable metadata with fewer errors.

Core Features & Use Cases

  • Creates deployment-ready custom object metadata with the required label, plural label, sharing model, deployment status, visibility, and name field.
  • Applies smart defaults for text versus auto-number name fields, master-detail sharing behavior, and clean XML choices.
  • Keeps object descriptions current when fields or validation rules change, helping avoid stale documentation and deployment failures.
  • Use it when you need to generate a new custom object, fix sharing model issues, or refresh object metadata after schema changes.

Quick Start

Use the platform-custom-object-generate skill to create or update a Salesforce custom object metadata file with the correct sharing model, name field, and refreshed description.

Frequently Asked Questions about platform-custom-object-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a deployment-ready Salesforce custom object metadata file?

To generate a deployment-ready Salesforce custom object, you need the required label, plural label, sharing model, deployment status, visibility, and name field. Applying smart defaults for text versus auto-number name fields ensures clean XML and prevents deployment errors.

What's the best way to fix sharing model issues in Salesforce custom objects?

Fixing sharing model issues in Salesforce custom objects requires applying the correct master-detail sharing behavior during metadata generation. Configuring clean XML choices and validating constraints ensures the updated sharing model deploys without errors.

How do I keep custom object descriptions current after schema changes in SFDX?

To keep custom object descriptions current after schema changes in SFDX, refresh the object metadata when fields or validation rules change. This prevents stale documentation and avoids deployment failures caused by outdated object descriptions.

Does this apply validation rules and XML constraint validation for Salesforce DX projects?

Yes, XML constraint validation and description enrichment rules apply to validation rules in Salesforce DX projects. This prevents deployment errors by ensuring custom object metadata meets deployment-ready standards before execution.

Why does my Salesforce custom object deployment fail due to name field configuration?

Salesforce custom object deployment fails when the name field configuration is incorrect. Applying smart defaults for text versus auto-number name fields and validating XML constraints prevents stale object documentation and deployment failures.