platform-flexipage-generate

Name: platform-flexipage-generate
Availability: InStock
Author: angryracoon

Generate and validate Salesforce FlexiPage metadata for RecordPage, AppPage, and HomePage.

Updated Jun 17, 2026

Search Tags:#deployment #cli #xml #salesforce #lightning #flexipage #recordpage

Ready to run

npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-flexipage-generate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: platform-flexipage-generate
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/platform-flexipage-generate
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-flexipage-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create and validate Salesforce Lightning FlexiPages without introducing invalid XML, duplicate identifiers, or deployment-breaking region layouts.

Core Features & Use Cases

CLI-first generation: Bootstraps new RecordPage, AppPage, and HomePage metadata from the Salesforce CLI template command.
Validation and troubleshooting: Explains common deployment errors, field reference rules, and XML encoding requirements.
Safe page editing: Guides updates to existing *.flexipage-meta.xml files while preserving unique regions, facets, and identifiers.
Use case: Create a new record page, validate its XML, and prepare it for deployment with the correct component structure.

Quick Start

Use this skill to create or update a Salesforce FlexiPage and check it for deployment-safe XML before you deploy.

Frequently Asked Questions about platform-flexipage-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a Salesforce FlexiPage using the CLI without deployment errors?▼

Generate Salesforce FlexiPage metadata by bootstrapping new RecordPage, AppPage, or HomePage files from the Salesforce CLI template command. This CLI-first approach prevents XML encoding errors, duplicate identifiers, and invalid region layouts during deployment.

Why does my FlexiPage deployment fail with duplicate region or identifier errors?▼

FlexiPage deployment fails when XML files contain duplicate regions, facets, or identifiers. Validating Lightning page structure ensures all regions and identifiers remain unique and field references are correct before deploying the metadata.

How do I safely edit an existing flexipage-meta.xml file without breaking the Lightning page structure?▼

Safely edit existing flexipage-meta.xml files by preserving unique regions, facets, and identifiers during updates. Guided validation checks Record field references and XML encoding to prevent deployment-breaking structural changes.

What is the difference between RecordPage, AppPage, and HomePage when generating FlexiPage metadata?▼

RecordPage, AppPage, and HomePage are distinct FlexiPage types in Salesforce Lightning. Generating FlexiPage metadata involves bootstrapping the correct page type from the CLI, each requiring unique regions, facets, and valid field references for deployment.

Can I validate Lightning page XML structure before deploying a FlexiPage?▼

Yes, validating Lightning page XML structure before deployment checks for unique regions, correct Record field references, and proper XML encoding. This troubleshooting step prevents common deployment errors in flexipage-meta.xml files.