Sf Diagram Nanobananapro
Generate professional Salesforce integration-flow and architect-style ERD diagrams via structured prompts (e.g., Gemini image generation) for proposals and solution design.
Overview
sf-diagram-nanobananapro is an agent skill most often used in Build (also Validate, Launch) that produces Salesforce integration and ERD diagrams from reusable nanobananapro-style prompt templates.
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-diagram-nanobananaproWhat is this skill?
- Integration-flow prompt template: systems, patterns, API gateway, auth, middleware, error/retry
- Example hub-spoke flow: Salesforce REST to MuleSoft BAPI to SAP with bidirectional sync labels
- ERD template aligned to architect.salesforce.com style: legend, labeled relationships, footer
- Default styling: dark border, translucent fill, Salesforce header banner, ENTITIES/RELATIONSHIPS legend
- Gemini /generate command examples with OAuth 2.0 badges and error-queue callouts
- Two template families: Integration Flow and Core Salesforce Objects ERD
- Default ERD style: legend bar with ENTITIES and RELATIONSHIPS
Adoption & trust: 1.2k installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a credible Salesforce integration or ERD diagram for a deck or SOW but lack time to hand-draw architect.salesforce.com-quality figures.
Who is it for?
Indie Salesforce consultants, solution designers, and builders documenting MuleSoft, SAP, or multi-system flows before build-out.
Skip if: Teams needing automated metadata ERD extraction from an org, performance testing, or security architecture reviews without human fact-checking.
When should I use this skill?
User needs Salesforce integration architecture or architect-style ERD diagrams from structured image-generation prompts.
What do I get? / Deliverables
You get copy-paste prompt blocks and Gemini-ready examples that yield labeled integration flows and styled ERDs for reviews and proposals.
- Integration-flow prompt block
- Architect-style ERD prompt block
- Example gemini /generate command strings
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Architecture diagrams are produced while designing and documenting integrations—canonical first shelf is Build when the system picture is being defined. docs fits because outputs are visual architecture artifacts for stakeholders, not runtime Salesforce metadata deployment.
Where it fits
Show a prospect how Salesforce, middleware, and ERP connect before you quote build hours.
Drop a legend-backed ERD into your internal build spec for Account–Contact–Opportunity models.
Align engineers on REST vs event-driven legs before writing MuleSoft flows.
Publish a sanitized architecture figure in a portfolio post about enterprise integrations.
How it compares
Prompt-template generator for visuals—not Salesforce CLI, not Lucidchart MCP, not live org schema sync.
Common Questions / FAQ
Who is sf-diagram-nanobananapro for?
Solo consultants and builders who sell or implement Salesforce integrations and need fast, on-brand architecture diagrams.
When should I use sf-diagram-nanobananapro?
During Build/docs while drafting solution design; during Validate/scope when visualizing proposed integrations; during Launch/distribution when attaching architecture figures to case studies or RFPs.
Is sf-diagram-nanobananapro safe to install?
It mainly supplies text prompts; review the Security Audits panel on this page and avoid embedding customer secrets or live credentials inside generation prompts.
SKILL.md
READMESKILL.md - Sf Diagram Nanobananapro
# Architecture Template: Integration Flow ## Prompt Template ``` Professional Salesforce integration architecture diagram: SYSTEMS: [List systems with types and icons] INTEGRATION PATTERNS: [List integrations with protocols and directions] COMPONENTS: - API Gateway (if applicable) - Authentication layer - Middleware/ESB (if applicable) - Error handling/retry logic STYLING: - Cloud icon for Salesforce - Server icons for external systems - Arrows with protocol labels - Color coding by system type - Professional diagram style FORMAT: - Landscape orientation - Left-to-right or hub-spoke layout - Include legend ``` ## Example ```bash gemini "/generate 'Salesforce integration architecture diagram: Systems: 1. Salesforce (cloud icon, blue) 2. MuleSoft (middleware icon, purple) 3. SAP ERP (server icon, orange) Flows: 1. Salesforce --REST--> MuleSoft --BAPI--> SAP - Account/Contact sync (bidirectional) 2. SAP --Events--> MuleSoft --Platform Events--> Salesforce - Invoice updates Include: - OAuth 2.0 authentication badges - Error queue for failed messages Style: Professional, clean lines, pastel colors'" ``` # ERD Template: Core Salesforce Objects (Architect.salesforce.com Style) ## Default Style All ERDs now use the **official architect.salesforce.com aesthetic** by default: - Dark border + light translucent fill boxes - Header banner with Salesforce logo - LEGEND bar with ENTITIES and RELATIONSHIPS - Labeled relationship lines - Footer with copyright See `references/architect-aesthetic-guide.md` for full specification. --- ## Prompt Template (Architect.salesforce.com Style) ``` Create a Salesforce Core CRM ERD in the EXACT architect.salesforce.com style: PAGE TITLE (very top, large bold text): 'Core CRM Overview Data Model' HEADER SECTION (below title): - Left: Salesforce cloud logo + 'SALESFORCE PLATFORM Overview' in dark teal (#0B827C) banner box - Center: LEGEND with 'ENTITIES' section showing: * Cloud Entity box (dark teal #0B827C border, light teal ~25% opacity fill) * Related Entity box (dark teal border, lighter fill) * External Entity box (black border, white fill) - Right: 'RELATIONSHIPS' section showing notation symbols for Parent/Child, Required, Optional, Many-to-Many BOX STYLING - CRITICAL: - DARK BORDER: Solid 2px border in dark teal (#0B827C) - LIGHT TRANSLUCENT FILL: Same teal hue at ~25% opacity - Rounded corners (8-12px radius) - Text in dark gray/black on the light fill ENTITY BOX FORMAT: ┌─────────────────────────┐ │ Logical Name │ (Bold, larger) │ APIName │ (Smaller, italic, gray) │ • Field1 │ (Bullet points) │ • Field2 │ └─────────────────────────┘ OBJECTS TO INCLUDE (all with dark teal border + light teal fill): - Account (center position): Account Account • Account Number • Name • Industry • Type - Contact (linked to Account): Contact Contact • Name • Email • Title • Phone - Opportunity (linked to Account): Opportunity Opportunity • Name • Amount • Close Date • StageName - Case (linked to Account and Contact): Case Case • CaseNumber • Type • Priority • Status RELATIONSHIP LINES: - Thin black lines with text labels ON the lines - Contact → Account: "child of" (crow's foot on Contact side) - Opportunity → Account: "child of" (crow's foot on Opportunity side) - Case → Account: "related to" (crow's foot on Case side) - Case → Contact: "related to" (optional) - STRAIGHT LINES ONLY (horizontal and vertical, no diagonals) FOOTER: Left: '©2024 Salesforce - Subject to change without notice' Right: 'Last modified: [current date]' CRITICAL: Dark teal borders with LIGHT translucent teal fill - NOT solid filled boxes. ``` --- ## Usage ```bash # Quick draft at 1K (iterate here) gemini --yolo "/generate '[paste prompt above]'" open ~/nanobanana-output/*.png # Review and refine # Final at 4K (when satisfied) uv run scripts/generate_image.py \ -p "[your refined prompt]"