platform-custom-application-generate
Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Do NOT use when the goal is hosting a React UI bundle in the App Launcher — use experience-ui-bundle-custom-app-generate for that case.
- Installs
- 5.8K
- Last 24h
- +15
- Trending rank
- #6972
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/forcedotcom/sf-skills --skill platform-custom-application-generate- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads platform-custom-application-generate automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
When to Use This Skill
Use this skill when you need to:
- Create Lightning applications
- Organize tabs and features into focused apps
- Configure application navigation and branding
- Set up custom page layouts for objects
- Troubleshoot deployment errors related to custom applications
CustomApplication (Lightning App) Metadata Specification
Overview
Custom applications (Lightning Apps) that group tabs and functionality to provide a focused user experience for specific business processes. Always configured for Lightning Experience.
Purpose
- Organize related functionality into focused applications
- Group tabs and components for specific user roles
- Provide tailored user experiences
- Control access to specific features and data
- Use Standard navigation for general business applications or Console navigation for specialized service/support workflows requiring multi-tab workspaces
- Create professional, branded application identity with custom colors and branding
- Override standard actions with custom Lightning pages for enhanced user experience
- Enable profile-specific experiences through profile action overrides
Required Properties
Core Application Properties
- fullName: API name of the application
- label: Display name of the application
- uiType: Always "Lightning" for modern apps
- navType: CRITICAL - Choose based on user requirements and workflow patterns
- "Standard": DEFAULT for general business applications (e.g., sales, marketing, operations)
- "Console": ONLY when workflow requires managing multiple records simultaneously with split-view or multi-tab workspace (e.g., customer service, call centers, support operations)
- formFactors: Array of form factors (["LARGE"] for desktop, ["SMALL"] for mobile, or both)
Optional Properties
- description: Brief description of the application's purpose
- tabs: Array of tab names to include
- utilityBar: API name of the Utility Bar configuration
- brand: HIGHLY RECOMMENDED - Branding configuration object (headerColor, shouldOverrideOrgTheme, footerColor)
- actionOverrides: REQUIRED when custom record pages exist - Action override configuration (actionName, content, formFactor, type, pageOrSobjectType)
- profileActionOverrides: Profile-specific action overrides (actionName, content, formFactor, pageOrSobjectType, type, profile)
- isNavAutoTempTabsDisabled: Navigation behavior setting (default: false)
- isNavPersonalizationDisabled: Personalization setting (default: false)
- isNavTabPersistenceDisabled: Tab persistence setting (default: false)
Application Configuration
Navigation Type Selection (CRITICAL)
Decision Criteria for navType:
Choose "Standard" (DEFAULT) for:
- General business applications and most workflows
- Single-record focus or linear navigation patterns
- Standard tab-based navigation is sufficient
Choose "Console" ONLY when workflow requires:
- Managing multiple related records simultaneously in split-view
- Multi-tab workspace for handling complex, interconnected data
- Contextual information from multiple sources visible at once
- Examples: customer service operations, support desks, call centers
When in doubt: Default to "Standard" for most general business use cases
Navigation Settings
- isNavAutoTempTabsDisabled: Controls automatic temporary tab creation
- isNavPersonalizationDisabled: Controls user personalization features
- isNavTabPersistenceDisabled: Controls tab persistence across sessions
Tab Management
- tabs: Array of tab names to include in the application
- formFactors: Device-specific configurations (Large for desktop, Small for mobile)
Utility Bar
- utilityBar: Reference to Lightning utility bar (appears at bottom of Lightning Experience)
Branding (HIGHLY RECOMMENDED - DO NOT SKIP)
IMPORTANT: Provide branding configuration to create a professional, visually distinct application identity.
- brand.headerColor: Header bar color in hex format (e.g., "#0070D2") - RECOMMENDED
- brand.shouldOverrideOrgTheme: Override organization theme (true/false) - Default: false
- brand.footerColor: Footer color in hex format
Action Overrides (CRITICAL - DO NOT SKIP)
IMPORTANT: Action overrides MUST be created for every custom object tab that has a record page generated by flexipage expert.
- actionOverrides.actionName: Action to override ("View" or "Tab")
- actionOverrides.content: Page/component name (FlexiPage, Visualforce, Lightning component)
- For "View" action: Reference record pages generated by flexipage expert
- For "Tab" action: Reference home/app pages generated by flexipage expert
- actionOverrides.formFactor: Device type ("Large" or "Small")
- actionOverrides.type: Override type ("Default", "Visualforce", "Flexipage", "LightningComponent", "Scontrol")
- Recommended: Use "Flexipage" for Lightning record/home pages generated by flexipage expert
- actionOverrides.pageOrSobjectType: Object API name the override applies to
- actionOverrides.comment: Optional description (max 1000 characters)
- Auto-generated comment: "Action override created by Lightning App Builder during activation."
- actionOverrides.skipRecordTypeSelect: Skip record type selection (default: false)
Profile Action Overrides
- profileActionOverrides.actionName: Action to override ("View" or "Tab")
- profileActionOverrides.content: Page/component name
- For "View" action: Reference profile-specific record pages generated by flexipage expert
- For "Tab" action: Reference profile-specific home pages generated by flexipage expert
- Can reference same or different FlexiPages than actionOverrides for profile-specific experiences
- profileActionOverrides.formFactor: Device type ("Large" or "Small")
- profileActionOverrides.pageOrSobjectType: Object API name
- profileActionOverrides.type: Override type
- Recommended: Use "Flexipage" for Lightning pages generated by flexipage expert
- profileActionOverrides.profile: Profile API name (e.g., "Admin", "Standard User")
- Enables different page layouts for different user profiles
Device Support
Desktop Configuration
- formFactor: "Large"
- tabs: Full list of application tabs
Phone Configuration
- formFactor: "Small"
- tabs: Mobile-optimized tab selection
Tablet Configuration
- formFactor: "Medium"
- tabs: Tablet-appropriate tab selection
User Experience Features
Navigation Behavior
- Auto Temporary Tabs: Can be enabled/disabled
- Personalization: User customization options
- Tab Persistence: Remember user's tab selections
Accessibility
- Keyboard Navigation: Full keyboard support
- Screen Reader: Compatible with assistive technologies
- High Contrast: Support for high contrast modes
Integration Points
- Custom Tabs: Include custom object and web tabs
- Standard Tabs: Include standard Salesforce tabs
- Lightning Pages: Integrate with Lightning page layouts
- Components: Include custom Lightning components
Best Practices
- Always use Lightning UI: Set
uiTypeto "Lightning" for modern apps - Choose appropriate navigation: CRITICAL - Analyze requirements carefully for
navTypeselection- Use "Standard" (DEFAULT) for general business applications
- Use "Console" ONLY when workflow requires multi-tab workspace, split-view, or managing multiple related records simultaneously
- Examples for Console: customer service, call centers, support operations
- Default to "Standard" for most general business use cases
- Include Standard Tabs: Add common Salesforce tabs (Home, Accounts, Contacts, etc.)
- Use clear, descriptive application names
- Group related functionality logically
- Consider different user roles and needs
- Test across different device types
- Ensure proper permissions and access control
- Provide meaningful descriptions for users
- Follow consistent naming conventions
- Always configure branding: Set headerColor to create professional application identity
- Use accessible brand colors: Ensure hex colors have sufficient contrast (WCAG AA compliant)
- Configure utility bars: Add useful quick-access tools for users
- Leverage action overrides: Customize page layouts for specific objects using FlexiPages from flexipage expert
- Use profile overrides: Provide role-specific experiences by referencing different flexipage expert generated pages per profile
Enhancement Rules
- uiType: Always set to "Lightning" for modern app experience
- navType: CRITICAL DECISION - Analyze user requirements carefully
- Set to "Standard" (DEFAULT) for general business applications
- Set to "Console" ONLY when workflow requires:
- Managing multiple related records simultaneously with split-view capability
- Multi-tab workspace for handling complex, interconnected data
- Contextual information from multiple sources visible at once
- Console examples: customer service operations, call centers, support desks
- When in doubt between Standard and Console, choose "Standard" for most business use cases
- formFactors: Always set to ["LARGE"] for desktop Lightning Experience
- Standard Tabs: Automatically add Home, Accounts, Contacts, Opportunities, Leads, Cases
- Navigation Settings: Set all navigation flags to false for best user experience
- Branding: ALWAYS include brand configuration for professional application identity
- MANDATORY: Set brand.headerColor to appropriate color (e.g., "#0070D2" for Salesforce Blue)
- Set brand.shouldOverrideOrgTheme based on requirements
- Action Overrides: ALWAYS create action overrides when custom record pages exist
- MANDATORY: Add actionOverrides for "View" action pointing to flexipage expert generated record pages
- Use "Flexipage" type and reference the exact FlexiPage name
- Set formFactor to "Large" for desktop
- Include pageOrSobjectType with the object API name
- Profile Action Overrides: Reference flexipage expert generated pages for role-based customization
- Form Factors: Use "Large" for desktop, "Small" for mobile in overrides
CRITICAL Verification Checklist (MUST VERIFY)
- All tabs are included in the application
- navType IS CORRECTLY SET - Verify Console vs Standard selection
- Default to "Standard" for most general business applications
- Set to "Console" ONLY if workflow requires managing multiple records simultaneously, split-view, or multi-tab workspace
- If requirements are general/ambiguous → navType should be "Standard"
- BRANDING IS CONFIGURED - This is HIGHLY RECOMMENDED for professional applications
- brand.headerColor is set with valid hex color (e.g., "#0070D2")
- brand.shouldOverrideOrgTheme is set (default: false)
- ACTION OVERRIDES ARE CREATED - This is MANDATORY for every custom object with a record page
- Action overrides are defined for EACH custom object tab pointing to the correct record page
- actionOverrides.content matches the exact FlexiPage name generated by flexipage expert
- actionOverrides.pageOrSobjectType is set to the correct object API name
- actionOverrides.type is set to "Flexipage"
- actionOverrides.actionName is set to "View"
- actionOverrides.formFactor is set to "Large"
- All required fields are populated (fullName, label, uiType, navType, formFactors)
FAQ
What does the platform-custom-application-generate skill do?
Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Do NOT use when the goal is hosting a React UI bundle in the App Launcher — use experience-ui-bundle-custom-app-generate for that case.
How do I install platform-custom-application-generate?
Run npx skills add https://github.com/forcedotcom/sf-skills --skill platform-custom-application-generate in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/platform-custom-application-generate/ (personal) or .claude/skills/platform-custom-application-generate/ (project).
Which AI agents can use platform-custom-application-generate?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is platform-custom-application-generate safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains platform-custom-application-generate?
It is published by forcedotcom in forcedotcom/sf-skills. It has 5,780 recorded installs.
More from forcedotcom/sf-skills
platform-apex-generate
forcedotcom/sf-skills
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill for requests involving SObject CRUD, mapping collections, fetching related records, scheduled jobs, batch jobs, trigger design, @AuraEnabled controllers, @RestResource endpoints, custom REST APIs, or code review of existing Apex.
platform-apex-test-generate
forcedotcom/sf-skills
Use to generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking, assertions, and disciplined test-fix loops. Use when creating Apex test classes (for triggers, services, controllers, batch jobs, queueables, and callouts), improving coverage, debugging or fixing failing Apex tests, or running test/coverage analysis. Triggers on Test.cls files, sf apex run test, coverage reports. Do NOT trigger for production Apex (use platform-apex-generate) or Jest/LWC tests.
platform-apex-test-run
forcedotcom/sf-skills
Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches Test.cls / Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate).
platform-apex-logs-debug
forcedotcom/sf-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).
platform-soql-query
forcedotcom/sf-skills
Use when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan/selectivity analysis, and performance or safety improvements. TRIGGER when the user writes, optimizes, or debugs SOQL/SOSL, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER for bulk data operations (use platform-data-manage), Apex DML logic (use platform-apex-generate), or report/dashboard queries.
platform-metadata-deploy
forcedotcom/sf-skills
Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, validates a deploy or does a dry-run, deploys to a Production org, quick-deploys a validated job ID, ships/promotes to prod, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code, building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate), deleting metadata from an org (use platform-destructive-deploy), or querying org data (use platform-data-manage).
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.