platform-lightning-app-coordinate

Generates complete Salesforce Lightning applications by orchestrating metadata types in dependency order.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill platform-lightning-app-coordinate-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-lightning-app-coordinate
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/platform-lightning-app-coordinate
Command: npx skills add https://github.com/padjei/SF_Build --skill platform-lightning-app-coordinate-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a complete Salesforce Lightning Experience app requires creating many interdependent metadata types (objects, fields, tabs, pages, applications, permission sets) in the correct order, and mistakes in sequencing or structure cause deployment failures. This Skill turns a natural language app description into a coordinated, deployable metadata build. ## Core Features & Use Cases - Dependency-Ordered Orchestration: Builds metadata in five phases (data model, business logic, UI, app assembly, security) so every component's prerequisites exist before it is generated. - Per-Type Skill and API Context Enforcement: Loads the specialized generation skill and calls salesforce-api-context tools for each metadata type before writing files, with status lines recording completion. - Cross-Component Validation: Verifies object-tab coverage, relationship integrity, field references in FlexiPages, and permission set completeness, then reports warnings without blocking delivery. - Use Case: Ask for a project management app with Tasks, Resources, and Supplies objects, and receive a full SFDX project with objects, fields, tabs, Lightning record pages, a custom application, permission sets, a package.xml manifest, and a build summary report. ## Quick Start Build a Lightning app for employee onboarding with Employee and Task objects, record pages, and permission sets.

Frequently Asked Questions about platform-lightning-app-coordinate

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

FAQPage Schema
How do I build a complete Salesforce Lightning app from a description?▼

Describe the app's business entities, fields, relationships, and user personas in natural language. The skill produces a build plan, then generates objects, fields, tabs, FlexiPages, a custom application, and permission sets in dependency order as an SFDX project.

What metadata types are generated for a Salesforce Lightning app?▼

The build covers Custom Objects, Custom Fields, Custom Tabs, FlexiPages, a Custom Application, and Permission Sets. Validation Rules, Flows, and List Views are generated only when the request mentions validation, automation, or filtered views.

When should I not use Lightning app orchestration?▼

Do not use it for a single metadata component such as one object, page, or permission set; use the specific per-type generation skill instead. It also does not apply to Salesforce Classic apps, debugging existing metadata, or grouping existing tabs into an app container.

Why must metadata be generated in dependency order in Salesforce?▼

Fields require objects, tabs require objects, FlexiPages require tabs, and applications require tabs, so out-of-order generation causes deployment failures. The skill enforces five phases from data model through security to guarantee prerequisites exist first.

What happens if validation fails after the Lightning app is generated?▼

Post-generation validation failures are logged as warnings in the Build Summary Report under a VALIDATION WARNINGS section rather than blocking delivery. Each warning includes the affected component, impact, and recommended manual remediation steps.