Generating Lightning App
Generate a full deployable Salesforce Lightning Experience app—with objects, UI, tabs, flows, and security—from a plain-language business scenario.
Overview
Generating Lightning App is an agent skill most often used in Build (also Ship) that assembles a complete, deployable Salesforce Lightning Custom Application and its dependent metadata from a natural language description
Install
npx skills add https://github.com/forcedotcom/afv-library --skill generating-lightning-appWhat is this skill?
- Turns natural language "complete app" or "management system" requests into a Lightning Custom Application plan
- Invokes specialized generating-* metadata skills in proper dependency order when available
- Covers interconnected components: objects, fields, tabs, flexipages, flows, validation, list views, permission sets
- Produces deployable application metadata, not isolated single-artifact snippets
- Version 1.0 skill with explicit related-skills map for downstream generators
- Metadata version 1.0
- Related-skills list spans 9 specialized generating-* metadata skills
Adoption & trust: 1.4k installs on skills.sh; 512 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 have scattered Salesforce metadata skills with no dependency order or unified Lightning application container.
Who is it for?
Indie consultants or solo admins using AI agents to stand up multi-object Lightning apps (tracking, PM, ops) in one guided pass.
Skip if: Single-object tweaks, lone flexipage edits, or App Launcher React UI bundles—which need generating-ui-bundle-custom-app instead of tab-based CustomApplication apps.
When should I use this skill?
User requests a complete app, Lightning app, business solution, management system, or a scenario needing multiple interconnected Salesforce components deployable as one application.
What do I get? / Deliverables
You get an orchestrated metadata set anchored on a Custom Application, ready for deployment after granular generators run in the right sequence.
- Lightning Custom Application definition
- Ordered set of dependent Salesforce metadata artifacts
- Invocation plan for granular generating-* skills
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build because the skill orchestrates many Salesforce metadata types into one application; Ship follows when you deploy that bundle. Integrations fits Salesforce metadata orchestration across objects, apps, pages, and automation rather than a single UI file.
Where it fits
Model a rental operations app with custom objects, tabs, and list views before any UI polish.
Add validation rules and flows implied by the business scenario in dependency-safe order.
Package the generated CustomApplication and related metadata for deployment to a sandbox org.
How it compares
Use this end-to-end orchestrator instead of chaining unrelated one-off Salesforce generator prompts without dependency ordering.
Common Questions / FAQ
Who is generating-lightning-app for?
It is for Salesforce builders and agent users who need a full Lightning Experience application—tabs, data model, pages, automation, and security—from a high-level scenario.
When should I use generating-lightning-app?
Use it in Build when the user asks for a complete Lightning app or management system; use Ship afterward to deploy and test the generated metadata bundle in a target org.
Is generating-lightning-app safe to install?
Review the Security Audits panel on this Prism page and your org’s change-management rules before letting an agent generate broad permission and automation metadata against production.
Workflow Chain
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.