Skills directory · page 80

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 feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

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

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.

Use when selecting skills for a task or resolving how skill workflows apply

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

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

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

Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

Use when writing or reviewing any visible copy — headlines, buttons, body, errors, empty states — inside a design-method move or standalone.

UX research: personas, journey maps, usability test plans, synthesis. Use whenever the user asks who their users are or why they struggle.

UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.

Screens that never wait on slow jobs, never call a failure empty, use one loader then skeletons, keep the record in the URL. Use for any screen or list.

Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV/HDF5/Arrow/Parquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that don't fit in memory.

Exercise validator failure boundaries with dependency-free malformed, missing-output, route, and publishing fixtures.

Separate the hard constraints that decide whether an option is admissible at all from the soft criteria that rank the admissible ones — then gate before you rank, so a beautiful invalid choice cannot outscore a plain valid one. Use this whenever you are about to pick, shortlist, or recommend from a set: choosing a library or vendor, triaging bugs to fix, screening candidates, selecting a design, or scoring alternatives against a rubric. Also use it when a scoring scheme deducts points for a violation that should have been disqualifying, when someone asks for N options and only two clear the bar, or when you notice a favourite you are about to justify. Not for running the head-to-head comparison once the admissible set exists (that is blind-evaluation), not for wording the final claim (falsifiable-claims), and not for checking your own work is finished (superpowers:verification-before-completion).

Generate value proposition statements for marketing, sales, and onboarding from existing value propositions. Use when writing marketing copy, creating sales messaging, or crafting onboarding messages.

Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.

Builds multiple variants of a component you're working on and helps you iterate and pick one.

Design and operate vector databases for semantic search and RAG: embeddings, indexes (HNSW), filtering, hybrid search, and scaling. Use for AI retrieval.

Maintain ynh vendor adapters against current vendor plugin specs. Use when updating adapters, checking spec compliance, or adding new vendor support.

Use when scoring or auditing vendors: scorecards, SLA compliance and service credits, third-party risk tier or a tier-1 vendor review. Runs vendor_scorer.py, sla_compliance_tracker.py and vendor_risk_classifier.py.

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.

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.

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.

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

Use when marking a task complete, finishing a feature, or claiming a bug fixed -- verifies functional resolution before closing. Do NOT use for lint/quality checks (use sniper AFTER this).

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 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

A comprehensive verification system for Claude Code sessions.

Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.

A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.

A comprehensive verification system for Claude Code sessions.

Sistema de verificación completo para sesiones de Claude Code.

Run the Verify stage end to end: progress, code review, paranoid review, the conditional checks, simplification, and the release review. Use it to close out a completed phase.

Prove a feature the way a user reaches it, with a feature map (one file per feature) and a verification guide. Use after UI changes or to prove behavior.

Run a multi-agent code review that fans out reviewers in parallel and reports only high-confidence findings. Use it to review the changes before they land.

Optional: run a design-system consistency and AI-taste review with gstack /design-review when the change touches the design.

Optional: run an AI-phase evaluation coverage audit with GSD /gsd-eval-review when the phase ships an AI feature.

Optional: run a four-specialist cross-review for a critical release, where the specialists question each other's findings instead of reporting independently.

Verify Paperclip from a source checkout, published npm install, or existing staging or production stack. Select the environment, data state, version, and platform; drive real UI or CLI journeys and capture evidence. Route deployment to the private Cloud skills.

Run the gstack Paranoid Staff Engineer review before a critical-module PR.

Verify the work against its acceptance criteria, then sync the roadmap state and the planning progress file. Run it first in the Verify stage.

Optional: run end-to-end QA with gstack /qa when the change touches the UI.

Optional: ask a second AI model for a peer review when the change touches the orchestration contract itself.