ash4180/skills/explore
skills/explore/SKILL.md
--- name: explore version: 1.6.0 description: Use when user says "explore idea", "quick exploration", "brainstorm feature", "investigate approach", or "research options". Lightweight UX/product exploration before a PRD. Block-mines references from Mobbin (and Dribbble/Pinterest via browser MCP) at multiple grains (section/pattern/component/page-archetype/flow), produces a **visual moodboard** with embedded screenshots (not text-only URLs), and saves to Notion. Each mined block becomes a structur
$ install --global
skillsauthnpx skillsauth add ash4180/vorbit skills/exploreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 3:35 AM15.4s2 files scanned
SKILL.md
- name:
- explore
- version:
- 1.6.0
- description:
- Use when user says "explore idea", "quick exploration", "brainstorm feature", "investigate approach", or "research options". Lightweight UX/product exploration before a PRD. Block-mines references from Mobbin (and Dribbble/Pinterest via browser MCP) at multiple grains (section/pattern/component/page-archetype/flow), produces a **visual moodboard** with embedded screenshots (not text-only URLs), and saves to Notion. Each mined block becomes a structured row that feeds /prd's component_mapping_intent. No lo-fi mockups — with a complete linked DS, lo-fi adds no value; references ground decisions in shipped evidence instead.
- > **MCP namespace**:
- This skill uses `mcp__mobbin__*` for primary research and `mcp__claude-in-chrome__*` or `mcp__plugin_playwright_playwright__*` for screenshotting non-Mobbin references (Dribbble / Pinterest / arbitrary URLs). See `_shared/mcp-tool-routing.md` for the Plugin Tool Index and the announce-the-plugin rule.
- > **Locate `_shared/`**:
- This skill ships as a plugin, so `_shared/` files live in the plugin cache, not your project. Before reading any `_shared/...` path below, run `ls -d ~/.claude/plugins/cache/local/vorbit/*/skills/_shared 2>/dev/null | head -1` and use the output as the absolute base for every `_shared/...` reference.
- > **UX patterns reference**:
- Senior UX product designer knowledge lives in `_shared/ux-knowledge/`. When sharpening Step 4 compare-and-contrast prompts, consult `question-matrix.md` for question categories. When checking whether Step 6 options cover edge cases, consult `edge-case-catalog.md`. When user is unsure between approaches, consult `ux-philosophy.md` for decision frameworks. Read directly — no need to invoke `/vorbit:design:ux` for these lookups.
- Exploration is for **UX/product direction**, not implementation. The output document MUST NOT contain frontend file paths, line numbers, LOC estimates, "PR #1 / PR #2" breakdowns, code snippets, Tailwind/CSS classes, component prop names, hex colors, or token IDs. Implementation specifics belong in `/vorbit:
- design:prd` or `/vorbit:implement:implement`. If they surface during exploration, capture them in a single "Follow-up questions for PRD" line and move on.
- **No Figma writes, no lo-fi mockups.** With a complete linked DS available downstream, lo-fi adds no value — it would just be drawing rectangles labeled "card" when the real component is already there. References ground decisions in shipped evidence; lo-fi mockups would invent layouts that bias `/vorbit:
- design:figma`'s Phase 2 mapping. Keep `/explore` research-only.
- ## Step 1:
- Detect Platform & Verify Connection
- ## Step 2:
- Scoping Batch (4 questions)
- ## Step 3:
- Reference Research + Block-Mining — BEFORE deep questions
- Research happens here so the deeper Step 4 questions can be sharpened by what shipped apps do. Beyond Mobbin's flow-level/screen-level synthesis, **mine references at multiple grains** — every reusable insight is a candidate "block" that may feed `/vorbit:
- design:prd`'s Component Mapping Intent.
- **Gate checks:
- **
- c. **Block-mining pass** — for each strong pattern surfaced, ask:
- is this a section, pattern, component, page-archetype, or flow?" Record it as a block with grain, source URL, screenshot URL, 1–2 sentence note, and a proposed_block_name. The proposed_block_name becomes the key in `/vorbit:design:prd`'s Component Mapping Intent. Example: `search-with-filters` (grain: `pattern`, source: Linear inbox, note: search input with inline filter chips, multi-select).
- **Non-Mobbin sources (Dribbble / Pinterest / arbitrary URLs):
- ** Use browser MCP (`mcp__claude-in-chrome__*` or `mcp__plugin_playwright_playwright__*`) to navigate and screenshot. Save the screenshot file path so Step 7 / Step 8 can embed it in the saved doc.
- **Both branches end with:
- **
- 1. **URL coverage check** (`Mobbin URL coverage:
- [N] bullets / [M] URLs`). If N ≠ M, extract missing URLs before continuing.
- 2. **Screenshot coverage check** — every mined block should have a screenshot URL OR a captured screenshot path. Blocks without a visual become text-only fallbacks (record as `screenshot:
- missing`).
- ## Step 4:
- Informed Questions (7-8 more)
- **Probe categories** (regardless of references):
- core functionality, scale, user control, error handling, constraints, real user scenarios.
- ## Step 5:
- Question Quota Gate
- 2. Output:
- **"Questions asked: [N]/10+ (Step 2: [X], Step 4: [Y])"**
- ## Step 6:
- Analyze
- 4. If Step 3 produced reference patterns, weave them in — cite specific apps (e.g., "Option 1:
- Notion-style sidebar + project switcher").
- ## Step 7:
- Draft in Chat
- After showing the draft, ask:
- Does this look good? Ready to save?
- ## Step 8:
- Save Document with Embedded Screenshots
- **Visual moodboard embedding (REQUIRED):
- ** the saved doc must include the screenshot images inline next to each block, not just URLs. Designers think in pixels; URL-only output is designer-hostile.
- **[proposed_block_name]** · grain:
- [section|pattern|component|page-archetype|flow]
- Source:
- [App](URL)
- Note:
- [1–2 sentences on what's interesting]
- This is the structured shape `/vorbit:
- design:prd` consumes to seed its Component Mapping Intent section.
- ## Step 9:
- Report
- - `/vorbit:
- design:figma` — promote the direction to a hi-fi Figma mockup with real library components and Code Connect mapping.
Output Schema & Validation
See ./output-schema.md (sibling of this SKILL.md) for the required sections table, options format, validation rules, the markdown template the agent should populate in Step 7, and the Notion mapping table.
Related Skills
ash4180/pencil
development
VerifiedTrustedCommunity
Sync design tokens and components from a codebase to a Pencil canvas (`.pen` files), or set up a Pencil canvas from a style guide when no codebase exists. Use when the user says "sync pencil", "setup pencil", "configure pencil", "pencil sync", "sync tokens to pencil", "build pencil component library", or names Pencil/`.pen` files explicitly. Also triggers when mockups generated by Pencil don't match project conventions.
2SKILL.mdUpdated May 18, 2026
ash4180/skills/figma
development
VerifiedTrustedCommunity
--- name: figma version: 1.6.0 description: Use when user says "figma", "figma it", "sync figma", "figma mockup", "create figma file", "design to figma", "figma from PRD", "figma from journey", "build in figma", or "figma design system" — anything that creates, syncs, or updates Figma design systems, components, variables, mockups, or front-end-ready screens. Always enumerates the linked Figma library FIRST (library-driven discovery, not per-need search), produces a block→DS mapping table for us
2SKILL.mdUpdated May 18, 2026
ash4180/vorbit-webflow
development
VerifiedTrustedCommunity
Use when the user wants to build Webflow pages, templates, or components, with or without Figma designs as reference.
2SKILL.mdUpdated May 18, 2026
ash4180/vorbit-verify
testing
VerifiedTrustedCommunity
Use when the user wants to verify an implementation, validate acceptance criteria, or run a Vorbit-style post-change check using shared project rules.
2SKILL.mdUpdated May 18, 2026