lex-app-solution

Orchestrates Salesforce Lightning Experience app creation from natural language prompts.

803|289|Updated Nov 7, 2025

Search Tags:#automation #architecture #orchestration #metadata #salesforce #lex-app #application-builder

Ready to run

npx skills add https://github.com/forcedotcom/afv-library --skill lex-app-solution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lex-app-solution
Source: https://github.com/forcedotcom/afv-library/tree/main/skills/lex-app-solution
Command: npx skills add https://github.com/forcedotcom/afv-library --skill lex-app-solution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the complexity of manually designing and stitching together Salesforce Lightning Apps by providing end-to-end orchestration from a natural language prompt.

Core Features & Use Cases

Orchestrates the sequenced creation of Custom Objects, Fields, Lightning Record Pages, Custom Tabs, Custom Applications, and Permission Sets.
Ensures correct sequencing of metadata components (Objects → Fields → Tabs → Pages → Apps → Security) and supports optional Flows and Validation Rules when requested.
Enables building end-to-end business solutions requiring multiple metadata types to work together within Salesforce Lightning Experience.

Quick Start

Ask me to build a complete LEX App from your natural language scenario, including objects, fields, pages, tabs, apps, and permission sets.

Frequently Asked Questions about lex-app-solution

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 natural language prompt?▼

You can build a complete Salesforce Lightning app from a natural language prompt by orchestrating the creation of Custom Objects, Fields, Tabs, FlexiPages, Custom Applications, and Permission Sets in a fixed deployment sequence.

What is the correct sequence for creating Salesforce Lightning Experience metadata components?▼

The correct sequence for creating Salesforce Lightning Experience metadata components is Objects first, then Fields, followed by Tabs, FlexiPages, Custom Applications, and finally Permission Sets for security configurations.

Can I generate Salesforce Flows and Validation Rules alongside my Lightning app components?▼

Yes, you can generate Salesforce Flows and Validation Rules alongside your Lightning app components, as the orchestration supports these optional automations when explicitly requested in your natural language prompt.

Does this approach work for building business solutions that require multiple interconnected Salesforce metadata types?▼

Yes, this approach works for building business solutions requiring multiple interconnected Salesforce metadata types, ensuring that Custom Objects, Fields, Pages, Tabs, Apps, and Permission Sets are properly stitched together.

What's the best way to automate Lightning Experience app creation without manually stitching metadata components?▼

The best way to automate Lightning Experience app creation is using an orchestration approach that delegates metadata generation to specialized processes, eliminating the need to manually design and connect individual components.

Do I need to manually configure Permission Sets when building a Lightning app through orchestration?▼

No, you do not need to manually configure Permission Sets, as the orchestration automatically includes them as the final step in the deployment sequence to handle security configurations for your generated Lightning app.