Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
forcedotcom avatar

Generating Flexipage

  • 1.6k installs
  • 763 repo stars
  • Updated July 24, 2026
  • forcedotcom/afv-library

This is a copy of generating-flexipage by forcedotcom - installs and ranking accrue to the original listing.

generating-flexipage is a Salesforce agent skill that generates, modifies, and validates Lightning FlexiPage XML for RecordPage, AppPage, and HomePage layouts using correct CLI templates and metadata structures.

About

generating-flexipage is a forcedotcom afv-library skill at version 1.0 for creating, modifying, and validating Salesforce Lightning FlexiPages. The skill covers RecordPage, AppPage, and HomePage types, component regions, page customization, and deployment error fixes when working with FlexiPage XML. Developers reach for generating-flexipage when adding components to record pages, generating new Lightning pages, or troubleshooting FlexiPage metadata from Salesforce CLI deploys. It triggers on any Salesforce page work—including phrases like customize the record page or generate a FlexiPage—and enforces correct component and region structures.

  • Always starts new FlexiPages with the official Salesforce CLI template command
  • Generates valid FlexiPage metadata XML for RecordPage, AppPage, and HomePage types
  • Adds and configures components, regions, and layouts without deployment errors
  • Troubleshoots and fixes FlexiPage deployment issues
  • Edits any *.flexipage-meta.xml file with proper structure

Generating Flexipage by the numbers

  • 1,551 all-time installs (skills.sh)
  • +2 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/forcedotcom/afv-library --skill generating-flexipage

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.6k
repo stars763
Security audit3 / 3 scanners passed
Last updatedJuly 24, 2026
Repositoryforcedotcom/afv-library

How do you create Salesforce Lightning FlexiPage XML?

Generate, modify, and validate Salesforce Lightning FlexiPages using correct CLI templates and metadata structures.

Who is it for?

Salesforce developers building or customizing Lightning record, app, and home pages through metadata and CLI workflows.

Skip if: Non-Salesforce frontends or teams customizing pages only through Lightning App Builder without metadata deploys.

When should I use this skill?

A developer mentions FlexiPage, RecordPage, AppPage, HomePage, Lightning page components, or FlexiPage deployment errors.

What you get

Valid FlexiPage XML metadata with component regions for RecordPage, AppPage, or HomePage ready for Salesforce CLI deploy.

  • FlexiPage XML metadata file

By the numbers

  • Skill version 1.0

Files

SKILL.mdMarkdownGitHub ↗

data360-query: Data Cloud Retrieve Phase

Use this skill when the user needs query, search, and metadata introspection for Data Cloud: sync SQL, paginated SQL, async query workflows, table describe, vector search, hybrid search, or search index operations.

When This Skill Owns the Task

Use data360-query when the work involves:

  • sf data360 query *
  • sf data360 search-index *
  • sf data360 metadata *
  • sf data360 profile * or sf data360 insight * inspection
  • understanding Data Cloud SQL results or query shape

Delegate elsewhere when the user is:

  • writing standard CRM SOQL only → platform-soql-query
  • designing segment or calculated insight assets → data360-segment
  • analyzing STDM/session tracing/parquet telemetry → agentforce-observe

---

Required Context to Gather First

Ask for or infer:

  • target org alias
  • whether the user needs quick count, medium result set, large export, schema inspection, or semantic search
  • table/index name if known
  • whether the task is read-only SQL or search-index lifecycle management

---

Core Operating Rules

  • Treat Data Cloud SQL as its own query language, not SOQL.
  • Run the shared readiness classifier before relying on query/search surfaces: node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json.
  • Use describe before guessing columns.
  • Prefer sqlv2 or async query flows for larger result sets.
  • Use vector search or hybrid search only when the search index lifecycle is healthy.
  • Keep STDM/parquet/session-tracing workflows out of this skill family.

---

Recommended Workflow

1. Classify readiness for retrieve work

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
# optional query-plane probe, only with a real table name
node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json

2. Choose the smallest correct query shape

sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query sqlv2 -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query async-create -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null

3. Use describe before guessing fields

sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null

4. Use vector or hybrid search only when an index exists

sf data360 search-index list -o <org> 2>/dev/null
sf data360 query vector -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o <org> --index Insurance_Index --query "weather damage coverage" --prefilter "Type_of_Insurance__c='Home'" --limit 10 2>/dev/null

5. Reuse curated search-index examples when creating indexes

Use the phase-owned examples instead of inventing JSON from scratch:

  • examples/search-indexes/vector-knowledge.json
  • examples/search-indexes/hybrid-structured.json

---

High-Signal Gotchas

  • Data Cloud SQL is not SOQL.
  • Table names should be double-quoted in SQL.
  • sqlv2 is better than ad hoc OFFSET paging for medium result sets.
  • async query is preferable for large results.
  • search-index operations and vector/hybrid queries depend on the index lifecycle being healthy.
  • Hybrid search can use --prefilter, but only on fields configured as prefilter-capable when the search index was created.
  • HNSW index parameters are typically read-only on create; leave userValues: [] unless the platform explicitly documents otherwise.
  • query describe is not a universal tenant probe; only run it with a known DMO or DLO table after broader readiness has been confirmed.

---

Output Format

Retrieve task: <sql / sqlv2 / async / describe / vector / search-index>
Target org: <alias>
Target object: <table or index>
Commands: <key commands run>
Verification: <query rows / schema / status>
Next step: <segment / harmonize / follow-up>

---

References

  • README.md
  • examples/search-indexes/vector-knowledge.json
  • examples/search-indexes/hybrid-structured.json
  • ../data360-orchestrate/assets/definitions/search-index.template.json
  • ../data360-orchestrate/references/plugin-setup.md
  • ../data360-orchestrate/references/feature-readiness.md

Related skills

FAQ

Which Lightning page types does generating-flexipage support?

generating-flexipage supports RecordPage, AppPage, and HomePage FlexiPage XML, including component regions, page customization, and CLI-ready metadata structures.

When should generating-flexipage run for Salesforce page work?

generating-flexipage should run whenever developers create, modify, or validate Lightning pages, FlexiPage XML files, component placement, or page deployment errors in Salesforce.

Is Generating Flexipage safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.