Generating Lightning App
Generate a deployable Salesforce Lightning custom application and dependent metadata from a natural-language business scenario.
Overview
generating-lightning-app is an agent skill for the Build phase that assembles deployable Salesforce Lightning custom applications and dependent metadata from natural language requirements.
Install
npx skills add https://github.com/forcedotcom/sf-skills --skill generating-lightning-appWhat is this skill?
- Builds complete Lightning Experience apps from NL descriptions, not isolated metadata snippets
- Orchestrates dependent metadata in proper dependency order for deployable packages
- Invokes specialized generating-* skills (objects, fields, tabs, FlexiPages, flows, permission sets, and more)
- Triggers on requests for complete apps, management systems, or multi-component business solutions
- Metadata version 1.0 with documented related-skills list for composition
- 9 related generating-* skills listed for orchestration (object, field, tab, flexipage, application, flow, validation rul
Adoption & trust: 724 installs on skills.sh; 513 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You described a full business app in chat but only got one object or page, with no ordered metadata plan for tabs, UI, security, and automation.
Who is it for?
Solo Salesforce builders and ISVs scoping a multi-object Lightning app from a single product-style description.
Skip if: One-off tweaks to a single field or page, non-Salesforce stacks, or teams that need production change management without human review of permissions and flows.
When should I use this skill?
User requests a complete Lightning app, business solution, management system, or multi-component Salesforce scenario requiring CustomApplication and dependent metadata.
What do I get? / Deliverables
You receive a orchestrated Lightning Custom Application plus interconnected metadata generated in deploy order, ready to validate and push to a Salesforce org.
- Lightning Custom Application definition
- Interconnected Salesforce metadata set
- Deploy-ordered metadata package for review
Recommended Skills
Journey fit
Build is canonical because the skill orchestrates creating interconnected Salesforce metadata—not distribution, validation experiments, or production monitoring. Integrations fits platform-specific app assembly (CustomApplication, FlexiPages, tabs, security) that connects objects, UI, and automation on Salesforce.
How it compares
Use for full-app metadata orchestration on Salesforce instead of asking the agent for piecemeal CustomObject or FlexiPage files without a CustomApplication shell.
Common Questions / FAQ
Who is generating-lightning-app for?
Developers and solution builders using agent-assisted Salesforce development who need end-to-end Lightning apps from conversational requirements.
When should I use generating-lightning-app?
Use it in Build when the user wants a complete Lightning app, management system, or business solution with multiple interconnected Salesforce components rather than a single metadata type.
Is generating-lightning-app safe to install?
Generated permission sets, flows, and validation rules can affect live orgs; review the Security Audits panel on this Prism page and validate in a sandbox before deploying.
SKILL.md
READMESKILL.md - Generating Lightning App
# 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 `generating-custom-application` 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** | `generating-custom-object` | `salesforce-api-context` | MUST load skill AND call API context | | **Custom Field** | `generating-custom-field` | `salesforce-api-context` | MUST load skill AND call API context | | **Custom Tab** | `generating-custom-tab` | `salesforce-api-context` | MUST load skill AND call API context | | **FlexiPage** | `generating-flexipage` | `salesforce-api-context` | MUST load skill AND call API context | | **Custom Application** | `generating-custom-application` | `salesforce-api-context` | MUST load skill AND call API context | | **List View** | `generating-list-view` | `salesforce-api-context` | MUST load skill AND call API context (if requested) | | **Validation Rule** | `generating-validation-rule` | `salesforce-api-context` | MUST load skill AND call API context (if requested) | | **Flow** | `generating-flow` | `metadata-experts` pipeline | MUST load skill AND run pipeline. **Exempt from `salesforce-api-context`**. | | **Permission Set** | `generating-permission-set` | `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.