vm0-illustration
Generate vm0-style vm0 in-app spot illustrations: bold hand-drawn ink line art with white-filled interiors, a soft rounded color backdrop, transparent output, and simple iconic metaphors for product states.
What this skill does
# vm0 Illustration Use this register-only image style when the user asks for a vm0 in-app spot illustration, empty-state artwork, billing/permission/error state artwork, or a small product UI illustration in the vm0 style. This style is separate from Notion Illustration. Notion Illustration is black brush-pen editorial character artwork on pure white. vm0 Illustration is a vm0 product illustration style built around a single iconic object or metaphor, white-filled line art, and one soft color backdrop. ## Locked Style - Square spot illustration, usually 1024 x 1024. - Transparent final background in the delivered artifact. - Preferred generation setup: generate on a flat full-canvas warm gray background (`#eeeeee`), then remove only that gray background to transparency. This preserves pure-white object interiors. Direct transparent-background generation often creates unwanted glow/vignette and gray object fills. - One central product metaphor or object, not a character scene. - Bold confident black brush-pen ink line drawing, with thick chunky decisive strokes and natural hand-drawn wobble. Lines should look committed and drawn once, not ruler-straight or vector-clean. - Outlines have intentional small gaps and breaks for a breathy hand-drawn quality. - Minimal detail: only essential contours and one or two key details. No fine textures, no crosshatching, no heavy shading. - Pure white (`#FFFFFF`) filled interior inside the line art so the drawing stays opaque over the color shape. The interior must not be gray, dark, shaded, translucent, or blended with the backdrop. - The black ink drawing sits firmly on top of the white fill. Where the subject overlaps the color block, the white-filled object completely hides the color underneath. - One solid opaque flat soft-rounded color block behind the drawing, like a halo, chunky oval, generous pill, or rounded-square badge. - The color block has no gradient, no watercolor, no texture, no glow, and no transparency. Slightly imperfect hand-drawn edges are fine. - The color block supports the drawing; it should not fully contain it. - The drawing extends beyond the color block on at least 2-3 sides. - The color block occupies roughly 30-40% of the canvas and may be slightly off-center or rotated for editorial flair. - The full composition fills roughly 60-75% of the canvas with generous breathing room around it. - Pixels outside the line art and color block must be transparent in the final artifact. Do not add any glow, vignette, cast shadow, ambient lighting, gray paper, or background wash. - No logo, no text, no letters, no numbers, no UI chrome, no watermark, no border, no third color. ## Color Direction Prefer one accent color from the vm0 avatar/product palette: - yellow: `#EDC43E` - teal: `#3EB7B8` - grey: `#97918A` - pink: `#FF81B2` - brown: `#E88033` - wheat: `#EDC183` - light pink: `#F3BAB1` - sienna: `#C77242` - peach: `#EBC2AA` Pick one color per image. Use vibrant colors for friendly states and warmer neutral colors for permission, billing, or security states. Use pink sparingly. ## Prompt Construction Turn the user's request into a short concrete metaphor, then generate one polished image in this style. Good metaphors: - no permission: a chunky padlock with a rounded shackle and keyhole, with a small key beside it - empty schedule: a simple calendar page with one loose checkmark and a small sparkle - empty chat: two rounded speech bubbles overlapping, one with a small sparkle - billing plan: a small receipt or stacked card with a coin and checkmark - product update: a gift box with lid lifting and a few sparkles - retry/loop: two curved arrows chasing each other in a circular refresh loop Use a concise prompt with these constraints. If the generation tool supports background removal or post-processing, prefer the warm-gray-background workflow: ```text vm0-style vm0 in-app spot illustration of <metaphor>. Square 1:1 spot illustration on a flat full-canvas warm gray #eeeeee background that will be removed to transparency after generation. Bold confident black brush-pen ink line art with thick chunky decisive strokes, natural hand-drawn wobble, and intentional small contour breaks. The object has an opaque pure white #FFFFFF filled interior, not gray, not dark, not shaded, and not blended with the backdrop. The white-filled object sits on top of a single solid opaque flat soft-rounded <color name> color block using <hex>, like a pill, chunky oval, or rounded-square halo. The color block has no gradient, no watercolor, no texture, no glow, and no transparency. The drawing extends beyond the color block on at least 2-3 sides and fills 60-75% of the canvas. Minimal iconic detail only. No text, no letters, no numbers, no logo, no UI, no border, no shadows, no glow, no vignette, no hatching, no third color. ``` If direct transparent-background generation is the only available path, keep the same style constraints and additionally require that all pixels outside the drawing and color block are fully transparent. Be strict about no glow/vignette and pure white subject interiors, because direct transparent generation tends to drift there. ## Evaluation Checklist - The image reads as one simple iconic product metaphor. - The line art is bold and hand-drawn, not vector-clean. - The object interior is pure white-filled, not transparent, gray, dark, shaded, or backdrop-colored. - The color block sits behind the drawing and does not trap it inside. - The color block is solid flat color, not gradient/watercolor/textured. - The final background is transparent. - There is no glow, vignette, cast shadow, gray wash, or background outside the color block. - There is no text, letters, numbers, logo, UI chrome, border, watermark, or third color.
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.