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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsf-diagram-nanobananaproExecute the skills CLI command in your project's root directory to begin installation:
Fetches sf-diagram-nanobananapro from jaganpro/sf-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sf-diagram-nanobananapro. Access via /sf-diagram-nanobananapro in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
292
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
292
stars
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.
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:
Use sf-diagram-nanobananapro when the user wants:
Delegate elsewhere when the user wants:
Ask for or infer:
Unless the user explicitly asks for quick/simple/just generate, ask clarifying questions first.
| 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
If the user says “quick”, “simple”, or “just generate”, default to:
Decide which of these are needed:
Good prompts specify:
gemini --yolo "/generate 'Professional Salesforce ERD with Account, Contact, Opportunity; clean legend; white background; Salesforce-style colors'"
Use natural-language edits:
gemini --yolo "/edit 'Move Account to center, thicken relationship lines, add legend in bottom right'"
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
For ERDs, default to the architect.salesforce.com aesthetic unless the user asks otherwise:
Style guide: references/architect-aesthetic-guide.md
| 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
After generating, do one of these:
Keep the first pass cheap; only spend on high-res output after the composition is right.
| 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 |
| 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 |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for sf-diagram-nanobananapro matched our evaluation — installs cleanly and behaves as described in the markdown.
sf-diagram-nanobananapro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in sf-diagram-nanobananapro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
sf-diagram-nanobananapro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
sf-diagram-nanobananapro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
sf-diagram-nanobananapro has been reliable in day-to-day use. Documentation quality is above average for community skills.
sf-diagram-nanobananapro reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for sf-diagram-nanobananapro matched our evaluation — installs cleanly and behaves as described in the markdown.
We added sf-diagram-nanobananapro from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: sf-diagram-nanobananapro is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 45