ash4180
58 verified skills116 total stars
epic
Use when user says "create issues", "break down PRD", "set up epic", "create Linear tasks", "plan sprint", "convert to issues", "draft ticket", "make ticket", "create ticket for [feature]", or wants to transform PRD user stories into Linear epics and sub-issues. Also triggers when user describes a feature idea without a PRD - will use UX skill to gather requirements first.
tools2
explore
Use when user says "explore idea", "quick exploration", "brainstorm feature", "investigate approach", "research options", or wants to do lightweight idea exploration before creating a full PRD. Saves output as markdown file.
data-ai2
writing
Use when user asks to "write a blog post", "create an article", "draft content", "write about [topic]", "help me write", "content writing", "long-form writing", or wants to create blog posts, articles, or other long-form written content. Guides through structured questioning to produce high-quality, audience-focused content.
testing2
react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
development2
vorbit-journey
Use when the user wants to create a user flow diagram, user journey, or FigJam flow visualization.
tools2
implement-loop
Use when user says "implement --loop", "loop mode", "iterate on issues", "auto-continue", or adds --loop flag to implement. Manages autonomous iteration through sub-issues until completion.
tools2
vorbit-cleanup-mocks
Use when the user wants to clean up mock data, prepare for backend handover, or generate API contract documentation.
development2
vorbit-implement-loop
Use when the user wants to iterate autonomously through sub-issues, run implement in loop mode, or auto-continue through an epic's work queue.
tools2
prepare-pr
Prepare a feature branch for PR — strip design files, generate PR body, create the pull request, and post design file references to Linear. Use when user says "prepare PR", "create PR", "ready for review", "ship it", "open PR", "submit PR", "PR time", or wants to finalize a feature branch for merge. Also triggers on "strip designs", "clean up for merge", or "ready to merge". Handles both branches with and without design files.
content-media2
vorbit-figma
Use when the user wants to sync a Figma design system from code, use linked Figma design-system components/tokens, create Figma mockups from a PRD or journey, or plan front-end-ready Figma screens from complex flows.
development2
vorbit-code-review
Use when the user wants a code review, PR review, pre-merge check, or runs the code-review command. Respects shared project rules.
development2
vorbit-cleanup-mocks
Use when the user wants to clean up mock data, prepare for backend handover, or generate API contract documentation.
development2
vorbit-implement-loop
Use when the user wants to iterate autonomously through sub-issues, run implement in loop mode, or auto-continue through an epic's work queue.
tools2
vorbit-implement
Use when the user wants to implement a feature, fix a bug, work from a ticket, or follow Vorbit's coding workflow in a codebase with shared project rules.
development2
vorbit-prototype
Use when the user wants to create a UI prototype, build a mockup with mock data, or generate a quick frontend page that becomes production code.
development2
vorbit-journey
Use when the user wants to create a user flow diagram, user journey, or FigJam flow visualization.
tools2
vorbit-ui-patterns
Use when implementing UI components, building interfaces, creating forms, or any frontend work. Provides opinionated constraints for accessible, performant UI.
development2
vorbit-pencil
Use when the user wants to sync design tokens and components to Pencil, configure Pencil for a project, build a Pencil component library, or set up Pencil canvas rules from a codebase.
development2
vorbit-explore
Use when the user wants to explore an idea, brainstorm a feature, investigate approaches, or do lightweight research before creating a full PRD.
data-ai2
vorbit-implement
Use when the user wants to implement a feature, fix a bug, work from a ticket, or follow Vorbit's coding workflow in a codebase with shared project rules.
development2
vorbit-prd
Use when the user wants to create a Product Requirements Document, write requirements, define a feature, or document a product spec with shared Vorbit rules.
documentation2
vorbit-prepare-pr
Use when the user wants to prepare a feature branch for PR, strip design files, create a pull request, or finalize for merge.
content-media2
vorbit-explore
Use when the user wants to explore an idea, brainstorm a feature, investigate approaches, or do lightweight research before creating a full PRD.
data-ai2
vorbit-epic
Use when the user wants to create Linear issues from a PRD, break down user stories into epics and sub-issues, or plan a sprint.
tools2
vorbit-prepare-pr
Use when the user wants to prepare a feature branch for PR, strip design files, create a pull request, or finalize for merge.
content-media2
vorbit-react-best-practices
Use when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns.
development2
vorbit-verify
Use when the user wants to verify an implementation, validate acceptance criteria, or run a Vorbit-style post-change check using shared project rules.
testing2
vorbit-ui-patterns
Use when implementing UI components, building interfaces, creating forms, or any frontend work. Provides opinionated constraints for accessible, performant UI.
development2
vorbit-prototype
Use when the user wants to create a UI prototype, build a mockup with mock data, or generate a quick frontend page that becomes production code.
development2
vorbit-ux
Use when any skill needs to clarify user experience requirements through exhaustive questioning. Transforms vague requirements into precise acceptance criteria.
testing2
vorbit-ux
Use when any skill needs to clarify user experience requirements through exhaustive questioning. Transforms vague requirements into precise acceptance criteria.
testing2
vorbit-verify
Use when the user wants to verify an implementation, validate acceptance criteria, or run a Vorbit-style post-change check using shared project rules.
testing2
vorbit-pencil
Use when the user wants to sync design tokens and components to Pencil, configure Pencil for a project, build a Pencil component library, or set up Pencil canvas rules from a codebase.
development2
vorbit-webflow
Use when the user wants to build Webflow pages, templates, or components, with or without Figma designs as reference.
development2
vorbit-react-best-practices
Use when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns.
development2
vorbit-code-review
Use when the user wants a code review, PR review, pre-merge check, or runs the code-review command. Respects shared project rules.
development2
vorbit-prd
Use when the user wants to create a Product Requirements Document, write requirements, define a feature, or document a product spec with shared Vorbit rules.
documentation2
vorbit-figma
Use when the user wants to sync a Figma design system from code, use linked Figma design-system components/tokens, create Figma mockups from a PRD or journey, or plan front-end-ready Figma screens from complex flows.
development2
vorbit-webflow
Use when the user wants to build Webflow pages, templates, or components, with or without Figma designs as reference.
development2
canvas-sync
Scan codebase and sync design tokens, components, and conventions to Pencil canvas — or start from scratch using Pencil style guides when no codebase exists. Use when user says "sync canvas", "configure pencil", "setup pencil", "canvas sync", "sync tokens to pencil", "design from scratch", "pick a style guide", or wants Pencil to generate project-aware code. Also triggers on "build component library", "pencil components", "start designing", or when mockup quality from Pencil is poor.
development2
ui-patterns
Use when implementing UI components, building interfaces, creating forms, or any frontend work. Provides opinionated constraints for accessible, performant, consistent UI based on ui-skills.com patterns.
development2
vorbit-epic
Use when the user wants to create Linear issues from a PRD, break down user stories into epics and sub-issues, or plan a sprint.
tools2
prd
Use when user asks to "write PRD", "create requirements", "define feature", "document requirements", "product spec", "clarify user flow", "UX analysis", "edge case analysis", "analyze user stories", "find edge cases", "user journey", or wants to create a complete Product Requirements Document with user stories built through exhaustive questioning.
documentation2
learn
Real-time correction capture with Obsidian-backed context storage. Correction capture triggers mid-session on single keyword. Corrections stored as structured Obsidian notes for accurate root cause analysis.
data-ai2
vorbit-canvas-sync
Use when the user wants to sync design tokens and components to Pencil canvas, configure Pencil for a project, or set up a design system from scratch.
testing2
verify
Use when user says "verify implementation", "check acceptance criteria", "validate feature", "does this meet requirements", "QA check", or wants to confirm code meets the original requirements and passes quality checks.
development2
ux
Senior UX product designer knowledge layer. Called by /explore, /prd, /journey, /figma, /epic, /implement, /verify when they need to clarify UX requirements, check edge-case coverage, validate state design, or look up decision frameworks. Transforms vague requirements into precise acceptance criteria via exhaustive questioning, and serves as the canonical reference for UX patterns across the design chain.
development2
journey
Use when user says "create user flow", "user journey", "flow diagram", "map user steps", "Excalidraw diagram", or wants to visualize user flows. Renders the flow inline in chat with animation, then publishes a shareable Excalidraw URL. **Optional pre-design sketch tool — NOT a chain-required step.** The vorbit designer chain (/explore → /prd → /figma) generates a Flow Page directly inside the Figma file from /prd's flow_steps; use /journey only when you want a standalone diagram for stakeholders or to sketch the flow shape before /prd is written.
tools2
skills/explore
--- 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
tools2
implement
Use when user says "implement this", "build feature", "fix this bug", "code this", "work on issue", "start coding", or asks to implement from a Linear issue or description. Standard TDD workflow for coding tasks.
development2
skills/prd
--- name: prd version: 2.1.0 description: Use when user says "write PRD", "create requirements", "define feature", "document requirements", "product spec", "create ticket", or wants to capture a feature spec as a single Linear ticket. Creates a Linear ticket carrying numbered AC-* acceptance criteria, ordered flow steps with F*-S* IDs + AC tags (Notion-doc format), component mapping intent (kind-of-component per block, NOT concrete DS names — that's /figma's job), state list (empty/loading/error
development2
pencil
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.
development2
skills/figma
--- 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
development2
skills/epic
--- name: epic version: 1.7.0 description: Transform a PRD's user stories into Linear epics and sub-issues. Use whenever the user wants to break down a PRD, create Linear tickets, plan a sprint, decompose a feature into tasks, set up an epic, or convert a user story into implementation work — even if they don't say "epic" explicitly. Common triggers include "create issues", "break down PRD", "set up epic", "epic from VIB-XXX", "create Linear tasks", "plan sprint", "decompose this feature", "sub-
testing2
implement-cleanup-mocks
Use when user says "cleanup mocks", "handover to backend", "remove mock data", "prepare for backend", or wants to clean up mock data and generate API contract docs before backend handover.
development2
review
Use when user says "review this code", "code review", "check my implementation", "review PR", "pre-PR check", or wants brutally honest feedback. Handles both targeted file review and full PR review pipeline.
development2
webflow
Use when user says "build in Webflow", "create Webflow page", "develop Webflow template", "Figma to Webflow", "create Webflow component", "add page slots", "create static page template", "build directly in Webflow", "develop from Figma design", or wants to develop layouts and components in Webflow. Supports pages, templates with page slots, and reusable components - with or without Figma designs.
development2
prototype
Use when user says "create prototype", "build UI mockup", "quick prototype", "mock this feature", "prototype page", or wants to generate UI with mock data that becomes production code by swapping mocks for real API.
development2