/platform-lightning-app-coordinate

name: platform-lightning-app-coordinate
description: "Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a \"complete app\", \"Lightning app\", \"business solution\", \"management system\", or describes a scenario requiring multiple interconnected Salesforce components (objects, fields, pages, tabs, security). Orchestrates all required metadata types in proper dependency order to produce a deployable application."
metadata:
  version: "1.0"
  domains: ["Platform"]
  minApiVersion: "60.0"
  relatedSkills:
    - "automation-flow-generate"
    - "platform-custom-application-generate"
    - "platform-custom-field-generate"
    - "platform-custom-object-generate"
    - "platform-custom-tab-generate"
    - "platform-flexipage-generate"
    - "platform-list-view-generate"
    - "platform-permission-set-generate"
    - "platform-validation-rule-generate"
  mcpTools:
    metadata-experts:
      tools: ["execute_metadata_action"]
      semver: ">=1.0.0"
    salesforce-api-context:
      tools: ["get_metadata_type_context", "get_metadata_type_fields", "get_metadata_type_fields_properties", "get_metadata_type_sections", "search_metadata_types"]
      semver: ">=1.0.0"

Generating Lightning App

Overview

Build a complete, deployable Salesforce Lightning Experience application from a natural language description by defining a Lightning Custom Application and orchestrating its dependent metadata types in correct dependency order. Invoke specialized metadata skills when available; generate metadata directly when no skill exists.

When to Use This Skill

**Use when:**

• User requests a "Lightning app", or "end-to-end solution"
• User says "build an app", "create an application", "build a [type] app" (project management, tracking, etc.)
• The work produces a custom app (CustomApplication) plus supporting metadata, not a lone object, page, or tab in isolation

**Examples that should trigger this skill:**

• "Build a project management lightning app with Tasks, Resources, and Supplies objects"
• "Create a LEX app to track vehicles with Lightning pages and permission sets"
• "I need a Space Station management system with multiple objects and relationships"
• "Build an employee onboarding lightning app with custom Lightning Record Pages"

**Do NOT use when:**

• Creating a single metadata component (use specific metadata skill instead)
• Troubleshooting or debugging existing metadata
• Building Salesforce Classic apps (not Lightning Experience)
• User asks for just one object, or just one page, or just one permission set (without others)
• User only needs to create or configure an app container (grouping existing tabs) without other metadata; use `platform-custom-application-generate` instead

Metadata Type Registry

This table shows which metadata types are commonly needed for Lightning Experience apps, their skill availability, and API context requirement.

| Metadata Type | Skill Name | API Context | Usage Rule | |---------------|------------|-------------|------------| | **Custom Object** | `platform-custom-object-generate` | `salesforce-api-context` | MUST load skill AND call API context | | **Custom Field** | `platform-custom-field-generate` | `salesforce-api-context` | MUST load skill AND call API context | | **Custom Tab** | `platform-custom-tab-generate` | `salesforce-api-context` | MUST load skill AND call API context | | **FlexiPage** | `platform-flexipage-generate` | `salesforce-api-context` | MUST load skill AND call API context | | **Custom Application** | `platform-custom-application-generate` | `salesforce-api-context` | MUST load skill AND call API context | | **List View** | `platform-list-view-generate` | `salesforce-api-context` | MUST load skill AND call API context (if requested) | | **Validation Rule** | `platform-validation-rule-generate` | `salesforce-api-context` | MUST load skill AND call API context (if requested) | | **Flow** | `automation-flow-generate` | `metadata-experts` pipeline | MUST load skill AND run pipeline. **Exempt from `salesforce-api-context`**. | | **Permission Set** | `platform-permission-set-generate` | `salesforce-api-context` | MUST load skill AND call API context |

Usage Rules

**SKILL RULE**: When a skill exists for a metadata type, you **MUST** load that skill. Do NOT generate metadata directly without loading the skill first.

**API CONTEXT RULE**: For every metadata type (except Flow), you **MUST** call `salesforce-api-context` tools before generating. Do NOT generate metadata without calling API context first. The skill provides structure and rules; API context confirms what is valid for the current API version. Both are essential.

**FALLBACK RULE**: When no skill exists for a metadata type you need, generate the metadata directly using your knowledge of Salesforce Metadata API and best practices. API context is still required.

**RATIONALE**: Skills contain validated patterns and constraints. API context provides version-specific accuracy. Together they prevent deployment failures.

---

Dependency Graph & Build Order

Phase 1: Data Model (Foundation)

Custom Objects (no dependencies)
    ↓
Custom Fields (depends on: Objects exist)
    ↓
Relationships (depends on: Both parent and child objects + fields exist)

**Metadata types in this phase:**

1. `platform-custom-object-generate` - once, with all objects 2. `platform-custom-field-generate` - once, with all fields (including Master-Detail, Lookup, Roll-up Summary)

Phase 2: Business Logic (Optional - only if requested)

Validation Rules (depends on: Fields exist)
    ↓
Flows (depends on: Objects, Fields exist)

**Metadata types in this phase (only if user requested):**

1. `platform-validation-rule-generate` - once, if validation requirements mentioned 2. `automation-flow-generate` - once, if automation/workflow requirements mentioned

Phase 3: User Interface