soft-vector
Airy flat-vector spot illustration style — square 1:1 pale-blue canvas, delicate ~1.5-2px dark-navy linework with intentionally OPEN / unclosed outlines, flat color fills, one muted accent hue (mustard / lime-sage / warm-orange / violet), centered subject with generous breathing room, scattered thin-navy micro-marks (dots, plus signs, sparkles, or motion ticks). Trigger when the user says /soft-vector, asks for a "soft-vector illustration", a "friendly UI onboarding illustration", a "thin-line flat spot illustration", or briefs a scene metaphor + palette + complexity in this house style.
What this skill does
# /soft-vector — locked airy flat-vector spot illustration style
Friendly, calm, "modern UI onboarding" spot illustrations. Every piece holds the same locked frame: a soft pale-blue square canvas, delicate dark-navy linework, flat color fills, and one muted accent hue. The signature lift comes from intentionally **open / unclosed outlines** — small visible gaps in rims, handles, ground lines, cloud silhouettes — that keep the artwork feeling hand-drawn rather than mechanical.
Think Storyset / Lottiefiles airy spot art with the airiness pushed harder by the open-line rule.
## Prompt interpretation
The user will usually give a short brief — sometimes just a concept ("morning routine"), sometimes concept + palette ("empty inbox in violet"), sometimes concept + complexity ("focus mode, L3"). Your job is to turn that brief into a complete spot illustration spec without pausing for clarification:
1. **Pick a hero subject** from the brief — a single theme-native object that visually carries the concept. One mug for morning, one mailbox for inbox, one lamp + book + plant for focus. The scene IS the metaphor — never default to generic filing-cabinet + megaphone.
2. **Pick a complexity level** (L1 / L2 / L3) based on how rich the brief is.
3. **Pick a palette accent** that matches the subject's mood (see palette options below).
4. **Pick an accent-mark motif** — dots, plus signs, sparkles, or motion ticks — that fits the subject's emotional world.
5. **Pick 2–3 specific open-line callouts** for the chosen subject. These vary by subject: mug rim gap, handle that doesn't close, ground line that ends in mid-air, cloud silhouette break, lamp arm fade, pot rim gap, etc.
Bias toward subjects that are concrete and iconic — things you can name in one or two words.
## Locked style axes (NEVER vary)
### Canvas
- **Square 1:1**, recommended 1024×1024
- A single **flat pale-blue field** fills the entire canvas — `#EEF1F5`
- No gradient, no border, no horizon, no texture
### Line quality
- **Thin dark-navy outlines, ~1.5–2px** at 1024-wide canvas (delicate, NOT chunky)
- One uniform stroke colour everywhere (a single deep navy, ~`#1F2A44`)
- Uniform stroke weight on each shape — no calligraphic taper, no pencil scratch
- **Rounded line caps** (no flat or square caps)
### Open outlines (the signature)
- Every piece must include several intentionally **unclosed** outlines. Examples by subject:
- Mugs / cups → rim has a small visible gap; handle does not return to the body; steam wisps end as free-floating lines
- Vehicles → ground line ends in mid-air on both sides; one body panel doesn't fully close
- Buildings → roof eaves run past the wall; door jamb doesn't reach the floor
- Plants → pot rim has a tiny gap; one leaf outline breaks at the tip
- Clouds / tree blobs → one or two small visible breaks in the silhouette
- Devices → speech-bubble lines are floating ticks, not closed pills
- This open-line treatment is **non-optional** — it is what distinguishes Soft Vector from generic flat illustration. Always name the specific open-line spots when briefing a model.
### Fill
- **Strictly flat colour** — no gradients, no shading, no ambient occlusion, no inner highlights, no halftone
- One lead accent hue (the chosen palette dial), plus always-available neutrals: soft grey-white `#F4F5F1` and the dark-navy stroke `#1F2A44`
- One optional secondary accent is permitted on L3 vignettes (e.g., warm-orange book cover inside a violet-led desk scene)
### Subject placement
- **Centered**, occupying ~60–75% of the canvas
- Generous breathing room around the subject — pieces never fill edge-to-edge
### Micro-marks
- Scattered decorative marks drawn in the same thin navy stroke
- Vocabulary: tiny dots, small plus signs, four-point sparkles, short motion ticks
- 4–8 marks total — sparse but alive
- Pick **one** motif per piece (a few dots can mix with anything)
### What is NOT in the canvas
- No text, no caption, no headline, no wordmark, no logo, no UI chrome
- No full human figures, no faces
- Humans appear at most as a silhouette behind glass or a partial hand
- No second illustration, no border, no patterned background
## Variable axes (the dials)
These are the only things that should change between pieces.
| # | Dial | What it controls | Options |
|---|---|---|---|
| 1 | **Palette accent** | The single muted hue leading the piece | mustard `#E8B53A` · lime-sage `#A8C95A` · warm-orange `#E87A3A` · violet `#7B6FE0` |
| 2 | **Scene metaphor** | The hero subject + any environment props | coffee mug for morning · bicycle for commute · lamp + book for focus · phone + bell for ping · mailbox for inbox · envelope + note for messages, etc. — always theme-native |
| 3 | **Complexity** | How many props share the canvas | L1 single object hero · L2 object + 1–2 environment props · L3 vignette with 3–5 props composing a scene |
| 4 | **Cast** | Optional human element | none · silhouette-behind-glass · partial hand (never full figures, never faces) |
| 5 | **Accent marks** | The micro-mark motif | dots · plus signs · sparkles · motion ticks |
| 6 | **Action / mood** | Energy in the scene | static · gesture (wave, tilt) · in-motion (rolling wheel, ringing bell) |
### Palette mood pairing hints
- Mustard → warm, welcoming, morning, food / drink, mail
- Lime-sage → outdoor, commute, nature, growth
- Warm-orange → energetic, billing / cards, alerts, activity
- Violet → focus, evening, reading, devices
## Brief template
When generating, expand the user's input into this internal brief before describing the image:
```
Palette accent: <one of mustard / lime-sage / warm-orange / violet, with hex>
Scene metaphor: <one theme-native subject + environment, in one sentence>
Complexity: <L1 / L2 / L3, with prop count>
Cast: <none / silhouette-behind-glass / partial hand>
Accent marks: <one motif, with rough count>
Action / mood: <static / gesture / in-motion>
Open-line spots: <2-3 specific outlines that will be unclosed, named explicitly>
```
## Generation guidance
Models with strong flat-vector handling and crisp uniform stroke output (e.g. `gpt-image-1.5`, `nano-banana-2`, or `gpt-image-2`) produce the most reliable output here. When briefing the model:
- State **explicitly** that the canvas is square 1:1 and the background is a single flat pale-blue `#EEF1F5` field with no gradient, no border, no horizon.
- State **explicitly** the stroke style — thin (~1.5–2px), uniform, dark navy `#1F2A44`, rounded caps, NOT chunky.
- State **explicitly** that several outlines are intentionally **OPEN / unclosed**, and **name the 2–3 specific spots** for this scene (e.g. "the mug rim has a small visible gap, the handle does not return to the body, the steam wisps end as free-floating lines"). Without naming the open-line spots, most models default to fully closed mechanical outlines.
- State **explicitly** that fills are flat — no gradients, no shading, no inner highlights.
- Name the accent-mark vocabulary explicitly — models otherwise default to generic stars / sparkles everywhere.
- State **explicitly** "no text, no logo" — models often slip in extra text on UI subjects (phones, mailboxes).
If the model produces chunky 3–4px outlines, regenerate with stronger emphasis on "thin, delicate, NOT chunky". If outlines are all closed, regenerate with the specific open-line spots called out more aggressively (e.g. "the rim MUST have a visible 4–6px gap on the left").
## Worked examples
Three reference pieces below — one per complexity level — each holds the locked frame and varies the dials.
### Example 1 — coffee mug · mustard · L1 (single object hero)

- Palette accent: mustard `#E8B53A`
- Scene metaphor: ceramic coffee mug with two short steam wisps (morning)
- Complexity: L1 — single object hero
- Cast: none
- Accent marks: plus signs + scattered dots
- Action: static
- Open-line spots: mug rRelated 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.