Video & Animation

Review docs/prose for Writing Guidelines compliance. Use when asked to

Review UI code for Web Interface Guidelines compliance. Use when asked to

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Use when creating new skills, editing existing skills, or verifying skills work before deployment

React composition patterns that scale. Use when refactoring components with

Deploy applications and websites to Vercel. Use when the user requests deployment actions like

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.

Use when executing implementation plans with independent tasks in the current session

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Evidence-informed marketing and founder-led sales decisions and execution. Use when the user needs to understand customers or markets; choose audiences, positioning, value, pricing, packaging or offers; diagnose weak or changing performance; create or critique marketing communication or brand identity; prioritize founder-led sales; plan or diagnose marketing channel execution across pages, email, social, paid media, search, or commerce; test, localize, or retain learning. Also use when symptoms imply these jobs, such as unclear differentiation, uncertain targeting, weak conversion, conflicting marketing signals, unclear commercial fit, or stalled buyer progress. Do not use for generic writing, mechanical content operations, product-roadmap, legal, finance/accounting, CRM administration, or unrelated technical work.

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.