mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-07-30 03:09:50 +08:00
W-21667517: Update Skills name as per the recommendations (#77)
* refactor: Update skills name * refactor: update the LEX app skill name
This commit is contained in:
parent
9ba064174a
commit
f87b74aca4
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-custom-application
|
||||
name: generating-custom-application
|
||||
description: Use this skill when users need to create or configure Salesforce Custom Applications. 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. Always use this skill for custom application work.
|
||||
---
|
||||
|
||||
@ -11,7 +11,6 @@ Use this skill when you need to:
|
||||
- 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
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-custom-field
|
||||
name: generating-custom-field
|
||||
description: Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, or field metadata. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, or formula issues. Always use this skill for any custom field metadata work, field generation, or field troubleshooting.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-custom-lightning-type
|
||||
name: generating-custom-lightning-type
|
||||
description: Use this skill when users need to create Custom Lightning Types (CLTs) for Einstein Agent actions or structured input/output schemas. Trigger when users mention CLT, Custom Lightning Types, JSON schemas for agents, type definitions, lightning__objectType, or editor/renderer configurations. This is complex - always use this skill for CLT work.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-custom-object
|
||||
name: generating-custom-object
|
||||
description: Use this skill when users need to create, generate, or validate Salesforce Custom Object metadata. Trigger when users mention custom objects, creating objects, object metadata, .object files, sharing models, name fields, or validation rules on objects. Also use when users say things like "create a custom object", "generate object metadata", "set up an object for...", or when they're troubleshooting object deployment errors especially around sharing models and Master-Detail relationships. Always use this skill for any custom object metadata work.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-custom-tab
|
||||
name: generating-custom-tab
|
||||
description: Use this skill when users need to create or configure Salesforce Custom Tabs. Trigger when users mention tabs, navigation tabs, object tabs, web tabs, Visualforce tabs, Lightning component tabs, app page tabs, or tab configuration. Also use when users want to add navigation to custom objects, create tabs for external content, or set up Lightning page tabs. Always use this skill for any custom tab work.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-flexipage
|
||||
name: generating-flexipage
|
||||
description: Use this skill when users need to create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger when users mention RecordPage, AppPage, HomePage, Lightning pages, page layouts, adding components to pages, or page customization. Also use when users say things like "create a Lightning page", "add a component to a page", "customize the record page", "generate a FlexiPage", or when they're working with FlexiPage XML files and need help with components, regions, or deployment errors. Always use this skill for any FlexiPage-related work, even if they just mention "page" in the context of Salesforce.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-flow
|
||||
name: generating-flow
|
||||
description: Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-fragment
|
||||
name: generating-fragment
|
||||
description: Use this skill when users need to create or edit Salesforce Fragments (reusable UI pieces). Trigger when users mention fragments, UEM blocks, reusable UI templates, structured rendering across Slack/Mobile/LEX, or block-based layouts. Also use when users want to create unified experience components. Always use this skill for any fragment work.
|
||||
---
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
name: salesforce-lightning-app-build
|
||||
name: generating-lightning-app-solution
|
||||
description: Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a "complete app", "Lightning app", "business solution", "management system", or describes a scenario requiring multiple interconnected Salesforce components (objects, fields, pages, tabs, security). Orchestrates all required metadata types in proper dependency order to produce a deployable application.
|
||||
metadata:
|
||||
category: orchestration
|
||||
version: "1.0"
|
||||
related-skills: salesforce-custom-object, salesforce-custom-field, salesforce-custom-tab, salesforce-flexipage, salesforce-custom-application, salesforce-flow, salesforce-validation-rule, salesforce-list-view, generate-permission-set
|
||||
related-skills: skills/generating-custom-object/SKILL.md, skills/generating-custom-field/SKILL.md, skills/generating-custom-tab/SKILL.md, skills/generating-flexipage/SKILL.md, skills/generating-custom-application/SKILL.md, skills/generating-flow/SKILL.md, skills/generating-validation-rule/SKILL.md, skills/generating-list-view/SKILL.md, skills/generating-permission-set/SKILL.md
|
||||
---
|
||||
|
||||
# Salesforce Lightning Application Build
|
||||
# Generating Lightning App Solution
|
||||
|
||||
## Overview
|
||||
|
||||
@ -35,6 +35,7 @@ Build a complete, deployable Salesforce Lightning Experience application from a
|
||||
- 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 skills/generating-custom-application/SKILL.md instead
|
||||
|
||||
## Metadata Type Registry
|
||||
|
||||
@ -42,15 +43,15 @@ This table shows which metadata types are commonly needed for LEX apps and their
|
||||
|
||||
| Metadata Type | Skill Available? | Skill Name | Usage Rule |
|
||||
|---------------|------------------|------------|------------|
|
||||
| **Custom Object** | ✅ YES | `salesforce-custom-object` | MUST use skill |
|
||||
| **Custom Field** | ✅ YES | `salesforce-custom-field` | MUST use skill |
|
||||
| **Custom Tab** | ✅ YES | `salesforce-custom-tab` | MUST use skill |
|
||||
| **FlexiPage** | ✅ YES | `salesforce-flexipage` | MUST use skill |
|
||||
| **Custom Application** | ✅ YES | `salesforce-custom-application` | MUST use skill |
|
||||
| **List View** | ✅ YES | `salesforce-list-view` | MUST use skill |
|
||||
| **Validation Rule** | ✅ YES | `salesforce-validation-rule` | MUST use skill (if requested) |
|
||||
| **Flow** | ✅ YES | `salesforce-flow` | MUST use skill (if requested) |
|
||||
| **Permission Set** | ✅ YES | `generate-permission-set` | MUST use skill |
|
||||
| **Custom Object** | ✅ YES | `skills/generating-custom-object/SKILL.md` | MUST use skill |
|
||||
| **Custom Field** | ✅ YES | `skills/generating-custom-field/SKILL.md` | MUST use skill |
|
||||
| **Custom Tab** | ✅ YES | `skills/generating-custom-tab/SKILL.md` | MUST use skill |
|
||||
| **FlexiPage** | ✅ YES | `skills/generating-flexipage/SKILL.md` | MUST use skill |
|
||||
| **Custom Application** | ✅ YES | `skills/generating-custom-application/SKILL.md` | MUST use skill |
|
||||
| **List View** | ✅ YES | `skills/generating-list-view/SKILL.md` | MUST use skill |
|
||||
| **Validation Rule** | ✅ YES | `skills/generating-validation-rule/SKILL.md` | MUST use skill (if requested) |
|
||||
| **Flow** | ✅ YES | `skills/generating-flow/SKILL.md` | MUST use skill (if requested) |
|
||||
| **Permission Set** | ✅ YES | `skills/generating-permission-set/SKILL.md` | MUST use skill |
|
||||
|
||||
### Skill Usage Rules
|
||||
|
||||
@ -74,8 +75,8 @@ Relationships (depends on: Both parent and child objects + fields exist)
|
||||
```
|
||||
|
||||
**Skills to invoke in order:**
|
||||
1. `salesforce-custom-object` for each object
|
||||
2. `salesforce-custom-field` for each field (including Master-Detail, Lookup, Roll-up Summary)
|
||||
1. `skills/generating-custom-object/SKILL.md` — once, with all objects
|
||||
2. `skills/generating-custom-field/SKILL.md` — once, with all fields (including Master-Detail, Lookup, Roll-up Summary)
|
||||
|
||||
### Phase 2: Business Logic (Optional - only if requested)
|
||||
```
|
||||
@ -85,8 +86,8 @@ Flows (depends on: Objects, Fields exist)
|
||||
```
|
||||
|
||||
**Skills to invoke (only if user requested):**
|
||||
1. `salesforce-validation-rule` if validation requirements mentioned
|
||||
2. `salesforce-flow` if automation/workflow requirements mentioned
|
||||
1. `skills/generating-validation-rule/SKILL.md` — once, if validation requirements mentioned
|
||||
2. `skills/generating-flow/SKILL.md` — once, if automation/workflow requirements mentioned
|
||||
|
||||
### Phase 3: User Interface
|
||||
```
|
||||
@ -98,9 +99,9 @@ FlexiPages (depends on: Objects, Tabs exist)
|
||||
```
|
||||
|
||||
**Skills to invoke in order:**
|
||||
1. `salesforce-list-view` for filtered record views (if requested)
|
||||
2. `salesforce-custom-tab` for each object tab
|
||||
3. `salesforce-flexipage` for record/home/app pages
|
||||
1. `skills/generating-list-view/SKILL.md` — once, for filtered record views (if requested)
|
||||
2. `skills/generating-custom-tab/SKILL.md` — once, with all object tabs
|
||||
3. `skills/generating-flexipage/SKILL.md` — once, with all record/home/app pages
|
||||
|
||||
### Phase 4: Application Assembly
|
||||
```
|
||||
@ -108,7 +109,7 @@ Custom Application (depends on: Tabs exist)
|
||||
```
|
||||
|
||||
**Skills to invoke:**
|
||||
1. `salesforce-custom-application` to create the Lightning App container
|
||||
1. `skills/generating-custom-application/SKILL.md` — once, to create the Lightning App container
|
||||
|
||||
### Phase 5: Security & Access
|
||||
```
|
||||
@ -116,7 +117,7 @@ Permission Sets (depends on: Objects, Fields, Tabs, App exist)
|
||||
```
|
||||
|
||||
**Skills to invoke:**
|
||||
1. `generate-permission-set` for each permission set with access to:
|
||||
1. `skills/generating-permission-set/SKILL.md` — once, with all permission sets and access to:
|
||||
- Objects (Read, Create, Edit, Delete)
|
||||
- Fields (Read, Edit)
|
||||
- Tabs (Visible)
|
||||
@ -163,14 +164,14 @@ SECURITY:
|
||||
- Permission Sets: [list with purpose]
|
||||
|
||||
METADATA SKILLS TO INVOKE:
|
||||
- salesforce-custom-object (x N)
|
||||
- salesforce-custom-field (x N)
|
||||
- salesforce-validation-rule (x N) - if validation requirements identified
|
||||
- salesforce-flow (x N) - if automation requirements identified
|
||||
- salesforce-custom-tab (x N)
|
||||
- salesforce-flexipage (x N)
|
||||
- salesforce-custom-application (x 1)
|
||||
- generate-permission-set (x N)
|
||||
- skills/generating-custom-object/SKILL.md (x 1)
|
||||
- skills/generating-custom-field/SKILL.md (x 1)
|
||||
- skills/generating-validation-rule/SKILL.md (x 1) - if validation requirements identified
|
||||
- skills/generating-flow/SKILL.md (x 1) - if automation requirements identified
|
||||
- skills/generating-custom-tab/SKILL.md (x 1)
|
||||
- skills/generating-flexipage/SKILL.md (x 1)
|
||||
- skills/generating-custom-application/SKILL.md (x 1)
|
||||
- skills/generating-permission-set/SKILL.md (x 1)
|
||||
|
||||
DEPENDENCY ORDER:
|
||||
1. Phase 1: Data Model (Objects → Fields)
|
||||
@ -182,23 +183,23 @@ DEPENDENCY ORDER:
|
||||
|
||||
### STEP 2: Skill Invocation Sequence
|
||||
|
||||
Execute in strict dependency order. For each metadata component:
|
||||
Execute in strict dependency order. Invoke each skill once with all components for that metadata type.
|
||||
|
||||
1. **Check Metadata Type Registry**: Does a skill exist?
|
||||
2. **If YES (✅)**: Invoke the specialized skill with required parameters
|
||||
2. **If YES (✅)**: Invoke the specialized skill once with all components for that type
|
||||
3. **If NO (❌)**: Generate metadata directly using Metadata API knowledge
|
||||
4. **Handle Errors**: If skill invocation fails, log error and continue (don't block entire app)
|
||||
|
||||
**Invocation Pattern Example:**
|
||||
**Invocation Pattern (one invocation per metadata type):**
|
||||
|
||||
- For Custom Object → Invoke `salesforce-custom-object`
|
||||
- For Custom Field → Invoke `salesforce-custom-field`
|
||||
- For Validation Rule → Invoke `salesforce-validation-rule`
|
||||
- For Flow → Invoke `salesforce-flow`
|
||||
- For Custom Tab → Invoke `salesforce-custom-tab`
|
||||
- For FlexiPage → Invoke `salesforce-flexipage`
|
||||
- For Custom Application → Invoke `salesforce-custom-application`
|
||||
- For Permission Set → Invoke `generate-permission-set`
|
||||
- Custom Objects → Invoke `skills/generating-custom-object/SKILL.md` once with all objects
|
||||
- Custom Fields → Invoke `skills/generating-custom-field/SKILL.md` once with all fields
|
||||
- Validation Rules → Invoke `skills/generating-validation-rule/SKILL.md` once (if requested)
|
||||
- Flows → Invoke `skills/generating-flow/SKILL.md` once (if requested)
|
||||
- Custom Tabs → Invoke `skills/generating-custom-tab/SKILL.md` once with all tabs
|
||||
- FlexiPages → Invoke `skills/generating-flexipage/SKILL.md` once with all pages
|
||||
- Custom Application → Invoke `skills/generating-custom-application/SKILL.md` once
|
||||
- Permission Sets → Invoke `skills/generating-permission-set/SKILL.md` once with all permission sets
|
||||
|
||||
### STEP 3: Final Artifact Assembly
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-list-view
|
||||
name: generating-list-view
|
||||
description: Use this skill when users need to create, generate, or validate Salesforce List View metadata. Trigger when users mention list views, filtered record lists, creating views, setting up record columns, filtering records by criteria, or ask about list view visibility. Also use when users say things like "I need a view that shows...", "filter records by...", "create a list view for...", or when they're working with ListView XML files and need validation or troubleshooting.
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: generate-permission-set
|
||||
name: generating-permission-set
|
||||
description: Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.
|
||||
compatibility: Salesforce Metadata API v60.0+
|
||||
metadata:
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
name: salesforce-validation-rule
|
||||
name: generating-validation-rule
|
||||
description: Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formulas, or want to enforce business rules at the data layer. Always use this skill for any validation rule work.
|
||||
---
|
||||
|
||||
Loading…
Reference in New Issue
Block a user