@salesforce/afv-skills 1.29.0 → 1.30.0

package/skills/platform-policy-rule-generate/references/ui-compatibility.md

@@ -0,0 +1,142 @@
+# UI Compatibility — Data Governance Policy Builder
+
+The Data Governance Policy Builder edits a **strict subset** of the MDAPI. Anything outside that subset must be maintained via MDAPI/Tooling for the policy's lifetime — admins cannot open it in the builder without silent data loss or a hard crash.
+
+> **Default goal**: produce UI-compatible policies. Only fall back to API-only after asking the operator and getting explicit confirmation.
+
+---
+
+## What the UI Can Render
+
+**Categories** : `GOVERNANCE_POLICY_RULE_DEFINITION`, `RECORD_POLICY_RULE_DEFINITION`, `TRANSFORM_POLICY_RULE_DEFINITION` 
+**Categories NOT handled** : `ACCESS_POLICY_RULE_DEFINITION` (UI forces to GOVERNANCE on save), `IDENTIFIED_RECORD_POLICY_RULE_DEFINITION`
+
+**Effects** : `Permit`, `Forbid` (UI label "Deny"), `Transform`
+
+**Actions** : `Read`, `TupleRead` — two real choices for OLS/FLS rules.
+- `Read`: evaluates conditions against the resource itself
+- `TupleRead`: cascade rewriter — expands object-level condition to also cover `resource.object.*` for fields. Use when the intent is "objects matching X AND all their fields"
+- Multiple `<action>` entries: only the first is kept on save
+
+**`<ruleConsumer>`** : only `DATACLOUD` (hardcoded on save) 
+**`<principalScopeType>`** : only `ANY` (hardcoded on save) 
+**`<resourceScopeType>`** : `ANY`, `RECORD`, `FIELD`, `DATASPACE`, `SPAN` 
+**`<principalAuthenticationLevel>`** : `INTERNAL`, `AUTHENTICATED`, `UNIDENTIFIED`. `IDENTIFIED` not exposed. 
+**`<replicated>`** : read but NOT editable. Once `true`, UI forces read-only mode. 
+**`<transformPrecedence>`** : not exposed; non-zero values dropped.
+
+---
+
+## Conditions — Supported Shapes
+
+**Top-level conjunction**: only `<whenPolicyRuleDefinitionClauseConjunction>`. The UI forces `<unlessPolicyRuleDefinitionClauseConjunction>` to `null` on save.
+
+**Conjunction expression**: the UI builds `(AND …)` of up to four sections dispatched by path type. A pure flat `(OR 1 2)` at the top level triggers `// ERROR: Unsupported rule!` — rule silently dropped. `OR` only round-trips inside a single section's group.
+
+**Path types per UI section:**
+
+| UI Section | Recognized path |
+|------------|-----------------|
+| Users (Permission) | `principalPath = ASSIGNED_PERMISSIONS_PATH` |
+| Resource entity-type | `resourcePath = ENTITYTYPE` with `IS` operator |
+| Data space | `resourcePath = DATASPACE` or `contextPath = SESSION_DATASPACE` |
+| Tag / Classification | `resourcePath = TAG` or `CLASSIFICATION` |
+| RLS rule criteria | `resourcePath = RECORDFIELD` or `EXPRESSION` |
+
+Any other path type → condition silently ignored when UI rebuilds the rule.
+
+**Operators per path**:
+- Tag/Classification: `CONTAINS_ANY`, `CONTAINS_NONE`. (`CONTAINS_ALL` exists in schema but not offered in dropdowns)
+- Permission: `CONTAINS_ANY` (Permit) / `CONTAINS_NONE` (Forbid/Transform)
+- RLS `RECORDFIELD`: `EQUALS`, `NOT_EQUALS`, `LIKE`, `LESS_THAN(_OR_EQUALS)`, `GREATER_THAN(_OR_EQUAL)`, `HIERARCHICALLY_ABOVE` (DLO/DMO only). **Not editable**: `HIERARCHICALLY_BELOW`, `IN`, `CONTAINS_ALL`
+- RLS join (`EXPRESSION`): `EXISTS` only
+
+**`<policyRuleValueSet>` reference types** : `CUSTOM_TAG`, `STANDARD_TAG`, `CUSTOM_CLASSIFICATION`, `STANDARD_CLASSIFICATION`, `CUSTOM_PERMISSION`. **Not editable**: `HIERARCHY`, `DATASPACE`.
+
+---
+
+## Implicit Defaults Injected by the UI on Save
+
+When the UI saves, it auto-injects these — if your hand-authored XML omits them or uses different values, the first UI save rewrites them:
+
+| Field | UI default |
+|-------|-----------|
+| `principalAuthenticationLevel` | `INTERNAL` |
+| `principalScopeType` | `ANY` |
+| `ruleConsumer` | `DATACLOUD` |
+| `unlessPolicyRuleDefinitionClauseConjunction` | `null` (always) |
+| `actions` | only first action kept |
+| `policyRuleResourceDomains` | only first `<resourceDomain>` kept |
+
+---
+
+## The Non-Round-Trip Checklist
+
+The policy will **not** round-trip through the UI without data loss or silent failure if **any** of the following is true:
+
+- [ ] `category` is `ACCESS_POLICY_RULE_DEFINITION` or `IDENTIFIED_RECORD_POLICY_RULE_DEFINITION`
+- [ ] `ruleConsumer` ≠ `DATACLOUD`
+- [ ] More than one `<action>`, or action is not `Read` / `TupleRead`
+- [ ] **No top-level `resourcePath=ENTITYTYPE` discriminator group** for ACCESS/GOVERNANCE rules — this causes a **hard crash** (`Cannot use 'in' operator to search for 'Permit' in undefined`), not a graceful degradation. A `TupleRead` rule without the OR-of-ENTITYTYPE clause still deploys and works at runtime — the crash is UI-only.
+- [ ] **Bare top-level condition index** in `<conjunctionExpression>` (e.g. `3` instead of `(AND 3)`) — causes crash in `buildCriteria` (`param.params.map(...)` = `undefined.map()`)
+- [ ] More than one `<resourceDomain>`
+- [ ] An `<unlessPolicyRuleDefinitionClauseConjunction>` block present
+- [ ] Any `<conditions>` uses `<clause>UNLESS</clause>`
+- [ ] `<conjunctionExpression>` uses top-level `OR` (e.g. `(OR 1 2)`)
+- [ ] `<principalPath>` other than `ASSIGNED_PERMISSIONS_PATH` (user ID etc. may appear only inside SOQL `${User.X}` substitutions)
+- [ ] `<resourcePath>` other than `TAG`, `CLASSIFICATION`, `DATASPACE`, `RECORDFIELD`, `EXPRESSION`, `ENTITYTYPE`
+- [ ] `<valuePrincipalPath>` is not one of `USER_ID`, `USER_ROLE_ID`, `ORGANIZATION_ID`, `SCALAR_ATTRIBUTE`, `PLURAL_ATTRIBUTE` (with `${User.X}` expression)
+- [ ] `<contextPath>` other than `SESSION_DATASPACE`
+- [ ] Operator is `HIERARCHICALLY_BELOW`, `IN`, or `CONTAINS_ALL`
+- [ ] `<valueReferenceType>` is `HIERARCHY` or `DATASPACE`
+- [ ] `<valueString>` is typed JSON other than `{"t":"Text","v":"FIELD"|"RECORD"|"OBJECT"}` or `{"t":"Boolean","v":…}` with a UI-recognized boolean field
+- [ ] `<resourceTransform>` not in the masking-category mapped set
+- [ ] `<resourceExpression>` ARGLIST has multiple arguments
+- [ ] `<replicated>true</replicated>` in an org with replication frozen
+
+If **none** of the above is true, the policy is **UI-compatible**.
+
+> **Important**: The UI shows NO banner when it drops unsupported pieces on save (`// ERROR: Unsupported rule!` comment, no surfaced message). Operator-confirmation is the only line of defense.
+
+---
+
+## Operator-Confirmation Protocol
+
+Whenever a request would produce a UI-incompatible policy:
+
+1. **Try to make it UI-compatible first.** Mechanical rewrites:
+ - `unless` → `when` with negated operator:
+ | Intent | UI-compatible rewrite |
+ |--------|----------------------|
+ | `unless principal has permission X` | `WHEN ASSIGNED_PERMISSIONS_PATH CONTAINS_NONE X` |
+ | `unless resource has tag X` | `WHEN TAG CONTAINS_NONE X` |
+ | `unless record field = value` | `WHEN RECORDFIELD NOT_EQUALS value` |
+ - Top-level `OR` between two tags → nest inside a tag/classification section group
+ - Multiple `<action>` → split into multiple rules
+
+2. **If a UI-compatible rewrite is not possible**, tell the operator:
+ - Which traits make it incompatible (cite items from the checklist above)
+ - That the Data Governance Policy Builder will silently drop unsupported pieces on save with no warning
+ - That maintenance must happen through MDAPI/Tooling for the policy's lifetime
+
+3. **Wait for explicit confirmation.** Do not write the file until confirmed.
+
+4. **On confirmation**, add an in-source marker to `<description>` (or a comment above the rule): `# API-only: not editable in Data Governance Policy Builder. Reasons: <bullets>`. Also set `<builderCompatible>false</builderCompatible>` on the parent set.
+
+---
+
+## UI-Compatibility Matrix for Templates
+
+| Template | UI-compatible? | Notes |
+|----------|----------------|-------|
+| Bare permit, no conditions | Partial | Single `<action>Read</action>` only; `ruleConsumer=DATACLOUD`. UI maps ACCESS → Governance on load. |
+| Tag / Classification / Permission gate | Yes | `CONTAINS_ANY` / `CONTAINS_NONE` only. Tag refs must resolve in org. |
+| Basic RLS (RECORDFIELD = user attribute) | Yes | `USER_ID` / `ORGANIZATION_ID` / `USER_ROLE_ID` round-trips. |
+| TupleRead with OR-of-ENTITYTYPE | Yes | The canonical UI-compatible OLS/FLS shape. |
+| IDENTIFIED_RECORD | Not MDAPI-authorable | Must be a runtime RuleProvider. |
+| RLS via PROJECTION join | Yes | Single PROJECTION editable. |
+| Scalar/plural SOQL principal | Out of MDAPI contract | `SCALAR_ATTRIBUTE`/`PLURAL_ATTRIBUTE` not in `RulePrincipalPathType`. Fixture-only. |
+| TRANSFORM with permission + classification | Yes | Use masking-category-mapped transforms only. |
+| `(AND 1 2)` multi-condition | Yes (if each section is one of the four UI buckets) | |
+| Top-level `(OR 1 2)` | No | Triggers unsupported-rule path; silently dropped. |
+| Hierarchy traversal | No | `HIERARCHICALLY_BELOW` and `HIERARCHY` not in UI dropdowns. Always API-only. |

package/skills/platform-soql-query/README.md

@@ -14,7 +14,7 @@ Salesforce SOQL query generation, optimization, and analysis skill with 100-poin
 
 ### 1. Invoke the skill
 
-```
+```yaml
 Skill: platform-soql-query
 Request: "Find Accounts with open Opportunities created this quarter"
 ```

package/skills/platform-soql-query/SKILL.md

@@ -90,7 +90,7 @@ When finishing, report in this order:
 
 Suggested shape — use `references/soql-syntax-reference.md` for exact syntax:
 
-```
+```text
 Query goal: <summary>
 Query: <soql or sosl>
 Design: <relationship / aggregate / filter choices>

package/skills/platform-soql-query/references/anti-patterns.md

@@ -308,7 +308,7 @@ WHERE Days_Open__c > 30
 
 ## Quick Reference: Selectivity Rules
 
-```
+```text
 A filter is SELECTIVE when:
 ├── Uses an indexed field, AND
 ├── Returns < 10% of first million records, OR

package/skills/platform-soql-query/references/field-coverage-rules.md

@@ -21,7 +21,7 @@ This guide documents field coverage validation rules for SOQL queries — ensuri
 
 When you query an sObject, only the fields in the SELECT clause are populated. Accessing any other field results in a runtime error:
 
-```
+```text
 System.SObjectException: SObject row was retrieved via SOQL without querying the requested field: Account.Industry
 ```
 

package/skills/platform-soql-query/references/query-optimization.md

@@ -17,7 +17,7 @@
 
 ## Selectivity Rules
 
-```
+```text
 A filter is selective when it returns:
 - < 10% of total records for first 1 million
 - < 5% of total records for additional records

package/skills/platform-soql-query/scripts/post-tool-validate.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Post-Tool Validation Hook for querying-soql skill.
+Post-Tool Validation Hook for platform-soql-query skill.
 
 This hook runs AFTER Write or Edit tool completes and provides validation
 feedback for SOQL files (*.soql).
@@ -23,8 +23,8 @@ import json
 SCRIPT_DIR = os.path.dirname(os.path.abspath(__file__))
 sys.path.insert(0, SCRIPT_DIR)
 
-# Find shared modules (../../shared relative to querying-soql)
-PLUGIN_ROOT = os.path.dirname(os.path.dirname(SCRIPT_DIR))  # querying-soql/
+# Find shared modules (../../shared relative to platform-soql-query)
+PLUGIN_ROOT = os.path.dirname(os.path.dirname(SCRIPT_DIR))  # platform-soql-query/
 SKILLS_ROOT = os.path.dirname(PLUGIN_ROOT)  # sf-skills/
 SHARED_DIR = os.path.join(SKILLS_ROOT, "shared")
 sys.path.insert(0, SHARED_DIR)

package/skills/data360-activate/CREDITS.md

@@ -1,5 +0,0 @@
-# Credits & Acknowledgments
-
-This skill is part of the `*-datacloud` family. Shared attribution, upstream source mapping, and maintenance notes live in:
-- [../data360-orchestrate/CREDITS.md](../data360-orchestrate/CREDITS.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

package/skills/data360-connect/CREDITS.md

@@ -1,5 +0,0 @@
-# Credits & Acknowledgments
-
-This skill is part of the `*-datacloud` family of skills covering the full Data Cloud workflow lifecycle. Shared upstream source mapping and maintenance notes live in:
-- [../data360-orchestrate/CREDITS.md](../data360-orchestrate/CREDITS.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

package/skills/data360-harmonize/CREDITS.md

@@ -1,3 +0,0 @@
-# Credits & Acknowledgments
-
-This skill is part of the `*-datacloud` family of skills covering the Data Cloud lifecycle: ingestion, harmonization, segmentation, and retrieval.

package/skills/data360-orchestrate/CREDITS.md

@@ -1,15 +0,0 @@
-# Credits & Acknowledgments
-
-This skill family distills publicly shared Data Cloud implementation knowledge into sf-skills house style. Attribution is intentionally explicit because contributor credit is a core sf-skills principle.
-
----
-
-This family intentionally:
-- keeps sf-skills naming consistency (`*-datacloud`)
-- keeps the external CLI plugin outside this repo
-- favors deterministic helper scripts and reusable JSON templates
-- rewrites examples into generic sf-skills-style guidance rather than copying workshop-specific payloads
-
-See [UPSTREAM.md](UPSTREAM.md) for the maintenance contract.
-
----

package/skills/data360-orchestrate/UPSTREAM.md

@@ -1,45 +0,0 @@
-# Upstream Distillation Map for data360-orchestrate
-
-This file exists to make downstream maintenance easy without sacrificing sf-skills consistency.
-
-## Maintenance contract
-
-When upstream changes, do **not** copy blindly.
-
-Instead:
-1. review new upstream commits
-2. identify changed command behaviors, install patterns, or gotchas
-3. update sf-skills prompts and templates in a distilled form
-4. keep naming, attribution, and cross-skill boundaries consistent with sf-skills
-5. update this file with the new reviewed commit SHAs
-
-## High-priority upstream areas to re-check
-
-- installation / linking workflow for the community plugin
-- command counts and topic coverage
-- API-version guidance
-- known issues and bug-fix notes
-- live-tested command set
-- any new commands affecting Connect / Prepare / Harmonize / Segment / Act / Retrieve boundaries
-- connector-specific payload examples worth distilling into generic repo-safe examples
-- search-index / hybrid-search guidance and any command-surface changes around hybrid scoring or prefilter behavior
-- Ingestion API schema-upload flow, send-data examples, and problem-record guidance
-- unstructured-source setup differences between connection-level reruns, stream refreshes, and initial UI seeding
-- UI-only gaps where upstream introduces browser automation; validate before importing
-
-## Cross-skill boundary reminders
-
-Keep Data Cloud product work in `*-datacloud`, but do not blur into:
-- `agentforce-observe` for STDM/session tracing/parquet workflows
-- `platform-soql-query` for CRM SOQL-only tasks
-- `platform-data-manage` for CRM record seeding/cleanup
-- `platform-*-generate` skills for CRM schema creation (custom objects, fields, validation rules, etc.)
-
-## Local helper files in this family
-
-- `references/plugin-setup.md`
-- `scripts/bootstrap-plugin.sh`
-- `scripts/verify-plugin.sh`
-- `assets/definitions/`
-
-These are sf-skills-owned conveniences and should evolve independently from upstream when that improves user experience.

package/skills/data360-prepare/CREDITS.md

@@ -1,7 +0,0 @@
-# Credits & Acknowledgments
-
-Primary contributor: **Gnanasekaran Thoppae**
-
-This skill is part of the `*-datacloud` family. Shared attribution, upstream source mapping, and maintenance notes live in:
-- [../data360-orchestrate/CREDITS.md](../data360-orchestrate/CREDITS.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

package/skills/data360-query/CREDITS.md

@@ -1,7 +0,0 @@
-# Credits & Acknowledgments
-
-Primary contributor: **Gnanasekaran Thoppae**
-
-This skill is part of the `*-datacloud` family. Shared attribution, upstream source mapping, and maintenance notes live in:
-- [../data360-orchestrate/CREDITS.md](../data360-orchestrate/CREDITS.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

package/skills/data360-segment/CREDITS.md

@@ -1,3 +0,0 @@
-# Credits & Acknowledgments
-
-This skill is part of the `*-datacloud` family of skills covering the Salesforce Data Cloud workflow phases. Shared definitions, templates, and readiness scripts for this family live in the `data360-orchestrate` skill directory.

package/skills/experience-lwc-generate/CREDITS.md

@@ -1,5 +0,0 @@
-# Credits & Acknowledgments
-
-This skill is built on official Salesforce LWC platform patterns and established component development practices.
-
----

package/skills/external-diagram-mermaid-generate/CREDITS.md

@@ -1,46 +0,0 @@
-# Credits & Acknowledgments
-
-This skill was built upon established patterns in technical diagramming and Salesforce data modeling. The following concepts and conventions shaped its design.
-
----
-
-## Diagramming Concepts
-
-### Text-Based Diagramming
-The skill uses Mermaid as its primary diagramming syntax, covering Entity Relationship Diagrams, sequence diagrams, and flowcharts. Key capabilities include:
-
-- Entity Relationship Diagram syntax
-- Sequence diagram patterns
-- Flowchart and state diagram support
-- Live rendering through Mermaid-capable renderers
-
-An alternative syntax, PlantUML, informed the UML diagram patterns used in sequence and class diagrams.
-
----
-
-## Salesforce Domain Patterns
-
-### Data Modeling Conventions
-The ERD conventions follow standard Salesforce object relationship patterns, including Master-Detail, Lookup, and External relationships as documented in the Salesforce platform's object model.
-
-### Integration Architecture
-Integration sequence diagrams draw on widely-adopted API documentation patterns adapted for Salesforce's authentication and integration architecture.
-
-### Schema Reference
-Object and field relationship information reflects standard Salesforce object reference conventions and relationship type definitions.
-
----
-
-## Key Concepts
-
-### ERD Notation
-The Entity Relationship Diagram conventions follow standard database modeling patterns adapted for Salesforce relationships (Master-Detail, Lookup, External).
-
-### Sequence Diagram Patterns
-OAuth flow and integration sequence diagrams follow UML 2.0 standards with Salesforce-specific adaptations.
-
-### Mermaid in Documentation
-The approach of using Mermaid for inline diagrams in Markdown documentation is a widely-adopted pattern in technical documentation that enables version-controlled diagrams alongside code.
-
-### Color Accessibility
-The color palette follows accessibility guidelines for color-blind-friendly design, using a pastel fill with high-contrast stroke approach.

package/skills/external-diagram-visual-generate/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/external-diagram-visual-generate/README.md

@@ -1,83 +0,0 @@
-# external-diagram-visual-generate
-
-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: external-diagram-visual-generate
-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 |
-|---------------|-------------|
-| external-diagram-mermaid-generate | Convert Mermaid to visual rendering |
-| platform-custom-object-generate | Query object/field data before generating ERDs |
-| experience-lwc-generate | Generate mockups for LWC components |
-| platform-apex-generate | 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)