@salesforce/afv-skills 1.27.0 → 1.29.0

package/skills/dx-code-analyzer-run/SKILL.md

@@ -1,19 +1,27 @@
 ---
 name: dx-code-analyzer-run
-description: "Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what specific rules mean. TRIGGER when: user says 'scan my code', 'check for security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', 'show only security violations', 'what is this rule', 'explain ApexCRUDViolation', 'filter results', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). Use this skill for scanning, exploring results, understanding rules, and listing available rules. DO NOT TRIGGER when: user wants to fix code without scanning, or asks ONLY about installation/configuration."
-allowed-tools: Read, Bash(sf code-analyzer), Bash(node), Bash(git diff), Bash(date), Write, Edit
+description: "Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', 'show security violations', 'what is this rule', 'explain ApexCRUDViolation', 'filter results', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). Use this skill for scanning, exploring results, and listing rules. DO NOT TRIGGER when: user asks only about installation/configuration (use dx-code-analyzer-configure), or wants to create a custom rule (use dx-code-analyzer-custom-rule-create)."
 metadata:
   version: "1.0"
-  argument-hint: "[target-path] [--engine pmd|eslint|cpd|retire-js|regex|flow|sfge|apexguru] [--category Security|Performance|BestPractices|...] [--severity 1-5] [--diff]"
+  relatedSkills:
+    - "dx-code-analyzer-configure"
+    - "dx-code-analyzer-custom-rule-create"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["git"]
+      semver: ">=2.0.0"
 ---
 
 # Running Code Analyzer Skill
 
-## ⚠️ CRITICAL: Mandatory Script Usage
+## CRITICAL: Mandatory Script Usage
 
 Every interaction with Code Analyzer results MUST go through the bundled scripts in `<skill_dir>/scripts/`. No exceptions.
 
-### ❌ WRONG — never do this:
+### WRONG — never do this:
 
 ```bash
 # WRONG: inline Python to parse results
@@ -31,7 +39,7 @@ Read tool → code-analyzer-results-*.json
 
 Also forbidden: `run_code_analyzer` and any `mcp__*` tool — Bash only.
 
-### ✅ RIGHT — always do this:
+### RIGHT — always do this:
 
 ```bash
 # Summarize scan results
@@ -67,11 +75,13 @@ Any aggregation, filter, or rank question ("which file has the most violations?"
 
 ## Overview
 
+> **Ecosystem:** This skill is part of a 3-skill Code Analyzer suite — `dx-code-analyzer-run` (scans & results) · `dx-code-analyzer-configure` (setup, config, CI/CD) · `dx-code-analyzer-custom-rule-create` (custom rule authoring).
+
 This skill translates natural-language requests ("scan for security issues", "check my changes") into the correct `sf code-analyzer run` command, executes scans across any combination of engines/targets/severities, and presents actionable results. When engine-provided fixes are available, it discovers them, asks for user confirmation, applies them safely, and offers verification. Use it for static analysis, security reviews, AppExchange certification, code-quality checks, and finding duplicates/vulnerabilities in Salesforce projects.
 
 **In scope:** running scans, parsing/filtering/ranking results, applying engine auto-fixes, diff-based scans, all output formats (JSON/HTML/SARIF/CSV/XML), describing/listing rules, scan-failure troubleshooting.
 
-**Out of scope:** installing/configuring `sf` or the plugin (→ `dx-code-analyzer-configure`), writing custom rules/engines, AI-generated fixes beyond engine-provided ones, deep refactoring, CI/CD setup (→ `dx-code-analyzer-configure`).
+**Out of scope:** installing/configuring `sf` or the plugin (→ `dx-code-analyzer-configure`), writing custom rules/engines (→ `dx-code-analyzer-custom-rule-create`), AI-generated fixes beyond engine-provided ones, deep refactoring, CI/CD setup (→ `dx-code-analyzer-configure`).
 
 **Allowed tools:** Bash (`sf code-analyzer`, `node`, `git diff`, `date`), Read, Write, Edit. **Forbidden:** any MCP tool, Agent tool, web tools, other skills, Python, `jq`, inline scripts/heredocs. This skill owns the complete scan-fix-verify-query-explain workflow end-to-end.
 
@@ -203,7 +213,7 @@ Use the **Bash tool only** — never the `run_code_analyzer` MCP tool.
 
 1. Generate the timestamp via Bash: `date +%Y%m%d-%H%M%S` → e.g. `20260512-143022`.
 2. Tell the user:
-   ```
+   ```text
    Starting scan...
    Results: ./code-analyzer-results-20260512-143022.json
    Log:     ./code-analyzer-results-20260512-143022.log
@@ -237,7 +247,7 @@ node "<skill_dir>/scripts/parse-results.js" "./code-analyzer-results-TIMESTAMP.j
 
 ### Presentation template
 
-```
+```text
 ## Scan Complete
 
 **Found X violations** across Y files.
@@ -296,7 +306,7 @@ node "<skill_dir>/scripts/discover-fixes.js" "./code-analyzer-results-TIMESTAMP.
 
 ### 6.3 Present + ASK (then STOP)
 
-```
+```text
 ### Engine-Provided Fixes Available
 **X of Y violations** have auto-fixes provided by the analysis engine:
 
@@ -327,7 +337,7 @@ node "<skill_dir>/scripts/summarize-fixes.js" "./code-analyzer-results-TIMESTAMP
 
 Then present:
 
-```
+```text
 ### Engine-Provided Fixes Applied Successfully ✓
 **Applied X auto-fixes across Y files.**
 
@@ -439,6 +449,29 @@ node "<skill_dir>/scripts/list-rules.js" "<selector>" [options]
 
 Filters: `--engine`, `--severity`, `--top` (default 100), `--count-only`. The script pre-validates selector tokens (catches typos like `secruity`) before calling the CLI. Presentation: `<skill_dir>/references/post-scan-workflows.md`.
 
+---
+## Cross-Skill Integration
+
+This skill is part of a 3-skill Code Analyzer ecosystem. Hand off cleanly rather than attempting work that belongs to another skill.
+
+### When THIS skill delegates to `dx-code-analyzer-configure`:
+
+- Pre-flight check fails (CLI missing, plugin not installed, engine prereqs broken) → stop, delegate, return here after fix
+- User asks to set up CI/CD, edit `code-analyzer.yml`, change severities, or disable engines → delegate entirely
+
+### When THIS skill delegates to `dx-code-analyzer-custom-rule-create`:
+
+- User asks to create a new rule, write XPath, write a regex rule, or enforce a pattern not covered by built-in rules → delegate entirely. Do NOT attempt to create rules here.
+
+### When other skills hand off HERE:
+
+- `dx-code-analyzer-configure` completes setup → proceed with scan (Step 1–5)
+- `dx-code-analyzer-custom-rule-create` finishes creating a rule → proceed with scan targeting the new rule (e.g., `--rule-selector pmd:<RuleName>`) to verify it works
+
+### Ownership boundary
+
+This skill owns the complete **scan → explore → fix** workflow end-to-end. It does NOT own installation, config file management, or rule authoring.
+
 ---
 
 ## Constraints & Gotchas

package/skills/dx-code-analyzer-run/examples/command-variations.md

@@ -297,7 +297,7 @@ sf code-analyzer run \
 
 ## Anti-Patterns (DO NOT USE)
 
-### ❌ Using `--format` flag
+### Using `--format` flag
 ```bash
 # WRONG - v3 syntax, does not exist in v4+
 sf code-analyzer run --format json
@@ -306,7 +306,7 @@ sf code-analyzer run --format json
 
 ---
 
-### ❌ Using `$TIMESTAMP` variable in command
+### Using `$TIMESTAMP` variable in command
 ```bash
 # WRONG - variable substitution fails in permission prompts
 sf code-analyzer run --output-file "./results-${TIMESTAMP}.json"
@@ -315,7 +315,7 @@ sf code-analyzer run --output-file "./results-${TIMESTAMP}.json"
 
 ---
 
-### ❌ Running in background for long scans
+### Running in background for long scans
 ```bash
 # WRONG - loses output stream
 sf code-analyzer run --rule-selector sfge &
@@ -324,7 +324,7 @@ sf code-analyzer run --rule-selector sfge &
 
 ---
 
-### ❌ Partial rule names
+### Partial rule names
 ```bash
 # WRONG - returns 0 results
 sf code-analyzer run --rule-selector "no-hardcoded-values"

package/skills/dx-org-permission-set-assign/SKILL.md

@@ -12,7 +12,7 @@ Assigns one or more permission sets to org users using `sf org assign permset`.
 
 ---
 
-## ⚠️ Tool Restrictions
+## Tool Restrictions
 
 **Use ONLY the Bash tool** to execute `sf org assign permset`. Do NOT use MCP tools like `assign_permission_set` — ignore them completely.
 

package/skills/experience-lwc-generate/references/async-notification-patterns.md

@@ -617,7 +617,7 @@ connectedCallback() {
 
 ## Best Practices
 
-### DO ✅
+### DO
 
 | Practice | Reason |
 |----------|--------|
@@ -627,7 +627,7 @@ connectedCallback() {
 | Use `refreshApex` after events | Keeps wire data in sync |
 | Set reasonable replay ID | `-1` for real-time, `-2` for recovery |
 
-### DON'T ❌
+### DON'T
 
 | Anti-Pattern | Problem |
 |--------------|---------|

package/skills/experience-lwc-generate/references/state-management.md

@@ -511,7 +511,7 @@ export default class ComposedStateComponent extends LightningElement {
 
 ## Anti-Patterns to Avoid
 
-### ❌ BAD: Mutating Objects In Place
+### BAD: Mutating Objects In Place
 
 ```javascript
 // DON'T - won't trigger reactivity
@@ -519,7 +519,7 @@ this.user.name = 'New Name';
 this.items.push(newItem);
 ```
 
-### ✅ GOOD: Create New References
+### GOOD: Create New References
 
 ```javascript
 // DO - triggers reactivity
@@ -527,7 +527,7 @@ this.user = { ...this.user, name: 'New Name' };
 this.items = [...this.items, newItem];
 ```
 
-### ❌ BAD: Heavy Computation in Getters
+### BAD: Heavy Computation in Getters
 
 ```javascript
 // DON'T - runs every render cycle
@@ -539,7 +539,7 @@ get expensiveComputation() {
 }
 ```
 
-### ✅ GOOD: Cache Computed Values
+### GOOD: Cache Computed Values
 
 ```javascript
 _cachedResult;
@@ -558,7 +558,7 @@ get optimizedComputation() {
 }
 ```
 
-### ❌ BAD: Forgetting to Unsubscribe
+### BAD: Forgetting to Unsubscribe
 
 ```javascript
 // DON'T - memory leak
@@ -567,7 +567,7 @@ connectedCallback() {
 }
 ```
 
-### ✅ GOOD: Clean Up Subscriptions
+### GOOD: Clean Up Subscriptions
 
 ```javascript
 // DO - proper cleanup

package/skills/experience-lwc-generate/references/template-anti-patterns.md

@@ -26,7 +26,7 @@ This guide documents systematic errors in Lightning Web Component templates, wit
 
 **Critical Rule**: LWC templates do NOT support JavaScript expressions. Only property references are allowed.
 
-### ❌ BAD: Arithmetic in Template
+### BAD: Arithmetic in Template
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -37,7 +37,7 @@ This guide documents systematic errors in Lightning Web Component templates, wit
 </template>
 ```
 
-### ✅ GOOD: Use Getters
+### GOOD: Use Getters
 
 ```javascript
 // component.js
@@ -69,7 +69,7 @@ export default class PriceCalculator extends LightningElement {
 </template>
 ```
 
-### ❌ BAD: String Concatenation in Template
+### BAD: String Concatenation in Template
 
 ```html
 <!-- DOES NOT WORK -->
@@ -79,7 +79,7 @@ export default class PriceCalculator extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Computed Properties
+### GOOD: Computed Properties
 
 ```javascript
 // component.js
@@ -112,7 +112,7 @@ export default class Greeting extends LightningElement {
 
 **Critical Rule**: Ternary operators (`condition ? a : b`) are NOT allowed in LWC templates.
 
-### ❌ BAD: Ternary in Template
+### BAD: Ternary in Template
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -123,7 +123,7 @@ export default class Greeting extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Use Getters for Conditional Values
+### GOOD: Use Getters for Conditional Values
 
 ```javascript
 // component.js
@@ -155,7 +155,7 @@ export default class StatusDisplay extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Use if:true/if:false for Conditional Rendering
+### GOOD: Use if:true/if:false for Conditional Rendering
 
 ```html
 <!-- component.html -->
@@ -189,7 +189,7 @@ get hasCount() {
 
 **Critical Rule**: Object literals (`{}`) cannot be passed directly as attribute values.
 
-### ❌ BAD: Inline Object Literals
+### BAD: Inline Object Literals
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -206,7 +206,7 @@ get hasCount() {
 </template>
 ```
 
-### ✅ GOOD: Define Objects in JavaScript
+### GOOD: Define Objects in JavaScript
 
 ```javascript
 // component.js
@@ -237,7 +237,7 @@ export default class ParentComponent extends LightningElement {
 </template>
 ```
 
-### ❌ BAD: Inline Array Literals
+### BAD: Inline Array Literals
 
 ```html
 <!-- DOES NOT WORK -->
@@ -246,7 +246,7 @@ export default class ParentComponent extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Define Arrays in JavaScript
+### GOOD: Define Arrays in JavaScript
 
 ```javascript
 // component.js
@@ -272,7 +272,7 @@ export default class ColorPicker extends LightningElement {
 
 **Critical Rule**: No method calls, comparisons, or logical operators in templates.
 
-### ❌ BAD: Method Calls in Template
+### BAD: Method Calls in Template
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -284,7 +284,7 @@ export default class ColorPicker extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Use Getters for Transformations
+### GOOD: Use Getters for Transformations
 
 ```javascript
 // component.js
@@ -322,7 +322,7 @@ export default class DataDisplay extends LightningElement {
 </template>
 ```
 
-### ❌ BAD: Comparisons in Template
+### BAD: Comparisons in Template
 
 ```html
 <!-- DOES NOT WORK -->
@@ -337,7 +337,7 @@ export default class DataDisplay extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Getter-Based Comparisons
+### GOOD: Getter-Based Comparisons
 
 ```javascript
 // component.js
@@ -363,7 +363,7 @@ get isActive() {
 </template>
 ```
 
-### ❌ BAD: Logical Operators in Template
+### BAD: Logical Operators in Template
 
 ```html
 <!-- DOES NOT WORK -->
@@ -378,7 +378,7 @@ get isActive() {
 </template>
 ```
 
-### ✅ GOOD: Computed Boolean Properties
+### GOOD: Computed Boolean Properties
 
 ```javascript
 // component.js
@@ -408,7 +408,7 @@ get isNotLoading() {
 
 ## 5. Event Handler Mistakes
 
-### ❌ BAD: Inline Event Handlers with Arguments
+### BAD: Inline Event Handlers with Arguments
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -419,7 +419,7 @@ get isNotLoading() {
 </template>
 ```
 
-### ✅ GOOD: Handler Functions with Data Attributes
+### GOOD: Handler Functions with Data Attributes
 
 ```html
 <!-- component.html -->
@@ -449,7 +449,7 @@ handleChange(event) {
 }
 ```
 
-### ❌ BAD: Event Binding with bind()
+### BAD: Event Binding with bind()
 
 ```html
 <!-- DOES NOT WORK -->
@@ -458,7 +458,7 @@ handleChange(event) {
 </template>
 ```
 
-### ✅ GOOD: Use Data Attributes for Context
+### GOOD: Use Data Attributes for Context
 
 ```html
 <!-- component.html -->
@@ -491,7 +491,7 @@ handleItemClick(event) {
 
 ## 6. Iteration Anti-Patterns
 
-### ❌ BAD: Missing Key in Iteration
+### BAD: Missing Key in Iteration
 
 ```html
 <!-- LLM forgets key - causes rendering issues -->
@@ -502,7 +502,7 @@ handleItemClick(event) {
 </template>
 ```
 
-### ✅ GOOD: Always Include Key
+### GOOD: Always Include Key
 
 ```html
 <!-- component.html -->
@@ -513,7 +513,7 @@ handleItemClick(event) {
 </template>
 ```
 
-### ❌ BAD: Using Index as Key
+### BAD: Using Index as Key
 
 ```html
 <!-- Anti-pattern: index can cause issues with reordering -->
@@ -524,7 +524,7 @@ handleItemClick(event) {
 </template>
 ```
 
-### ✅ GOOD: Use Unique Identifier as Key
+### GOOD: Use Unique Identifier as Key
 
 ```javascript
 // If items don't have unique IDs, generate them
@@ -545,7 +545,7 @@ connectedCallback() {
 </template>
 ```
 
-### ❌ BAD: Nested Iteration Without Proper Keys
+### BAD: Nested Iteration Without Proper Keys
 
 ```html
 <!-- PROBLEMATIC -->
@@ -562,7 +562,7 @@ connectedCallback() {
 </template>
 ```
 
-### ✅ GOOD: Compound Keys for Nested Iteration
+### GOOD: Compound Keys for Nested Iteration
 
 ```javascript
 // component.js
@@ -595,7 +595,7 @@ get processedCategories() {
 
 ## 7. Conditional Rendering Issues
 
-### ❌ BAD: if:true on Non-Boolean Values
+### BAD: if:true on Non-Boolean Values
 
 ```html
 <!-- LLM assumes truthy/falsy works like JS - it doesn't always -->
@@ -612,7 +612,7 @@ get processedCategories() {
 </template>
 ```
 
-### ✅ GOOD: Explicit Boolean Conversion
+### GOOD: Explicit Boolean Conversion
 
 ```javascript
 // component.js
@@ -638,7 +638,7 @@ get hasCount() {
 </template>
 ```
 
-### ❌ BAD: Multiple Conditions Without Else
+### BAD: Multiple Conditions Without Else
 
 ```html
 <!-- Verbose and error-prone -->
@@ -655,7 +655,7 @@ get hasCount() {
 </template>
 ```
 
-### ✅ GOOD: Use a State Getter
+### GOOD: Use a State Getter
 
 ```javascript
 // component.js
@@ -694,7 +694,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 
 ## 8. Slot and Composition Errors
 
-### ❌ BAD: Named Slot with Wrong Syntax
+### BAD: Named Slot with Wrong Syntax
 
 ```html
 <!-- LLM uses Vue/React slot syntax -->
@@ -711,7 +711,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 </template>
 ```
 
-### ✅ GOOD: LWC Slot Syntax
+### GOOD: LWC Slot Syntax
 
 ```html
 <!-- Parent component using slots -->
@@ -746,7 +746,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 
 ## 9. Data Binding Mistakes
 
-### ❌ BAD: Two-Way Binding Syntax
+### BAD: Two-Way Binding Syntax
 
 ```html
 <!-- LLM uses Angular/Vue two-way binding - doesn't exist in LWC -->
@@ -757,7 +757,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 </template>
 ```
 
-### ✅ GOOD: One-Way Binding with Event Handler
+### GOOD: One-Way Binding with Event Handler
 
 ```html
 <!-- component.html -->
@@ -790,7 +790,7 @@ handleInputChange(event) {
 }
 ```
 
-### ❌ BAD: Direct Property Mutation in Template
+### BAD: Direct Property Mutation in Template
 
 ```html
 <!-- Cannot mutate in template -->
@@ -799,7 +799,7 @@ handleInputChange(event) {
 </template>
 ```
 
-### ✅ GOOD: Mutate in Handler
+### GOOD: Mutate in Handler
 
 ```javascript
 // component.js
@@ -821,7 +821,7 @@ handleIncrement() {
 
 ## 10. Style and Class Binding
 
-### ❌ BAD: Dynamic Styles in Template
+### BAD: Dynamic Styles in Template
 
 ```html
 <!-- LLM uses React/Vue style binding - doesn't work in LWC -->
@@ -836,7 +836,7 @@ handleIncrement() {
 </template>
 ```
 
-### ✅ GOOD: CSS Custom Properties (Recommended)
+### GOOD: CSS Custom Properties (Recommended)
 
 ```javascript
 // component.js
@@ -864,7 +864,7 @@ renderedCallback() {
 </template>
 ```
 
-### ✅ GOOD: Computed Style String (When Necessary)
+### GOOD: Computed Style String (When Necessary)
 
 ```javascript
 // component.js
@@ -880,7 +880,7 @@ get dynamicStyle() {
 </template>
 ```
 
-### ❌ BAD: Dynamic Class with Expression
+### BAD: Dynamic Class with Expression
 
 ```html
 <!-- DOES NOT WORK -->
@@ -890,7 +890,7 @@ get dynamicStyle() {
 </template>
 ```
 
-### ✅ GOOD: Computed Class String
+### GOOD: Computed Class String
 
 ```javascript
 // component.js

package/skills/experience-ui-bundle-agentforce-client-generate/references/constraints.md

@@ -65,19 +65,19 @@ When updating an existing component:
 
 ## Examples
 
-### ❌ Wrong - Using containerStyle
+### Wrong - Using containerStyle
 
 ```tsx
 <AgentforceConversationClient agentId="0Xx..." containerStyle={{ width: 420, height: 600 }} />
 ```
 
-### ✅ Correct - Using width/height directly
+### Correct - Using width/height directly
 
 ```tsx
 <AgentforceConversationClient agentId="0Xx..." width="420px" height="600px" />
 ```
 
-### ❌ Wrong - Creating CSS file
+### Wrong - Creating CSS file
 
 ```css
 /* agent-styles.css */
@@ -93,7 +93,7 @@ import "./agent-styles.css";
 <AgentforceConversationClient className="agentforce-chat" />;
 ```
 
-### ✅ Correct - Using styleTokens
+### Correct - Using styleTokens
 
 ```tsx
 <AgentforceConversationClient
@@ -105,7 +105,7 @@ import "./agent-styles.css";
 />
 ```
 
-### ❌ Wrong - Creating style tag
+### Wrong - Creating style tag
 
 ```tsx
 <>
@@ -114,7 +114,7 @@ import "./agent-styles.css";
 </>
 ```
 
-### ✅ Correct - Using styleTokens
+### Correct - Using styleTokens
 
 ```tsx
 <AgentforceConversationClient
@@ -125,10 +125,10 @@ import "./agent-styles.css";
 />
 ```
 
-### ❌ Wrong - Editing implementation file
+### Wrong - Editing implementation file
 
 Reading or editing: `node_modules/@salesforce/ui-bundle-template-feature-react-agentforce-conversation-client/src/AgentforceConversationClient.tsx`
 
-### ✅ Correct - Editing usage file
+### Correct - Editing usage file
 
 Reading and editing: usage files where the component is imported and used (for example, `src/app.tsx`, a route component, or a feature page)

package/skills/experience-ui-bundle-custom-app-generate/SKILL.md

@@ -55,10 +55,10 @@ Use the default template in the doc below. Values in `{braces}` are resolved pro
 
 | Metadata Type | Template Reference |
 |--------------|-------------------|
-| CustomApplication | [configure-metadata-custom-application.md](docs/configure-metadata-custom-application.md) |
+| CustomApplication | [configure-metadata-custom-application.md](references/configure-metadata-custom-application.md) |
 
 ### Execution Note for Step 4: Load and use the doc
-- Agents MUST read the full contents of the docs/*.md file referenced in Step 4 before attempting to populate metadata fields.
+- Agents MUST read the full contents of the references/*.md file referenced in Step 4 before attempting to populate metadata fields.
 - Read the file in full, replace placeholders (e.g. `{appName}`) with the resolved values, then use the expanded template to populate the metadata XML content.
 - If Step 2 determined the older field names apply, substitute `<uiBundle>` with `<webApplication>` in the generated output.
 

package/skills/experience-ui-bundle-frontend-generate/SKILL.md

@@ -13,9 +13,9 @@ Determine which category the request falls into:
 
 | Category | Examples | Implementation Guide |
 |----------|----------|---------------------|
-| **Page** | New routed page (contacts, dashboard, settings) | `implementation/page.md` |
-| **Header / Footer** | Site-wide nav bar, footer, branding | `implementation/header-footer.md` |
-| **Component** | Widget, card, table, form, dialog | `implementation/component.md` |
+| **Page** | New routed page (contacts, dashboard, settings) | `references/page.md` |
+| **Header / Footer** | Site-wide nav bar, footer, branding | `references/header-footer.md` |
+| **Component** | Widget, card, table, form, dialog | `references/component.md` |
 
 ---