| agent-browser | Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to “open a website”, “fill out a form”, “click a button”, “take a screenshot”, “scrape data from a page”, “test this web app”, “login to a site”, “automate browser actions”, or any task requiring programmatic web interaction. | agent-browser/SKILL.md |
| agent-development | This skill should be used when the user asks to “create an agent”, “add an agent”, “write a subagent”, “agent frontmatter”, “when to use description”, “agent examples”, “agent tools”, “agent colors”, “autonomous agent”, or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins. | agent-development/SKILL.md |
| agent-email-inbox | Webhook signing secret for verifying inbound email event payloads. Returned as signing_secret in the response when you create a webhook via the API. | agent-email-inbox/SKILL.md |
| agent-md-refactor | Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation. | agent-md-refactor/SKILL.md |
| agentation-layout | Process Agentation v3.0 layout mode annotations. Converts drag-and-drop component placements and section rearrangements from the browser toolbar into actual code changes. Use when annotations have kind “placement” or “rearrange,” or when the user says “process layout annotations,” “implement wireframe,” or “apply layout changes. | agentation-layout/SKILL.md |
| agentation-self-driving | Autonomous design critique mode using the Agentation annotation toolbar. Use when the user asks to “critique this page,” “add design annotations,” “review the UI,” “self-driving mode,” “auto-annotate,” or wants an AI agent to autonomously add design feedback annotations to a web page via the browser. Requires the Agentation toolbar to be installed on the target page and agent-browser skill to be available. | agentation-self-driving/SKILL.md |
| agentation-triage | Batch triage and prioritization of Agentation annotations. Fetches all pending annotations across sessions, groups by page/severity/component, creates a prioritized plan, and optionally dispatches parallel agents to resolve them. Use when the user says “triage annotations,” “process all feedback,” “prioritize annotations,” or when there’s a backlog of unprocessed annotations. | agentation-triage/SKILL.md |
| agentation-watch | Hands-free annotation processor. Watches for Agentation annotations via MCP, reads the referenced code, fixes issues, and resolves annotations automatically. Use when the user says “watch for annotations,” “fix annotations,” “hands-free mode,” “fixer loop,” or wants an agent to autonomously process design feedback from the Agentation toolbar. | agentation-watch/SKILL.md |
| agentation | Add Agentation visual feedback toolbar to a Next.js project. Handles installation, component setup with MCP endpoint, and server configuration. | agentation/SKILL.md |
| agentic-eval | | | agentic-eval/SKILL.md |
| ai-elements | Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface. | ai-elements/SKILL.md |
| ai-evals | Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality. | ai-evals/SKILL.md |
| ai-gateway | Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API. | ai-gateway/SKILL.md |
| ai-sdk | Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: “AI SDK”, “Vercel AI SDK”, “generateText”, “streamText”, “add AI to my app”, “build an agent”, “tool calling”, “structured output”, “useChat”. | ai-sdk/SKILL.md |
| api-design-principles | Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards. | api-design-principles/SKILL.md |
| apify-ultimate-scraper | Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, Google Maps, Google Search, Google Trends, Booking.com, and TripAdvisor. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research, content analytics, audience analysis, or any data extraction task. | apify-ultimate-scraper/SKILL.md |
| automate-github-issues | Set up automated GitHub issue triage and resolution using parallel Jules coding agents | automate-github-issues/SKILL.md |
| before-and-after | Captures before/after screenshots of web pages or elements for visual comparison. Use when user says “take before and after”, “screenshot comparison”, “visual diff”, “PR screenshots”, “compare old and new”, or needs to document UI changes. Accepts two URLs (file://, http://, https://) or two image paths. | before-and-after/SKILL.md |
| building-components | Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation. | building-components/SKILL.md |
| canvas-design | Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists’ work to avoid copyright violations. | canvas-design/SKILL.md |
| claude-automation-recommender | Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use. | claude-automation-recommender/SKILL.md |
| claude-md-improver | Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions “CLAUDE.md maintenance” or “project memory optimization”. | claude-md-improver/SKILL.md |
| clerk-backend-api | Clerk backend REST API | clerk-backend-api/SKILL.md |
| clerk-custom-ui | Custom authentication flows and component appearance - hooks (useSignIn, useSignUp), themes, colors, fonts, CSS. Use for custom sign-in/sign-up flows, appearance styling, visual customization, branding. | clerk-custom-ui/SKILL.md |
| clerk-nextjs-patterns | Advanced Next.js patterns - middleware, Server Actions, caching with Clerk. | clerk-nextjs-patterns/SKILL.md |
| clerk-orgs | Clerk Organizations for B2B SaaS - create multi-tenant apps with org switching, role-based access, verified domains, and enterprise SSO. Use for team workspaces, RBAC, org-based routing, member management. | clerk-orgs/SKILL.md |
| clerk-setup | Add Clerk authentication to any project by following the official quickstart guides. | clerk-setup/SKILL.md |
| clerk-testing | E2E testing for Clerk apps. Use with Playwright or Cypress for auth flow tests. | clerk-testing/SKILL.md |
| clerk-webhooks | Clerk webhooks for real-time events and data syncing. Listen for user creation, updates, deletion, and organization events. Build event-driven features like database sync, notifications, integrations. | clerk-webhooks/SKILL.md |
| clerk | Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, organizations, syncing users, or testing. Automatically routes to the specific skill based on their task. | clerk/SKILL.md |
| code-exemplars-blueprint-generator | Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams. | code-exemplars-blueprint-generator/SKILL.md |
| copywriting | When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says “write copy for,” “improve this copy,” “rewrite this page,” “marketing copy,” “headline help,” “CTA copy,” “value proposition,” “tagline,” “subheadline,” “hero section copy,” “above the fold,” “this copy is weak,” “make this more compelling,” or “help me describe my product.” Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing. | copywriting/SKILL.md |
| creating-dashboards | Creates comprehensive dashboard and analytics interfaces that combine data visualization, KPI cards, real-time updates, and interactive layouts. Use this skill when building business intelligence dashboards, monitoring systems, executive reports, or any interface that requires multiple coordinated data displays with filters, metrics, and visualizations working together. | creating-dashboards/SKILL.md |
| deep-agents-memory | INVOKE THIS SKILL when your Deep Agent needs memory, persistence, or filesystem access. Covers StateBackend (ephemeral), StoreBackend (persistent), FilesystemMiddleware, and CompositeBackend for routing. | deep-agents-memory/SKILL.md |
| deploy-to-vercel | 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”. | deploy-to-vercel/SKILL.md |
| design-md | Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files | design-md/SKILL.md |
| design-system-patterns | Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations. | design-system-patterns/SKILL.md |
| design-taste-frontend | Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering. | design-taste-frontend/SKILL.md |
| documentation-templates | Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation. | documentation-templates/SKILL.md |
| documentation-writer | Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework. | documentation-writer/SKILL.md |
| dogfood | Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to “dogfood”, “QA”, “exploratory test”, “find issues”, “bug hunt”, “test this app/site/platform”, or review the quality of a web application. Produces a structured report with full reproduction evidence — step-by-step screenshots, repro videos, and detailed repro steps for every issue — so findings can be handed directly to the responsible teams. | dogfood/SKILL.md |
| electron | Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include “automate Slack app”, “control VS Code”, “interact with Discord app”, “test this Electron app”, “connect to desktop app”, or any task requiring automation of a native Electron application. | electron/SKILL.md |
| email-best-practices | Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing. | email-best-practices/SKILL.md |
| enhance-prompt | Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results. | enhance-prompt/SKILL.md |
| extract-design-system | Extract design primitives from a public website and generate starter token files for your project. | extract-design-system/SKILL.md |
| file-organization | Organize project files and folders for maintainability and scalability. Use when structuring new projects, refactoring folder structure, or establishing conventions. Handles project structure, naming conventions, and file organization best practices. | file-organization/SKILL.md |
| find-skills | Helps users discover and install agent skills when they ask questions like “how do I do X”, “find a skill for X”, “is there a skill that can…”, or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. | find-skills/SKILL.md |
| framer-motion-animator | Creates smooth animations and micro-interactions using Framer Motion including page transitions, gestures, scroll-based animations, and orchestrated sequences. Use when users request “add animation”, “framer motion”, “page transition”, “animate component”, or “micro-interactions”. | framer-motion-animator/SKILL.md |
| frontend-design-system | Produce production-grade UI designs using clear design tokens, layout rules, motion guidance, and accessibility checks for consistent, scalable frontend development. | frontend-design-system/SKILL.md |
| frontend-design | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics. | frontend-design/SKILL.md |
| Frontend Responsive Design Standards | Build responsive, mobile-first layouts using fluid containers, flexible units, media queries, and touch-friendly design that works across all screen sizes. Use this skill when creating or modifying UI layouts, responsive grids, breakpoint styles, mobile navigation, or any interface that needs to adapt to different screen sizes. Apply when working with responsive CSS, media queries, viewport settings, flexbox/grid layouts, mobile-first styling, breakpoint definitions (mobile, tablet, desktop), touch target sizing, relative units (rem, em, %), image optimization for different screens, or testing layouts across multiple devices. Use for any task involving multi-device support, responsive design patterns, or adaptive layouts. | frontend-responsive-design-standards/SKILL.md |
| github-issue-workflow | Provides a structured 8-phase workflow for resolving GitHub issues in Claude Code. Covers fetching issue details, analyzing requirements, implementing solutions, verifying correctness, performing code review, committing changes, and creating pull requests. Use when user asks to resolve, implement, work on, fix, or close a GitHub issue, or references an issue URL or number for implementation. | github-issue-workflow/SKILL.md |
| grill-me | A relentless interview to sharpen a plan or design. | grill-me/SKILL.md |
| grill-with-docs | Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project’s language and documented decisions. | grill-with-docs/SKILL.md |
| improve-codebase-architecture | Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. | improve-codebase-architecture/SKILL.md |
| interface-design | This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns). | interface-design/SKILL.md |
| landing-page-copywriter | Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand. Creates headlines, value propositions, CTAs, and full page sections optimized for conversion. Use when users need landing page copy, sales page content, or marketing website text. | landing-page-copywriter/SKILL.md |
| langchain-rag | INVOKE THIS SKILL when building ANY retrieval-augmented generation (RAG) system. Covers document loaders, RecursiveCharacterTextSplitter, embeddings (OpenAI), and vector stores (Chroma, FAISS, Pinecone). | langchain-rag/SKILL.md |
| langfuse | Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods. | langfuse/SKILL.md |
| langsmith-dataset | INVOKE THIS SKILL when creating evaluation datasets, uploading datasets to LangSmith, or managing existing datasets. Covers dataset types (final_response, single_step, trajectory, RAG), CLI management commands, SDK-based creation, and example management. Uses the langsmith CLI tool. | langsmith-dataset/SKILL.md |
| langsmith-evaluator | INVOKE THIS SKILL when building evaluation pipelines for LangSmith. Covers three core components: (1) Creating Evaluators - LLM-as-Judge, custom code; (2) Defining Run Functions - how to capture outputs and trajectories from your agent; (3) Running Evaluations - locally with evaluate() or auto-run via LangSmith. Uses the langsmith CLI tool. | langsmith-evaluator/SKILL.md |
| langsmith-trace | INVOKE THIS SKILL when working with LangSmith tracing OR querying traces. Covers adding tracing to applications and querying/exporting trace data. Uses the langsmith CLI tool. | langsmith-trace/SKILL.md |
| finetuning | Fine-tune models on Azure AI Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer). | microsoft-foundry/finetuning/SKILL.md |
| capacity | Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments. | microsoft-foundry/models/deploy-model/capacity/SKILL.md |
| customize | Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset). | microsoft-foundry/models/deploy-model/customize/SKILL.md |
| preset | Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize). | microsoft-foundry/models/deploy-model/preset/SKILL.md |
| deploy-model | Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create). | microsoft-foundry/models/deploy-model/SKILL.md |
| microsoft-foundry | Deploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffold, agent.yaml, dataset curation from traces, model fine-tuning (SFT/DPO/RFT). USE FOR: azd ai agent, azd provision/deploy, deploy agent, hosted agent, create agent, add tool to agent, invoke agent, evaluate agent, continuous eval, continuous monitoring, optimize prompt, improve prompt, optimize agent instructions, agent optimizer, deploy model, Foundry project, RBAC, role assignment, permissions, quota, capacity, region, troubleshoot agent, deployment failure, AI Services, create Foundry resource, provision, knowledge index, customize deployment, onboard, availability, fine-tune, SFT, DPO, RFT, training-data, grader, distillation, fine-tuned model, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare). | microsoft-foundry/SKILL.md |
| motion | | | motion/SKILL.md |
| next-forge | Expert assistance for next-forge — a production-grade Turborepo template for Next.js SaaS apps. Triggers on questions about next-forge installation, setup, architecture, packages, customization, deployment, and development workflows. | next-forge/SKILL.md |
| pdf | Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | pdf/SKILL.md |
| pgvector-semantic-search | | | pgvector-semantic-search/SKILL.md |
| postgresql-table-design | Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features | postgresql-table-design/SKILL.md |
| power-bi-report-design-consultation | Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design. | power-bi-report-design-consultation/SKILL.md |
| premium-frontend-design | Create award-winning, cinematic frontend interfaces that feel ALIVE. Combines 10+ years of creative frontend experience with technical excellence. Specializes in WebGL, custom shaders, premium animations, and distinctive aesthetics that would win on Awwwards. Use when building landing pages, dashboards, platforms, or any interface where “generic AI slop” is unacceptable. | premium-frontend-design/SKILL.md |
| rag-architect | Designs and implements production-grade RAG systems by chunking documents, generating embeddings, configuring vector stores, building hybrid search pipelines, applying reranking, and evaluating retrieval quality. Use when building RAG systems, vector databases, or knowledge-grounded AI applications requiring semantic search, document retrieval, context augmentation, similarity search, or embedding-based indexing. | rag-architect/SKILL.md |
| rag-implementation | Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or integrating LLMs with external knowledge bases. | rag-implementation/SKILL.md |
| react:components | Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation. | react-components/SKILL.md |
| react-email | Use when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails. | react-email/SKILL.md |
| react-hook-form | React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, and useFieldArray. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those). | react-hook-form/SKILL.md |
| refactor-plan | Plan a multi-file refactor with proper sequencing and rollback steps | refactor-plan/SKILL.md |
| refactor | Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements. | refactor/SKILL.md |
| remotion-best-practices | Best practices for Remotion - Video creation in React | remotion-best-practices/SKILL.md |
| remotion | Generate walkthrough videos from Stitch projects using Remotion with smooth transitions, zooming, and text overlays | remotion/SKILL.md |
| resend | Webhook signing secret for verifying event payloads. Found in the Resend dashboard under Webhooks after creating an endpoint. | resend/SKILL.md |
| responsive-design | Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior. | responsive-design/SKILL.md |
| sentry-cli | Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI. | sentry-cli/SKILL.md |
| shadcn-ui | Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices. | shadcn-ui/SKILL.md |
| shadcn | Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, —preset codes, or any project with a components.json file. Also triggers for “shadcn init”, “create an app with —preset”, or “switch to —preset”. | shadcn/SKILL.md |
| skill-creator | Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill’s description for better triggering accuracy. | skill-creator/SKILL.md |
| slack | Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include “check my Slack”, “what channels have unreads”, “send a message to”, “search Slack for”, “extract from Slack”, “find who said”, or any task requiring programmatic Slack interaction. | slack/SKILL.md |
| soultrace | Take a personality assessment via the SoulTrace API. Use when the user wants to take a personality test, discover their psychological archetype, understand their personality traits, or get a color-based personality profile. The API uses a 5-color psychological model (White=structure, Blue=understanding, Black=agency, Red=intensity, Green=connection) with Bayesian adaptive question selection to classify users into one of 25 archetypes. Triggers on: personality test, personality assessment, what’s my personality, take a quiz, archetype test, color personality, soultrace. | soultrace/SKILL.md |
| stitch-design | Unified entry point for Stitch design work. Handles prompt enhancement (UI/UX keywords, atmosphere), design system synthesis (.stitch/DESIGN.md), and high-fidelity screen generation/editing via Stitch MCP. | stitch-design/SKILL.md |
| stitch-loop | Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern | stitch-loop/SKILL.md |
| supabase-postgres-best-practices | Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations. | supabase-postgres-best-practices/SKILL.md |
| supabase | Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector). | supabase/SKILL.md |
| superdesign | > | superdesign/SKILL.md |
| tailwind-design-system | Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns. | tailwind-design-system/SKILL.md |
| tanstack-query | Powerful asynchronous state management, server-state utilities, and data fetching for TS/JS, React, Vue, Solid, Svelte & Angular. | tanstack-query/SKILL.md |
| tanstack-table | Headless UI for building powerful tables & datagrids for TS/JS, React, Vue, Solid, Svelte, Qwik, Angular, and Lit. | tanstack-table/SKILL.md |
| Tavus | Use when building real-time video conversations with AI replicas, creating personas with specific behaviors, training digital humans, generating videos, or integrating conversational AI into applications. Reach for this skill when working with the Conversational Video Interface (CVI) pipeline, configuring persona layers, managing replicas, or handling knowledge base integration. | tavus/SKILL.md |
| team-builder | Interactive agent picker for composing and dispatching parallel teams | team-builder/SKILL.md |
| travel-planner | This skill should be used whenever users need help planning trips, creating travel itineraries, managing travel budgets, or seeking destination advice. On first use, collects comprehensive travel preferences including budget level, travel style, interests, and dietary restrictions. Generates detailed travel plans with day-by-day itineraries, budget breakdowns, packing checklists, cultural do’s and don’ts, and region-specific schedules. Maintains database of preferences and past trips for personalized recommendations. | travel-planner/SKILL.md |
| trigger-tasks | Build AI agents, workflows and durable background tasks with Trigger.dev. Use when creating tasks, triggering jobs, handling retries, scheduling cron jobs, or implementing queues and concurrency control. | trigger-tasks/SKILL.md |
| typescript-advanced-types | Master TypeScript’s advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects. | typescript-advanced-types/SKILL.md |
| ui-ux-pro-max | UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples. | ui-ux-pro-max/SKILL.md |
| velt-activity-best-practices | Velt Activity Logs implementation patterns and best practices for React, Next.js, and web applications. Use when adding real-time activity feeds, custom activity logging, audit trails, CRDT debounce configuration, server-side activity management via REST API, customizing the Activity Log wireframe with template variables (velt-data, velt-if, velt-class), or composing the VeltActivityLogWireframe sub-component tree (Header, Filter, List, DateGroup, Item, ShowMore, Empty, Loading). | velt-activity-best-practices/SKILL.md |
| velt-approval-engine-best-practices | Best practices for the Velt Approval Engine — the declarative workflow runtime for multi-step agent + human approval processes. Use whenever the user is building approval workflows, multi-step review processes, agent-then-human approval chains, parallel reviewer quorums, SLA-aware approval steps, rejection-loop retry regions, or any workflow that combines AI agents with human gatekeeping. Triggers on any task involving the Velt Approval Engine, /v2/workflow/ REST endpoints, workflow definitions (nodes/edges/groups/loops), executions dispatch with idempotencyKey, recording reviewer decisions or agent resolutions, workflow webhooks (execution.dispatched/completed/failed/cancelled, step.awaiting-approval/completed/failed/breached/cancelled, group.quorum-met, loop.iteration-started, loop.exhausted), HMAC-SHA256 webhook signature verification, SLA-routed breach edges, quorum policies (waitAll/cancelOnQuorum/joinOnQuorum), onReject shorthand, loop regions, or recovering missed webhook events via /executions/getEvents with sinceSeq — even if the user does not explicitly say ‘Approval Engine’. | velt-approval-engine-best-practices/SKILL.md |
| velt-area-best-practices | Best practices for Velt Area Comments — the rectangle area-annotation feature that lets users draw a region on the page and attach a comment thread to it (Figma-style ‘draw a box and comment’). Use whenever the user is toggling area comments on or off (areaComment prop on VeltComments, or commentElement.enableAreaComment / disableAreaComment), customizing the area pin via the velt-area-pin-portal-wireframe tag, binding componentConfig.areaPinAnnotation / componentConfig.selected / componentConfig.isResizing / componentConfig.hideAreaAnnotation template variables, or reading the AreaAnnotation data model (annotationId, from, targetElements, areaProperties, targetAnnotations linking back to comments). Trigger on any task involving Velt area comments, rectangle annotations on documents, draw-a-box-and-comment UI, area pin customization, or the AreaAnnotation / AreaProperty / AreaTargetAnnotation shapes — even if the user does not explicitly say ‘Velt’ or ‘area comments’. | velt-area-best-practices/SKILL.md |
| velt-arrows-best-practices | Best practices for Velt Arrows — the directional arrow annotation feature that lets users draw arrows pinned to DOM elements for visual feedback, design review, or collaborative pointing. Use whenever the user is adding Velt Arrows to their app, placing the VeltArrows or VeltArrowTool components, restricting arrows to specific DOM regions via allowedElementIds, enabling dark mode, customizing the arrow tool button (CSS ::part hooks or full custom-button slot replacement), reading the ArrowAnnotation data model (annotationId, from, targetElement, position, props.arrowLength / props.arrowAngle), or working with the ArrowElement API (client.getArrowElement). Triggers on any task involving Velt Arrows, drawn arrow pins, arrow annotations, directional pointing UI, design-review arrows, the VeltArrows / VeltArrowTool / velt-arrows / velt-arrow-tool web components, or ArrowAnnotation — even when the user does not explicitly say ‘Velt’ or ‘arrows’. | velt-arrows-best-practices/SKILL.md |
| velt-chat-sdk-adapter-best-practices | Velt Chat SDK Adapter implementation patterns and best practices for building bots that integrate with Velt comment threads. Use when building a bot (greeting bot, AI bot, support bot) that responds to @-mentions in Velt comments, handling webhook events from Velt (comment.add, comment.reaction_add), configuring the Chat SDK with createVeltAdapter, setting up webhook routes in Next.js or other Node.js frameworks, handling reactions on Velt comments, resolving user identities for bot responses, or deploying a Velt-connected bot to Vercel or other platforms. Triggers on any task involving @veltdev/chat-sdk-adapter, Chat SDK adapters for Velt, Velt bot integration, Velt webhook handling for comments, onNewMention, onReaction, thread.post(), or building an automated responder for Velt comment threads — even if the user doesn’t explicitly say ‘chat SDK adapter’. | velt-chat-sdk-adapter-best-practices/SKILL.md |
| velt-comments-best-practices | Velt Comments implementation patterns and best practices for React, Next.js, and web applications. Use when adding collaborative commenting features, comment modes (Freestyle, Popover, Stream, Text, Page), rich text editor comments (TipTap, SlateJS, Lexical), media player comments, chart comments, comments sidebar setup and customization (embed mode, floating mode, focused thread, V2 sidebar), sidebar filtering with accessModes for privacy, isAnnotationPrivate() visibility routing, CommentDialogActionService.isSubmitInFlight() for duplicate-submit guards, VeltCommentDialogAgentSuggestion primitives for AI suggestion accept/reject UIs, agent comment annotations via REST API (agent block with agentSource/agentId/executionId, agent-specific GET filters, suggestionAccepted/suggestionRejected client events, sourceType “agent” UI rendering), or binding Comment Bubble / Comment Dialog / Comment Tool wireframe slots via template variables (velt-data, velt-if, velt-class). | velt-comments-best-practices/SKILL.md |
| velt-crdt-best-practices | Velt CRDT (Yjs) collaborative editing best practices for real-time applications. This skill should be used when implementing collaborative features using Velt CRDT stores, integrating with editors like Tiptap, BlockNote, CodeMirror, or ReactFlow, or debugging sync issues. Triggers on tasks involving real-time collaboration, multiplayer editing, CRDT stores, or Velt SDK integration. | velt-crdt-best-practices/SKILL.md |
| velt-cursors-best-practices | Velt Cursors implementation patterns and best practices for React, Next.js, and web applications. Use when adding real-time cursor tracking, collaborative cursor sharing, avatar-mode cursors, cursor element whitelisting, cursor inactivity timeouts, cursor position subscriptions, customizing the cursor pointer wireframe and its flat-config componentConfig template variables (cursorUser, showAvatar / showAudio / showVideo, huddle-on-cursor flags, helper functions), or customizing the Live Selection remote-user indicator wireframe (VeltSelectionElementPortalWireframe / velt-selection-element-portal, live-selection, selection-element-portal, userIndicatorPosition / userIndicatorType, selections). Triggers on any task involving live cursors, collaborative cursor display, live selection indicators, VeltCursor, VeltCursorPointerWireframe, VeltSelection*, cursor tracking on canvas or whiteboard, or showing where other users are pointing or selecting — even if the user doesn’t explicitly say ‘cursors’ or ‘live-selection’. | velt-cursors-best-practices/SKILL.md |
| velt-huddle-best-practices | Velt Huddle implementation patterns and best practices for React, Next.js, and web applications. Use when adding audio/video/screen sharing huddles, in-app voice or video calls, ephemeral chat within huddles, flock mode (follow me), cursor-mode huddle bubbles, or huddle webhook integration. Triggers on any task involving huddles, video calls, audio calls, screen sharing sessions, VeltHuddle, VeltHuddleTool, or collaborative real-time communication features — even if the user doesn’t explicitly say ‘huddle’. | velt-huddle-best-practices/SKILL.md |
| velt-live-state-sync-best-practices | Velt Live State Sync implementation patterns and best practices for React, Next.js, and web applications. Use when adding real-time shared state, syncing data across clients, Redux store synchronization, or live variables. Triggers on any task involving Velt live state, useLiveState, useSetLiveStateData, useLiveStateData, useLiveStateSyncUtils, createLiveStateMiddleware, getLiveStateSyncElement, live state broadcast API, real-time collaborative state, or building shared-state features — even if the user doesn’t explicitly say ‘live state sync’. | velt-live-state-sync-best-practices/SKILL.md |
| velt-node-sdk-best-practices | Velt Node SDK (@veltdev/node) implementation patterns for Node.js / TypeScript backends. Use whenever the user is writing server-side code that integrates with Velt — initializing VeltSDK, calling sdk.api.* (REST API services like Organizations, Documents, Comment Annotations, etc.) or sdk.selfHosting.* (MongoDB+S3 self-hosted services like Comments, Reactions, Attachments), generating JWT auth tokens for the frontend SDK from Node, configuring MongoDB or AWS S3 for self-hosting, handling the SDK’s typed error classes (VeltSDKError, VeltDatabaseError, VeltValidationError, VeltTokenError, VeltApiError), debugging response-envelope mismatches between the two backends, or shipping Node code that talks to Velt in any way. Triggers on any mention of @veltdev/node, VeltSDK, sdk.api, sdk.selfHosting, Velt server-side Node.js, MongoDB-backed Velt storage, or env-var auth (VELT_API_KEY / VELT_AUTH_TOKEN) — even if the user doesn’t say “Node SDK” explicitly. | velt-node-sdk-best-practices/SKILL.md |
| velt-notifications-best-practices | Velt Notifications implementation patterns and best practices for React, Next.js, and web applications. Use when adding in-app notifications, notification panels, email notifications via SendGrid, webhook integrations, user notification preference management, cross-organization notification feeds with enableCrossOrganization/disableCrossOrganization, or binding Notifications Panel / Notifications Tool wireframe slots with template variables (velt-data, velt-if, velt-class). | velt-notifications-best-practices/SKILL.md |
| velt-presence-best-practices | Velt Presence implementation patterns and best practices for React, Next.js, and web applications. Use when adding user presence avatars, online/away/offline status indicators, real-time cursor tracking, inactivity timeout configuration, location-based presence filtering, presence data subscriptions, or flock mode (follow me) shared navigation sessions with enableFlockMode, startFollowingUser, stopFollowingUser, onNavigate callback, and defaultFlockNavigation. Triggers on any task involving user presence, active user avatars, who’s online indicators, cursor sharing, VeltPresence, VeltCursor, follow-along features, or collaborative awareness features — even if the user doesn’t explicitly say ‘presence’. | velt-presence-best-practices/SKILL.md |
| velt-proxy-server-best-practices | Velt proxy server setup and configuration best practices for routing Velt SDK traffic through your own reverse proxy (nginx or Cloudflare Workers). Use when configuring proxyConfig on VeltProvider or initVelt, setting up nginx or Cloudflare Workers as a reverse proxy for Velt CDN/API/database/storage/auth endpoints, whitelisting Content Security Policy (CSP) domains for Velt, enabling Subresource Integrity (SRI), or debugging proxy-related connectivity issues. Triggers on any task involving Velt proxy, reverse proxy, proxyConfig, cdnHost, apiHost, v1DbHost, v2DbHost, storageHost, authHost, forceLongPolling, CSP whitelisting for Velt, nginx or Cloudflare Workers configuration for Velt, or network policy compliance with Velt — even if the user doesn’t explicitly say ‘proxy’. | velt-proxy-server-best-practices/SKILL.md |
| velt-reactions-best-practices | Best practices for Velt Inline Reactions — the emoji-reaction feature for adding contextual emoji feedback to elements of your app (articles, posts, images, charts, custom UI). Use whenever the user is adding the VeltInlineReactionsSection component, binding it to a target element via targetReactionElementId, configuring custom reaction emojis (image URLs, iconUrl, or unicode emoji) via setCustomReactions, calling client.getReactionElement(), customizing the wireframe primitives (velt-reaction-tool-wireframe, velt-reaction-pin-wireframe, velt-inline-reactions-section-wireframe, and their nested reactions-panel / tooltip children), binding componentConfig.* template variables (annotation, isReactionSelectedByCurrentUser, tooltipVisible, annotations, targetReactionElementId), or reading the ReactionAnnotation data model. Trigger on any task involving Velt reactions, emoji reactions on content, inline-reactions UI, contextual emoji feedback, or VeltInlineReactionsSection — even if the user does not explicitly say ‘Velt’ or ‘reactions’. | velt-reactions-best-practices/SKILL.md |
| velt-recorder-best-practices | Velt Recorder implementation patterns and best practices for React, Next.js, and web applications. Use when adding audio, video, or screen recording features, recording playback, video editing, recording transcription, managing recording lifecycle events, or binding Recorder wireframe slots with template variables (velt-data / velt-if / velt-class). | velt-recorder-best-practices/SKILL.md |
| velt-rest-apis-best-practices | Velt REST API v2 and webhook best practices for server-side integration. Use when calling Velt REST API v2 endpoints, generating JWT tokens for frontend authentication, handling Velt webhooks (comment events, huddle events, CRDT updates), managing users/documents/organizations via REST, or implementing server-side Velt operations. Triggers on any task involving Velt REST API, JWT token generation for Velt, Velt webhooks, x-velt-api-key headers, or server-side comment/notification/activity management — even if the user doesn’t explicitly say ‘REST API’. For the Python SDK (velt-py) for self-hosting, see velt-self-hosting-data-best-practices instead. | velt-rest-apis-best-practices/SKILL.md |
| velt-rewriter-best-practices | Best practices for the Velt Rewriter — the AI text-rewriter feature that lets users select text and apply AI-generated rewrites or anchor AI-assisted comments. Use whenever the user is integrating the Velt Rewriter, calling enableRewriter/disableRewriter, subscribing to textSelected events, calling askAi (multi-provider AI generation auto-routed by model prefix across OpenAI/Anthropic/Gemini), calling replaceText to swap DOM text, calling addComment to anchor a Velt comment to a text range, toggling the default selection toolbar with enableDefaultUI/disableDefaultUI, building custom rewriter UI with the wireframe variables (componentConfig.* on velt-rewriter-text-portal-wireframe / velt-rewriter-dialog-wireframe / velt-rewriter-bottom-sheet-wireframe), or typing against RewriterAskAiRequest / RewriterReplaceTextRequest / RewriterAddCommentRequest / AiModel. Trigger even if the user does not say ‘Velt’ explicitly — any mention of an AI text rewriter, in-place text replacement after AI generation, selection-toolbar AI prompt, or AI rewrite suggestions anchored to text ranges should pull this skill. | velt-rewriter-best-practices/SKILL.md |
| velt-self-hosting-data-best-practices | Velt self-hosting data implementation patterns and best practices for React, Next.js, and web applications. Use when storing sensitive user-generated content (comments, attachments, reactions, recordings, user PII) on your own infrastructure instead of Velt servers, implementing data providers (endpoint-based or function-based), building backend API routes, or debugging data provider events. | velt-self-hosting-data-best-practices/SKILL.md |
| velt-setup-best-practices | Velt collaboration SDK setup guide for React, Next.js, Angular, Vue, and HTML applications. Use this skill when setting up Velt for the first time, configuring VeltProvider, implementing user authentication with authProvider and JWT tokens, initializing document collaboration with setDocuments, adding VeltUserInviteTool for share & invite flows, or debugging Velt setup issues. Triggers on any task involving Velt installation, VeltProvider configuration, auth token generation, document identity setup, share/invite components, or project structure for Velt integration — even if the user doesn’t explicitly mention “setup”. | velt-setup-best-practices/SKILL.md |
| velt-single-editor-mode-best-practices | Velt Single Editor Mode implementation patterns and best practices for React, Next.js, and web applications. Use when implementing exclusive editing access, editor/viewer role management, access request handoff flows, element-level sync control, timeout-based editor transfer, or multi-tab editing restrictions. | velt-single-editor-mode-best-practices/SKILL.md |
| velt-suggestions-best-practices | Velt Suggestions implementation patterns and best practices for React, Next.js, and web applications. Use when adding suggestion mode (propose-then-review workflow), AI agent suggestion comments, accept/reject flows, suggestion targets on form inputs or custom components, suggestion status lifecycle (pending/accepted/rejected/stale), drift detection, or querying suggestions programmatically. Triggers on any task involving Velt suggestions, suggestion mode, data-velt-suggestion-target, SuggestionElement, useSuggestionUtils, enableSuggestionMode, commitSuggestion, suggestionAccepted, suggestionRejected, or building a propose-and-review editing workflow — even if the user doesn’t explicitly say ‘suggestions’. | velt-suggestions-best-practices/SKILL.md |
| velt-view-analytics-best-practices | Best practices for Velt View Analytics — the ‘who viewed this document today’ indicator with a count badge, recent-viewers dialog, and date- or user-aggregated subscriptions. Use whenever the user is adding the VeltViewAnalytics component, scoping it to a sub-document via type=‘location’ + location-id, reading unique-view counts via the React hooks (useUniqueViewsByUser / useUniqueViewsByDate) or the non-React observable form (client.getViewsElement().getUniqueViewsByUser/ByDate().subscribe), building a custom trigger or viewer-list overlay via the velt-view-analytics-wireframe / velt-view-analytics-dialog-wireframe / velt-view-analytics-bottom-sheet-wireframe tags, or binding componentConfig.* template variables (todayViewsCount, totalUniqueViewsCount, treadsVisible, userViews, bottomSheetMode). Trigger on any task involving Velt View Analytics, document view counts, recent-viewers lists, viewers-by-date trends, view aggregation, or VeltViewAnalytics customization — even when the user does not explicitly say ‘Velt’ or ‘view analytics’. | velt-view-analytics-best-practices/SKILL.md |
| vercel-composition-patterns | Composition patterns for building flexible, maintainable React components. Avoid | vercel-composition-patterns/SKILL.md |
| vercel-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. | vercel-react-best-practices/SKILL.md |
| verification-before-completion | 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 | verification-before-completion/SKILL.md |
| web-design-guidelines | Review UI code for Web Interface Guidelines compliance. Use when asked to “review my UI”, “check accessibility”, “audit design”, “review UX”, or “check my site against best practices”. | web-design-guidelines/SKILL.md |
| writing-plans | Use when you have a spec or requirements for a multi-step task, before touching code | writing-plans/SKILL.md |
| yjs-best-practices | Yjs CRDT best practices for building real-time collaborative applications. Use this skill when implementing collaborative editing, real-time sync, shared data structures, or any feature using Yjs (Y.Doc, Y.Text, Y.Array, Y.Map, Y.XmlFragment). Triggers on tasks involving Yjs, CRDTs, collaborative editors, y-websocket, y-webrtc, y-indexeddb, y-prosemirror, y-codemirror, y-quill, y-monaco, awareness/presence, undo/redo with shared types, or any mention of real-time document collaboration — even if the user doesn’t explicitly say ‘Yjs’. | yjs-best-practices/SKILL.md |
