Skills

Rules and patterns for building UI with shadcn/ui, Tailwind v4, and Motion against a Vois design token set. Use when building components, pages, or any UI that should conform to the workspace design system. Covers spacing, typography, color tokens, component architecture, animation, accessibility, and modern CSS patterns.

Component selection rubrics organized by job-to-be-done. Use after vois-patterns determines structure, before vois-tokens applies tokens. Optionally records each choice via the vois_record_component_choice MCP tool if one is available. Use when deciding between similar components — Dialog vs Drawer, Toast vs Banner, Select vs Combobox, etc.

Structural decision trees for container types, form states, table layouts, and page-level patterns. Use before vois-tokens. Routes to righter skill for all microcopy (labels, errors, buttons, helpers). Use when building pages, forms, features, workflows.

Apply UX content writing principles to review existing UI copy or write new UI copy from scratch. Use this skill whenever someone asks you to: review, audit, critique, or improve UI text, error messages, button labels, tooltips, empty states, onboarding copy, form helper text, or any software interface copy. Also trigger when someone asks you to write new UI copy, label a button, draft an error message, write a modal, or create any in-product text. If the request involves words that appear inside software — use this skill.

Help designers articulate the cognitive science, behavioral psychology, and platform standards behind their design decisions. Use this skill when a designer needs to explain why they made a decision in a critique, design review, or stakeholder meeting. Also use when auditing a screen for principle alignment, preparing for pushback, or evaluating whether a decision is truly irreversible. Trigger on phrases like: "how do I explain this decision", "what principle applies here", "help me defend this", "how would I articulate why I did this", "can you audit this screen", "what's the rationale for", or any request that involves justifying a design choice with evidence beyond personal preference.

Facilitates a structured behavioral assessment interview for IC designer levels, incorporating AI fluency across competency areas. Use this skill when someone wants to run a designer self-assessment, a manager assessment of a designer, or set up an IC level calibration session. Trigger whenever someone mentions designer levels, IC rubric, design assessment, career calibration, manager assessment, or designer growth conversations. Also trigger if someone says they want to evaluate a designer's AI fluency, run a competency interview, or prepare for a calibration meeting.

Write external-facing changelog and release note entries in a pithy, tastefully sassy, occasionally clever voice that makes software updates fun to read without burying what actually shipped. Use this skill whenever someone asks to write, draft, or review a changelog entry, release notes, "what's new" post, or product update announcement for end users. Also trigger when someone pastes a list of shipped features/fixes and wants them turned into public-facing copy, or asks to make a changelog "less boring," "more fun," or "not sound like corporate speak."

Framework-based skill for B2B product positioning, GTM strategy selection, and website messaging. Use when someone asks for help positioning their product, choosing a GTM strategy, writing homepage or website copy, messaging for different buyer personas, content strategy by awareness stage, or ad and landing page copy. Based on the Fletch framework by Anthony Pierri.

Analyze UI mockups, screenshots, or prototype frames to identify all trackable interactions and generate a complete analytics event taxonomy table. Use this skill whenever a designer uploads a screen, mockup, prototype screenshot, or UI frame and wants to know what should be tagged, what events to fire, or how to document analytics for handoff. Also trigger when someone asks to "tag this screen," "identify events," "create a tagging spec," "what should we track," or "build an event table" for any UI. If a designer shares any visual of a UI and mentions analytics, tracking, tagging, GTM, events, or metrics — use this skill.

Unpacks poorly written Jira or Azure DevOps tickets into design-relevant framing. Use this skill whenever a designer pastes in a ticket description, acceptance criteria, or any product/engineering requirement and wants to understand what the actual design work is. Trigger when someone says things like "can you help me understand this ticket," "what is this ticket actually asking for," "decode this ticket," "unpack this AC," "what design work does this require," or pastes raw ticket text and asks what to do with it. Also trigger when a designer mentions they're confused about scope, unclear on requirements, or trying to figure out if something is a content change vs. a flow vs. a new pattern. This skill is especially useful when tickets are written prescriptively (they specify a solution like "add a dropdown") instead of descriptively (explaining the user need), or when acceptance criteria are written from a dev/QA perspective with no design context.