sf-data-modeling

Design scalable Salesforce data models with object, field, and relationship definitions.

13|2|Updated Mar 18, 2026

Search Tags:#design #metadata #sharing #data-modeling #relationships #salesforce #custom-objects

Ready to run

npx skills add https://github.com/jiten-singh-shahi/salesforce-claude-code --skill sf-data-modeling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sf-data-modeling
Source: https://github.com/jiten-singh-shahi/salesforce-claude-code/tree/main/.cursor/skills/sf-data-modeling
Command: npx skills add https://github.com/jiten-singh-shahi/salesforce-claude-code --skill sf-data-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable and maintainable Salesforce data models can be difficult without a clear blueprint for custom objects, relationships, and sharing strategies across an org.

Core Features & Use Cases

Object and field design guidance for custom objects, including lookup and master-detail relationships, field naming, and naming conventions.
Sharing and metadata planning, covering record types, page layouts, and access models to support scalable org architecture.
Real-world planning examples and best-practice patterns for large data volumes, external objects, and metadata deployment.

Quick Start

Design a scalable Salesforce data model for a new org by outlining objects, relationships, and sharing rules.

Frequently Asked Questions about sf-data-modeling

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

FAQPage Schema

How do I design a scalable Salesforce data model for a new org?▼

A scalable Salesforce data model requires mapping custom objects, defining lookup and master-detail relationships, and establishing sharing rules. Enforcing naming conventions and metadata deployment patterns ensures maintainable architecture across multiple environments.

What is the best way to structure Salesforce custom objects and relationships?▼

Structuring Salesforce custom objects involves applying best-practice patterns for relationship types, field naming, and metadata. Choosing between lookup and master-detail relationships depends on your sharing model requirements and data volume constraints.

When should I use master-detail versus lookup relationships in Salesforce?▼

Use master-detail relationships in Salesforce when you need cascading sharing rules and tight coupling between records. Choose lookup relationships when you need flexible access models and independent record ownership across custom objects.

Can I use this approach for large data volumes and external objects in Salesforce?▼

Yes, this approach supports large data volumes and external objects in Salesforce by applying specific architecture planning patterns. It validates user requirements and constraints to ensure your sharing model and metadata deployment remain performant at scale.

How does Salesforce metadata deployment work across multiple environments?▼

Salesforce metadata deployment across multiple environments works by packaging object definitions, field configurations, and sharing settings. Validating metadata types and enforcing naming conventions prevents architectural drift during environment migration.

What are the limitations of custom objects in Salesforce data modeling?▼

Limitations of custom objects in Salesforce data modeling include relationship constraints and sharing model complexities at large data volumes. Proper architecture planning helps navigate record types, page layouts, and access model boundaries effectively.