AGENT SKILL

sf-diagram-nanobananapro

AI-powered image generation for Salesforce visuals via Nano Banana Pro. 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 sf-diagram-mermaid), or non-visual documentation tasks.

License 许可
MIT
最近更新
2026-07-18
Stars
★ 0
Forks
1

01 前言 Front Matter

name
sf-diagram-nanobananapro
license
MIT
metadata
{ "author": "Jag Valaiyapathy", "scoring": "80 points across 5 categories", "version": "1.5.0" }
description
AI-powered image generation for Salesforce visuals via Nano Banana Pro. 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 sf-diagram-mermaid), or non-visual documentation tasks.

03 SKILL.md 正文

sf-diagram-nanobananapro: 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.

Hard Gate: Prerequisites First

Always run the prerequisites check before using the skill:

~/.claude/skills/sf-diagram-nanobananapro/scripts/check-prerequisites.sh

If prerequisites fail, stop and route the user to setup guidance in:


When This Skill Owns the Task

Use sf-diagram-nanobananapro when the user wants:

  • PNG / SVG-style image output
  • rendered ERDs or architecture diagrams
  • LWC or Experience Cloud mockups / wireframes
  • visual polish beyond Mermaid
  • edits to a previously generated image

Delegate elsewhere when the user wants:


Required Context to Gather First

Ask for or infer:

  • image type: ERD, UI mockup, architecture illustration, or image edit
  • subject scope and key entities / systems
  • target quality: draft vs presentation vs production asset
  • preferred style and aspect ratio
  • whether the user wants quick mode or an interview-driven prompt build

Interview-First Workflow

Unless the user explicitly asks for quick/simple/just generate, ask clarifying questions first.

Minimum question set

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

Question bank: references/interview-questions.md

Quick mode defaults

If the user says “quick”, “simple”, or “just generate”, default to:

  • professional style
  • 1K draft output
  • legend included when helpful
  • one image first, then iterate

Recommended Workflow

1. Gather inputs

Decide which of these are needed:

  • object list / metadata
  • purpose: draft vs presentation vs documentation
  • desired aesthetic
  • aspect ratio / resolution
  • whether this is a fresh render or edit of an existing image

2. Build a concrete prompt

Good prompts specify:

  • subject and scope
  • composition / layout
  • color treatment
  • labels / legends / relationship lines
  • output quality goal

3. Generate a fast draft first

gemini --yolo "/generate 'Professional Salesforce ERD with Account, Contact, Opportunity; clean legend; white background; Salesforce-style colors'"

4. Iterate before final

Use natural-language edits:

gemini --yolo "/edit 'Move Account to center, thicken relationship lines, add legend in bottom right'"

5. Use the Python script for controlled final output

Use the script when you need higher resolution or explicit edit inputs:

uv run scripts/generate_image.py \
  -p "Final production-quality Salesforce ERD with legend and field highlights" \
  -f "crm-erd-final.png" \
  -r 4K

Full iteration guide: references/iteration-workflow.md


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

Style guide: references/architect-aesthetic-guide.md


Common Patterns

Pattern Default approach
visual ERD get metadata if available, then render a draft first
LWC mockup use component template + user context + one draft iteration
architecture illustration emphasize systems and flows, reduce field-level detail
image refinement use /edit for small changes before regenerating
final production asset switch to script-driven 2K/4K generation

Examples: references/examples-index.md


Output / Review Guidance

After generating, do one of these:

  • open the file in Preview for visual inspection
  • attach/read the image in the coding session for multimodal review
  • ask the user whether to iterate on layout, labeling, or color before finalizing

Keep the first pass cheap; only spend on high-res output after the composition is right.


Cross-Skill Integration

Need Delegate to Reason
Mermaid first draft or text diagram sf-diagram-mermaid faster structural diagramming
object / field discovery for ERD sf-metadata accurate schema grounding
turn mockup into real component sf-lwc implementation after design
review Apex / trigger code in parallel sf-apex code-quality follow-up

Reference Map

Start here

Visual style / examples


Score Guide

Score Meaning
70+ strong image prompt / workflow choice
55–69 usable draft with iteration needed
40–54 partial alignment to request
< 40 poor fit; re-interview and rebuild prompt

04 同仓库更多 Skills

om-scogo
om-scogo/skillsh-scraper

arxiv-search

Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.

★ 0
om-scogo
om-scogo/skillsh-scraper

arxiv-search

Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.

★ 0
om-scogo
om-scogo/skillsh-scraper

working-with-legacy-code

Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

★ 0
om-scogo
om-scogo/skillsh-scraper

working-with-legacy-code

Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

★ 0
om-scogo
om-scogo/skillsh-scraper

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0
om-scogo
om-scogo/skillsh-scraper

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0