@salesforce/afv-skills 1.22.0 → 1.24.0

package/skills/generating-ui-bundle-site/docs/configure-metadata-digital-experience.md

@@ -1,40 +0,0 @@
-# Configure Metadata: DigitalExperience (sfdc_cms__site)
-
-## Purpose
-These configuration files create **net-new, default** DigitalExperience content records (`sfdc_cms__site` type) for a Digital Experience React Site. They are not intended to edit or modify existing DigitalExperience content. Use these templates only when provisioning a brand-new React site.
-
-The `appContainer: true` field in `content.json` is what makes this a React site rather than a standard LWR site. The `appSpace` field should **be left empty if the UIBundle metadata record does not already exist**. When the UIBundle exists, populate the `appSpace` value following the format `{namespace}__{developerName}` to match the deployed `UIBundle` metadata record.
-
-## File Location
-The DigitalExperience directory contains only `_meta.json` and `content.json`. Do not create any directories other than `sfdc_cms__site` inside the bundle.
-
-```
-digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/_meta.json
-digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/content.json
-```
-
-## Default Templates
-### `_meta.json`
-```json
-{
-  "apiName": "{siteName}1",
-  "path": "",
-  "type": "sfdc_cms__site"
-}
-```
-
-### `content.json`
-```json
-{
-  "type": "sfdc_cms__site",
-  "title": "{siteName}",
-  "urlName": "{siteUrlPathPrefix}",
-  "contentBody": {
-    "authenticationType": "AUTHENTICATED_WITH_PUBLIC_ACCESS_ENABLED",
-    "appContainer": true,
-    "appSpace": ""
-  }
-}
-```
-
-**Note:** Leave `appSpace` empty (`""`) if the UIBundle does not exist. If the UIBundle metadata record is already deployed, populate it with `"{appNamespace}__{appDevName}"`.

package/skills/generating-ui-bundle-site/docs/configure-metadata-network.md

@@ -1,72 +0,0 @@
-# Configure Metadata: Network
-
-## Purpose
-This configuration file creates a **net-new, default** Network metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing Network record. Use this template only when provisioning a brand-new React site.
-
-## File Location
-```
-networks/{siteName}.network-meta.xml
-```
-
-## Default Template
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<Network xmlns="http://soap.sforce.com/2006/04/metadata">
-    <allowInternalUserLogin>false</allowInternalUserLogin>
-    <allowMembersToFlag>false</allowMembersToFlag>
-    <changePasswordTemplate>unfiled$public/CommunityChangePasswordEmailTemplate</changePasswordTemplate>
-    <disableReputationRecordConversations>true</disableReputationRecordConversations>
-    <emailSenderAddress>admin@company.com</emailSenderAddress>
-    <emailSenderName>{siteName}</emailSenderName>
-    <embeddedLoginEnabled>false</embeddedLoginEnabled>
-    <enableApexCDNCaching>true</enableApexCDNCaching>
-    <enableCustomVFErrorPageOverrides>false</enableCustomVFErrorPageOverrides>
-    <enableDirectMessages>true</enableDirectMessages>
-    <enableExpFriendlyUrlsAsDefault>false</enableExpFriendlyUrlsAsDefault>
-    <enableExperienceBundleBasedSnaOverrideEnabled>true</enableExperienceBundleBasedSnaOverrideEnabled>
-    <enableGuestChatter>{enableGuestAccess}</enableGuestChatter>
-    <enableGuestFileAccess>false</enableGuestFileAccess>
-    <enableGuestMemberVisibility>false</enableGuestMemberVisibility>
-    <enableImageOptimizationCDN>true</enableImageOptimizationCDN>
-    <enableInvitation>false</enableInvitation>
-    <enableKnowledgeable>false</enableKnowledgeable>
-    <enableLWRExperienceConnectedApp>false</enableLWRExperienceConnectedApp>
-    <enableMemberVisibility>false</enableMemberVisibility>
-    <enableNicknameDisplay>true</enableNicknameDisplay>
-    <enablePrivateMessages>false</enablePrivateMessages>
-    <enableReputation>false</enableReputation>
-    <enableShowAllNetworkSettings>false</enableShowAllNetworkSettings>
-    <enableSiteAsContainer>true</enableSiteAsContainer>
-    <enableTalkingAboutStats>true</enableTalkingAboutStats>
-    <enableTopicAssignmentRules>true</enableTopicAssignmentRules>
-    <enableTopicSuggestions>false</enableTopicSuggestions>
-    <enableUpDownVote>false</enableUpDownVote>
-    <forgotPasswordTemplate>unfiled$public/CommunityForgotPasswordEmailTemplate</forgotPasswordTemplate>
-    <gatherCustomerSentimentData>false</gatherCustomerSentimentData>
-    <headlessForgotPasswordTemplate>unfiled$public/CommunityHeadlessForgotPasswordTemplate</headlessForgotPasswordTemplate>
-    <headlessRegistrationTemplate>unfiled$public/CommunityHeadlessRegistrationTemplate</headlessRegistrationTemplate>
-    <networkMemberGroups>
-        <profile>admin</profile>
-    </networkMemberGroups>
-    <networkPageOverrides>
-        <changePasswordPageOverrideSetting>Standard</changePasswordPageOverrideSetting>
-        <forgotPasswordPageOverrideSetting>Designer</forgotPasswordPageOverrideSetting>
-        <homePageOverrideSetting>Designer</homePageOverrideSetting>
-        <loginPageOverrideSetting>Designer</loginPageOverrideSetting>
-        <selfRegProfilePageOverrideSetting>Designer</selfRegProfilePageOverrideSetting>
-    </networkPageOverrides>
-    <newSenderAddress>admin@company.com</newSenderAddress>
-    <picassoSite>{siteName}1</picassoSite>
-    <selfRegistration>false</selfRegistration>
-    <sendWelcomeEmail>true</sendWelcomeEmail>
-    <site>{siteName}</site>
-    <siteArchiveStatus>NotArchived</siteArchiveStatus>
-    <status>Live</status>
-    <tabs>
-        <defaultTab>home</defaultTab>
-        <standardTab>Chatter</standardTab>
-    </tabs>
-    <urlPathPrefix>{siteUrlPathPrefix}vforcesite</urlPathPrefix>
-    <welcomeTemplate>unfiled$public/CommunityWelcomeEmailTemplate</welcomeTemplate>
-</Network>
-```

package/skills/generating-ui-bundle-site/docs/update-site-urls.md

@@ -1,100 +0,0 @@
-# Updating Experience Site URLs
-
-Experience sites have a three-component architecture with two distinct URL patterns. Understanding this structure is critical when updating site URLs.
-
-## Architecture Overview
-
-Every Salesforce Experience Site consists of three components:
-
-1. **Network** (metadata: `Network`) - Network configuration
-2. **ChatterNetwork Site** (metadata: `CustomSite`) - Legacy site and proxy core site services
-3. **ChatterNetworkPicasso Site** (metadata: `DigitalExperienceConfig` + `DigitalExperienceBundle`) - Customer-facing pages and content
-
-## URL Pattern
-
-These three components use **two different URLs**:
-
-- **Primary URL** (ChatterNetworkPicasso): Used for customer-facing pages
-  - Defined in: `DigitalExperienceConfig` → `<urlPathPrefix>`
-  - Example: `mysite`
-
-- **Secondary URL** (Network + CustomSite): Used for legacy authentication endpoints and other services
-  - Defined in: `Network` → `<urlPathPrefix>` AND `CustomSite` → `<urlPathPrefix>`
-  - Example: `mysitevforcesite`
-  - **Must be synchronized** - both files must have identical values
-
-By default, Salesforce differentiates these URLs by appending `vforcesite` suffix to the Network/CustomSite URL.
-
-## URL Update Workflow
-
-When updating site URLs, follow this workflow:
-
-### Step 1: Discover All URL References
-
-Search for all occurrences of `urlPathPrefix` across the project metadata files.
-
-**For agents**: Use the `search_files` tool with these parameters:
-- path: `force-app/main/default`
-- regex: `urlPathPrefix`
-- file_pattern: `*.xml`
-
-**For humans**: Use your IDE's search functionality or command line tools:
-```bash
-# Using grep
-grep -r "urlPathPrefix" force-app/main/default --include="*.xml"
-
-# Using VS Code: Ctrl+Shift+F (Windows/Linux) or Cmd+Shift+F (Mac)
-# Search for: urlPathPrefix
-# Files to include: *.xml
-```
-
-### Step 2: Identify URL Groups
-
-Determine which files belong to which URL group:
-
-- **Primary URL Group**: `DigitalExperienceConfig`
-- **Secondary URL Group**: `Network` AND `CustomSite`
-
-### Step 3: Update URLs Consistently
-
-Update the `<urlPathPrefix>` value in each file:
-
-- **DigitalExperienceConfig**: Update to new primary URL
-- **Network**: Update to new secondary URL (typically primary URL + `vforcesite`)
-- **CustomSite**: Update to **same value as Network** (must be synchronized)
-
-### Step 4: Validate Naming Convention
-
-Ensure URL values follow best practices:
-- Use lowercase letters only
-- Avoid special characters except hyphens where appropriate
-- Keep URLs concise and meaningful
-
-### Step 5: Verify Consistency
-
-Before deploying, confirm:
-- [ ] Primary URL in `DigitalExperienceConfig` is set correctly
-- [ ] Secondary URL in `Network` matches `CustomSite` exactly
-- [ ] URLs are properly differentiated (typically via suffix)
-- [ ] All URL values follow naming conventions
-
-## Example URL Configuration
-
-```
-ChatterNetworkPicasso Site (Primary):
-  DigitalExperienceConfig: <urlPathPrefix>bestsupport</urlPathPrefix>
-
-Network + ChatterNetwork Site (Secondary):
-  Network:    <urlPathPrefix>bestsupportvforcesite</urlPathPrefix>
-  CustomSite: <urlPathPrefix>bestsupportvforcesite</urlPathPrefix>
-```
-
-## Common Pitfalls to Avoid
-
-❌ **Don't** update only one or two files - all three must be updated  
-❌ **Don't** use different values in Network and CustomSite  
-❌ **Don't** use the same URL for both Primary and Secondary groups  
-❌ **Don't** skip the discovery step with `search_files`  
-✅ **Do** use `search_files` to find all occurrences first  
-✅ **Do** maintain URL differentiation between the two groups  
-✅ **Do** follow lowercase naming conventions

package/skills/generating-validation-rule/SKILL.md

@@ -1,74 +0,0 @@
----
-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."
-metadata:
-  version: "1.0"
----
-
-## When to Use This Skill
-
-Use this skill when you need to:
-- Create validation rules to enforce data quality
-- Prevent invalid records from being saved
-- Generate validation rule metadata with formulas
-- Add business logic validation to objects
-- Troubleshoot deployment errors related to validation rules
-
-## Specification
-
-# ValidationRule Metadata Specification
-
-### 📋 Overview
-Validation Rules are declarative metadata components used to enforce data quality and business logic in Salesforce. They evaluate a formula expression when a record is saved and prevent the save operation if the expression returns TRUE.
-
-### 🎯 Purpose
--Enforce business rules at the data layer
--Prevent invalid or incomplete records from being saved
--Display meaningful error messages to guide users
-
-### ⚙️ Required Properties
-
-#### Core Validation Rule Properties
-
-- **fullName**
-    - The unique API name of the validation rule
-    - Must start with a letter
-        - Can contain letters, numbers, and underscores
-    - Cannot end with an underscore
-    - Cannot contain consecutive underscores
-    - Cannot exceed 40 character.
-
-- **active**
-  -Indicates whether the validation rule is enabled
-  true → Rule is enforced
-  false → Rule is inactive
-
-- **errorConditionFormula**
-- The logical formula that evaluates record data
-- Must return TRUE or FALSE
-- If TRUE, the validation rule triggers an error
-
-- **errorMessage**
-    - The message displayed to the user when validation fails
-- Maximum length: 255 characters
-
-### Specific Function Guidelines
-- TEXT - TEXT() function MUST NOT be used with Text fields, to fix this you can just remove the TEXT() function.
-- CASE - In salesforce CASE() function, last parameter is the default value. Admins often miss to provide this and number of parameters to CASE() function are always even.
-- VALUE - VALUE() function should only be used with Text fields. If a number is being used as a parameter to the VALUE() function, remove the VALUE() function.
-- DAY - DAY() function should only be used with Date fields. If a Datetime field is being used as a parameter to the DAY() function, convert it into a Date first.
-- MONTH - MONTH() function should only be used with Date fields. If a Datetime field is being used as a parameter to the MONTH() function, convert it into a Date first.
-- DATEVALUE - DATEVALUE() function should only be used with DateTime fields. If a Date is being used as a parameter to the DATEVALUE() function, remove the DATEVALUE() function.
-- ISPICKVAL - If checking equality of a picklist type field, the function ISPICKVAL() MUST be used.
-- ISCHANGE - Use ISCHANGE() function to check the value of a record has changed.
-
-### Critical Rules
-1. Formula XML Handling(MOST COMMON ERROR)
-    - ANY errorConditionFormula containing XML tags MUST be inside a CDATA section in the metadata XML.
-
-2. Interpretation of "Update" Instructions. When receiving instructions to modify a formula, distinguish between a replacement and an addition:
-    - "Update the formula to [Action]": Completely replace the existing formula logic with the new requirement.
-    - "Update the formula to also [Action]": Keep the existing logic and append the new requirement (usually by wrapping the logic in an AND() or OR() function).
-
-3. File Format Requirement
-    - Validation rule files MUST always use the `.validationRule-meta.xml` extension.

package/skills/generating-visual-diagrams/CREDITS.md

@@ -1,80 +0,0 @@
-# Credits & Acknowledgments
-
-This skill leverages cutting-edge AI technologies and tools to enable visual content generation in Salesforce development workflows.
-
----
-
-## Technologies & Tools
-
-### Google Gemini
-
-Key capabilities:
-- Gemini 3 Pro multimodal AI model
-- Image generation via Nano Banana Pro extension
-- Code review and analysis capabilities
-- Documentation research and summarization
-
-### Gemini CLI
-
-Key features:
-- Command-line access to Gemini models
-- Extension support (Nano Banana)
-- Non-interactive mode with --yolo flag
-- JSON output for programmatic use
-
-### Nano Banana Pro
-
-Gemini image generation extension.
-
-Key features:
-- High-quality image generation
-- ERD and diagram creation
-- UI/UX mockup generation
-- Architecture visualization
-
----
-
-## Display Technologies
-
-### timg
-
-Terminal image viewer.
-
-Key features:
-- Kitty graphics protocol support
-- Multiple format support (PNG, JPG, GIF)
-- Inline terminal display
-
-### Kitty Graphics Protocol
-
-High-fidelity image rendering protocol for modern terminals.
-
-Key features:
-- High-fidelity image display in terminals
-- Supported by Ghostty, Kitty, WezTerm
-- Enables visual content in CLI workflows
-
-### Ghostty Terminal
-
-Modern GPU-accelerated terminal emulator.
-
-Key features:
-- Kitty graphics protocol support
-- Cross-platform (macOS, Linux)
-- High performance rendering
-
----
-
-## Salesforce Resources
-
-### Salesforce Lightning Design System (SLDS)
-
-- Design patterns for LWC mockups
-- Color palettes and typography
-- Component specifications
-
-### Salesforce Developers Platform
-
-- API documentation
-- Best practices guides
-- Platform architecture references

package/skills/generating-visual-diagrams/README.md

@@ -1,83 +0,0 @@
-# generating-visual-diagrams
-
-AI-powered visual content generation for Salesforce development. Generate ERD diagrams, LWC mockups, and architecture visuals using Gemini 3 Pro Image (Nano Banana Pro).
-
-## Features
-
-- **Visual ERD Generation**: Create actual rendered ERD diagrams (not just Mermaid code)
-- **LWC/UI Mockups**: Generate wireframes and component mockups following SLDS
-- **Gemini Code Review**: Parallel code review while Claude continues working
-- **Documentation Research**: Parallel Salesforce documentation research via Gemini
-
-## Prerequisites
-
-**IMPORTANT**: Run the prerequisites check before using this skill:
-
-```bash
-scripts/check-prerequisites.sh
-```
-
-| Requirement | Description | How to Install |
-|-------------|-------------|----------------|
-| **Ghostty Terminal** | Required for Kitty graphics protocol | Download from the Ghostty website |
-| **GEMINI_API_KEY** | Personal API key for Nano Banana Pro | Generate via Google AI Studio |
-| **Gemini CLI** | Command-line interface for Gemini | `npm install -g @google/gemini-cli` |
-| **Nano Banana Extension** | Image generation extension | `gemini extensions install nanobanana` |
-| **timg** | Terminal image viewer with Kitty support | `brew install timg` |
-
-## Quick Start
-
-### 1. Set up your API key
-
-Add to `~/.zshrc`:
-```bash
-export GEMINI_API_KEY="your-personal-api-key"
-export NANOBANANA_MODEL=gemini-3-pro-image-preview
-```
-
-### 2. Invoke the skill
-
-```
-Skill: generating-visual-diagrams
-Request: "Generate an ERD diagram showing Account, Contact, and Opportunity relationships"
-```
-
-### 3. View the result
-
-Images are displayed inline using Kitty graphics protocol (Ghostty) or via Claude's multimodal vision using the Read tool.
-
-## Use Cases
-
-| Use Case | Example Request |
-|----------|-----------------|
-| ERD Diagrams | "Generate a visual ERD for Account, Contact, Opportunity" |
-| LWC Mockups | "Create a mockup for an Account list datatable component" |
-| Code Review | "Get Gemini's review of this Apex trigger" |
-| Doc Research | "Research the Flow best practices in Salesforce docs" |
-
-## Cross-Skill Integration
-
-| Related Skill | When to Use |
-|---------------|-------------|
-| generating-mermaid-diagrams | Convert Mermaid to visual rendering |
-| generating-custom-object | Query object/field data before generating ERDs |
-| generating-lwc-components | Generate mockups for LWC components |
-| generating-apex | Review Apex code via Gemini sub-agent |
-
-## Documentation
-
-- [Gemini CLI Setup](references/gemini-cli-setup.md)
-
-## Security Notes
-
-**NEVER commit your GEMINI_API_KEY to version control**
-
-- Store API key in `~/.zshrc` only (not in project files)
-- The key is personal and tied to your Google account billing
-
-## Requirements
-
-- Ghostty terminal (for Kitty graphics)
-- Gemini CLI with Nano Banana extension
-- GEMINI_API_KEY environment variable
-- timg (for terminal image display)

package/skills/generating-visual-diagrams/SKILL.md

@@ -1,207 +0,0 @@
----
-name: generating-visual-diagrams
-description: "AI-powered image generation for Salesforce visuals via Nano Banana Pro. Use this skill when the user needs rendered PNG/SVG output such as visual ERDs (Entity Relationship Diagrams), UI mockups, wireframes, or architecture illustrations. TRIGGER when: user asks for PNG/SVG output, UI mockups, wireframes, visual ERDs, or says \"generate image\" / \"create mockup\". DO NOT TRIGGER when: text-based Mermaid diagrams (use generating-mermaid-diagrams), or non-visual documentation tasks."
-metadata:
-  version: "1.0"
----
-
-# generating-visual-diagrams: Salesforce Visual AI Skill
-
-Use this skill when the user needs **rendered visuals**, not text diagrams: ERDs, UI mockups, architecture illustrations, slide-ready images, or image edits using Nano Banana Pro.
-
-## Scope
-
-**In scope:**
-- PNG / SVG-style rendered image output
-- Visual ERDs and architecture diagrams
-- LWC or Experience Cloud mockups / wireframes
-- Image edits on previously generated visuals
-
-**Out of scope — delegate instead:**
-- Mermaid or text-only diagrams → [generating-mermaid-diagrams](../generating-mermaid-diagrams/SKILL.md)
-- Object / field metadata discovery for ERDs → [generating-custom-object](../generating-custom-object/SKILL.md) or [generating-custom-field](../generating-custom-field/SKILL.md)
-- LWC implementation after the mockup is approved → [generating-lwc-components](../generating-lwc-components/SKILL.md)
-- Apex review / implementation → [generating-apex](../generating-apex/SKILL.md)
-
----
-
-## Hard Gate: Prerequisites First
-
-Run the prerequisites check before using the skill:
-
-```bash
-scripts/check-prerequisites.sh
-```
-
-If prerequisites fail, stop and route the user to setup guidance in:
-- [references/gemini-cli-setup.md](references/gemini-cli-setup.md)
-
----
-
-## Required Inputs
-
-Ask for or infer before generating:
-
-| Input | Default if not provided |
-|---|---|
-| Image type | ERD |
-| Subject scope and key entities / systems | Ask the user |
-| Target quality | Draft (1K) |
-| Preferred style | architect.salesforce.com aesthetic |
-| Aspect ratio | Default (no override) |
-| Quick mode or interview mode | Interview mode |
-
----
-
-## Interview-First Workflow
-
-Unless the user asks for **quick / simple / just generate**, ask clarifying questions first using the question bank in [references/interview-questions.md](references/interview-questions.md).
-
-| Request type | Ask about |
-|---|---|
-| ERD / schema | objects, visual style, purpose, extras |
-| UI mockup | component type, object/context, device/layout, style |
-| architecture image | systems, boundaries, protocols, emphasis |
-| image edit | what to keep, what to change, output quality |
-
-**Quick mode defaults** (triggered by "quick", "simple", "just generate", "fast"):
-- professional style, 1K draft, legend included, one image first then iterate
-
----
-
-## Recommended Workflow
-
-### 1. Run prerequisites check
-Run `scripts/check-prerequisites.sh` and confirm all required tools pass before proceeding.
-
-### 2. Gather inputs
-- object list / metadata (delegate to `generating-custom-object` / `generating-custom-field` if needed)
-- purpose: draft vs presentation vs documentation
-- desired aesthetic — read [references/architect-aesthetic-guide.md](references/architect-aesthetic-guide.md) for ERDs
-- aspect ratio / resolution
-
-### 3. Run interview or use quick-mode defaults
-Load [references/interview-questions.md](references/interview-questions.md) for the matching question set (ERD, LWC, architecture, code review).
-
-### 4. Build a concrete prompt
-Good prompts specify subject, composition, color treatment, labels/legends, and output quality goal.
-
-### 5. Generate a fast draft at 1K
-```bash
-gemini --yolo "/generate 'Your prompt here'"
-```
-Open the result and review layout before spending on higher resolution.
-
-### 6. Iterate using edits
-```bash
-gemini --yolo "/edit 'Specific change instruction'"
-```
-Use `/edit` for small adjustments — cheaper than regenerating. See [references/iteration-workflow.md](references/iteration-workflow.md).
-
-### 7. Generate final at 2K/4K using the Python script
-Run `scripts/generate_image.py` when layout is confirmed:
-```bash
-uv run scripts/generate_image.py -p "Refined prompt" -f "output.png" -r 4K
-```
-
-### 8. Error recovery
-- If `gemini --yolo` returns no image: re-run once; if it fails again, fall back to the Python script path.
-- If the Python script fails with `GEMINI_API_KEY not found`: verify the key is exported in your shell profile (`~/.zshrc` on macOS/zsh, `~/.bashrc` on Linux) and the terminal session is refreshed.
-- If the extension is missing: run `gemini extensions install nanobanana` and re-run the prerequisites check.
-
----
-
-## Default Style Guidance
-
-For ERDs, default to the **architect.salesforce.com** aesthetic unless the user asks otherwise:
-- dark border + light fill cards
-- cloud-specific accent colors
-- clean labels and relationship lines
-- presentation-ready whitespace and hierarchy
-
-Full style specification: [references/architect-aesthetic-guide.md](references/architect-aesthetic-guide.md)
-
----
-
-## Common Patterns
-
-| Pattern | Default approach |
-|---|---|
-| visual ERD | get metadata if available, then render a draft first |
-| LWC mockup | load [assets/lwc/data-table.md](assets/lwc/data-table.md), [assets/lwc/record-form.md](assets/lwc/record-form.md), or [assets/lwc/dashboard-card.md](assets/lwc/dashboard-card.md) for the matching template |
-| architecture illustration | load [assets/architecture/integration-flow.md](assets/architecture/integration-flow.md); emphasize systems and flows |
-| image refinement | use `/edit` for small changes before regenerating |
-| final production asset | switch to script-driven 2K/4K generation via `scripts/generate_image.py` |
-| Apex / LWC code review | load [assets/review/apex-review.md](assets/review/apex-review.md) or [assets/review/lwc-review.md](assets/review/lwc-review.md) for the review prompt template |
-
----
-
-## Output Expectations
-
-Deliverables produced by this skill:
-
-- **Draft image** (`<name>.png`) — 1K resolution rendered via `gemini --yolo "/generate ..."` for layout review
-- **Final image** (`<name>.png`) — 2K or 4K resolution rendered via `scripts/generate_image.py` once composition is approved
-- **Edit iteration** (`<name>.png`) — incremental refinement via `gemini --yolo "/edit ..."` without full regeneration
-
-After delivering each image:
-- Open the file in Preview or attach it in the session for multimodal review
-- Ask the user whether to iterate on layout, labeling, or color before finalizing
-- Only proceed to high-res output after draft composition is confirmed
-
----
-
-## Rules / Constraints
-
-| Rule | Rationale |
-|---|---|
-| Always run prerequisites check before any generation | Missing tools produce silent failures |
-| Always draft at 1K before generating at 4K | Cost and time savings; composition changes at high res are wasteful |
-| Use `/edit` for incremental changes, not full regeneration | Cheaper and faster for small adjustments |
-| Never commit `GEMINI_API_KEY` to version control | Key is personal and tied to billing |
-| Delegate text diagrams to `generating-mermaid-diagrams` | This skill owns rendered images only |
-
----
-
-## Gotchas
-
-| Issue | Resolution |
-|---|---|
-| Edit not applying correctly | Be specific: reference existing elements by name; one change at a time |
-| 4K output looks different from 1K draft | Use exact same prompt text; minor variations are normal model behavior |
-| `gemini --yolo` fails silently | Check that the Nano Banana extension is installed: `gemini extensions list` |
-| Image dimensions wrong | Set `--aspect-ratio` explicitly in `scripts/generate_image.py` using `-a "16:9"` |
-| RGBA image causes errors in Python script | Script auto-converts RGBA→RGB; ensure Pillow is installed via `uv` |
-
----
-
-## Cross-Skill Integration
-
-| Need | Delegate to | Reason |
-|---|---|---|
-| Mermaid first draft or text diagram | [generating-mermaid-diagrams](../generating-mermaid-diagrams/SKILL.md) | faster structural diagramming |
-| Object / field discovery for ERD | [generating-custom-object](../generating-custom-object/SKILL.md) / [generating-custom-field](../generating-custom-field/SKILL.md) | accurate schema grounding |
-| Turn mockup into real LWC component | [generating-lwc-components](../generating-lwc-components/SKILL.md) | implementation after design |
-| Apex review / implementation | [generating-apex](../generating-apex/SKILL.md) | code-quality follow-up |
-
----
-
-## Reference File Index
-
-| File | When to read |
-|---|---|
-| [references/gemini-cli-setup.md](references/gemini-cli-setup.md) | Prerequisites fail — Gemini CLI / Nano Banana setup guidance |
-| [references/interview-questions.md](references/interview-questions.md) | Step 3 — load question set matching the request type |
-| [references/iteration-workflow.md](references/iteration-workflow.md) | Step 6 — draft-to-final iteration patterns and cost tips |
-| [references/architect-aesthetic-guide.md](references/architect-aesthetic-guide.md) | Step 4 — ERD color palettes, box styles, prompt templates |
-| [references/examples-index.md](references/examples-index.md) | Step 4 — example prompts for ERD, LWC, architecture, code review |
-| [assets/erd/core-objects.md](assets/erd/core-objects.md) | Step 4 — prompt template for core CRM objects (Account, Contact, Opportunity, Case) |
-| [assets/erd/custom-objects.md](assets/erd/custom-objects.md) | Step 4 — prompt template for custom object ERDs |
-| [assets/lwc/data-table.md](assets/lwc/data-table.md) | Step 4 — prompt template for lightning-datatable mockups |
-| [assets/lwc/record-form.md](assets/lwc/record-form.md) | Step 4 — prompt template for lightning-record-form mockups |
-| [assets/lwc/dashboard-card.md](assets/lwc/dashboard-card.md) | Step 4 — prompt template for dashboard card / metric tile mockups |
-| [assets/architecture/integration-flow.md](assets/architecture/integration-flow.md) | Step 4 — prompt template for integration architecture diagrams |
-| [assets/review/apex-review.md](assets/review/apex-review.md) | Step 4 — Gemini review prompt template for Apex code |
-| [assets/review/lwc-review.md](assets/review/lwc-review.md) | Step 4 — Gemini review prompt template for LWC components |
-| [scripts/check-prerequisites.sh](scripts/check-prerequisites.sh) | Step 1 — run to verify all required tools are installed |
-| [scripts/generate_image.py](scripts/generate_image.py) | Step 7 — run for 2K/4K resolution output and image editing with resolution control |