visual-design
Use this skill any time the user needs a visual output as an image or PDF — charts, diagrams, posters, infographics, abstract artwork, or any visual design. Trigger for: data visualization requests, poster/flyer creation, infographic design, abstract or artistic visuals, architecture/flow diagrams, or any request mentioning 'chart', 'graph', 'poster', 'infographic', 'design', 'visual', or referencing .png/.pdf image output.
What this skill does
# Visual Design ## Quick Reference | Task | Tool | Guide | |-----------------------------|------------------------|--------------------------------------------| | Data chart or graph | `generate_chart` | Read SKILL.md Design Ideas | | Poster / infographic / art | `create_visual_design` | Read [canvas-design.md](canvas-design.md) | | Architecture / flow diagram | `create_visual_design` | Read [diagram-design.md](diagram-design.md)| ## Available Tools ### generate_chart Data visualization. Executes matplotlib/plotly code to produce chart PNGs. - `python_code` (str, required): Chart generation Python code - `output_filename` (str, required): `.png` filename ### create_visual_design Visual design creation: posters, infographics, artwork, diagrams. Uses reportlab, Pillow, svgwrite, or any available library. - `python_code` (str, required): Design generation Python code - `output_filename` (str, required): `.png` or `.pdf` filename ## Available Libraries | Purpose | Libraries | Output | Notes | |---------|-----------|--------|-------| | Data charts | matplotlib, plotly, bokeh | PNG | Best for charts | | PDF design | reportlab, fpdf | PDF | Full control | | Image design | Pillow + fonttools | PNG | Best for PNG designs | | Vector graphics | svgwrite → svglib + renderPDF | SVG → PDF | SVG→PNG NOT supported (no renderPM) | | Image processing | Wand (ImageMagick), opencv-python | PNG | Check availability first | **IMPORTANT**: For PNG output, use Pillow or matplotlib. Do NOT use svgwrite→renderPM (rlPyCairo is unavailable). ## Design Workflow ### Data Charts (`generate_chart`) 1. Identify data structure and choose appropriate chart type 2. Select color palette (see Design Ideas below) 3. Write code with `plt.savefig(filename, dpi=300, bbox_inches='tight')` 4. Review the generated chart ### Visual Design (`create_visual_design`) 1. Establish design concept/philosophy (internally) 2. Follow the process in [canvas-design.md](canvas-design.md) 3. Select appropriate library and write code 4. Save: reportlab `canvas.save()`, Pillow `image.save()`, matplotlib `plt.savefig()` 5. Review output and refine ## Design Ideas ### Color Palettes | Theme | Primary | Accent | Background | |-------|---------|--------|------------| | Midnight Executive | `1E2761` | `408EC6` | `0D1B2A` | | Forest & Moss | `2C5F2D` | `97BC62` | `1A1A1A` | | Coral Energy | `F96167` | `F9E795` | `2F3C7E` | | Ocean Gradient | `065A82` | `1B9AAA` | `021B29` | | Charcoal Minimal | `36454F` | `E8E8E8` | `1C1C1E` | | Cherry Bold | `990011` | `FCF6F5` | `150E11` | | Sage Calm | `84B59F` | `69A297` | `2D3A2D` | | Warm Terracotta | `B85042` | `E7E8D1` | `2A1F1C` | ### Typography Prefer thin/light fonts. Minimize text in designs. | Element | Size | Style | |---------|------|-------| | Main title | 48-72pt | Bold or Thin | | Subtext | 14-18pt | Light | | Labels/captions | 8-12pt | Regular, muted | **Text-to-Canvas Balance (IMPORTANT):** - Text size must be proportional to the overall canvas and surrounding design elements - Common mistake: text that is too small relative to the canvas, making it unreadable at normal viewing distance - Rule of thumb: if you need to zoom in to read it, it's too small - Titles should command attention — when in doubt, go larger - Labels/captions should be clearly legible, not decorative afterthoughts - Test: mentally shrink the output to 50% — all text should still be readable ### Spacing & Composition - Generous margins (minimum 10% of canvas) - Consistent spacing between elements - No overlapping; all elements within canvas bounds - Visual hierarchy: convey importance via size, color, position ### Avoid - Elements flush to canvas edges (insufficient margins) - Overlapping elements - Too many colors (stick to 3-4) - Excessive text — visual elements are the focus - Default matplotlib styles without customization ## Code Requirements - Code must save a file to disk - Use the exact `output_filename` provided - PNG: `dpi=300` or higher recommended - PDF: A4 or Letter size recommended - For Korean text: configure appropriate fonts ## QA **Assume there are problems and look for them.** 1. Review the generated image/PDF 2. Check for overlapping elements, clipped text, insufficient margins 3. Verify sufficient color contrast 4. If issues found, fix the code and regenerate 5. Complete at least one fix-verify cycle before finishing ## UI Guidance (from tools-config) **Tool Selection:** - generate_chart: Data charts/graphs (matplotlib, plotly, bokeh) → PNG - create_visual_design: Posters, infographics, artwork, flow diagrams (reportlab, Pillow, svgwrite) → PNG or PDF **Code Requirements:** - Charts: plt.savefig(filename, dpi=300, bbox_inches='tight') - PDF designs: canvas.save() (reportlab) or equivalent - Image designs: image.save(filename) (Pillow) - PNG: dpi=300+ recommended - PDF: A4 or Letter size recommended
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.