Skills
100,344 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Load PROACTIVELY when task involves designing or building UI components. Use when user says "build a component", "create a form", "add a modal", "design the layout", or "refactor this page". Covers component composition and hierarchy, prop design and typing, render optimization (memo, useMemo, useCallback), compound component patterns, controlled vs uncontrolled forms, file organization, and accessibility for React, Vue, and Svelte.
Preview React components with real Mantine + Tailwind styling using Ladle. Use when modifying UI components, fixing visual bugs, or when the user asks to see what a component looks like. Creates Ladle stories, captures screenshots in dark/light mode, and presents them for review. Use proactively after UI changes.
Use when implementing any substantial feature, multi-file modification, or architectural change - produces a plain-language walkthrough of every alteration so the developer can verify genuine understanding before committing, preventing the accumulation of cognitive debt where code ships faster than comprehension
Write git commit messages that follow the Conventional Commits v1.0.0 spec. Use this whenever you are about to author a commit on the user's behalf, prepare or run `git commit`, suggest or clean up a commit message, split a diff into commits, write a PR title/description that references commits, or generate a CHANGELOG from history — even when the user never says "conventional commits". If a commit message is being written in a git repo, this skill applies.
Convert Docker Compose files to Coolify templates. Use when creating Coolify services, converting docker-compose.yml for Coolify deployment, working with SERVICE_URL/SERVICE_PASSWORD magic variables, or troubleshooting Coolify compose errors.
Expert Core Data guidance (iOS/macOS): stack setup, fetch requests and NSFetchedResultsController, saving and merge conflicts, threading and Swift Concurrency, batch operations and persistent history, migrations, performance, and NSPersistentCloudKitContainer/CloudKit sync.
Garnish — Craft CMS's built-in JavaScript UI toolkit for the control panel. ALWAYS load when writing, editing, or reviewing JavaScript that runs in the Craft CP — plugin CP assets, custom field type JS, element index JS, CP webpack config, or code importing garnishjs / referencing window.Garnish. Also for CP accessibility, keyboard interactions, drag-sort, and CP JS memory issues.
Plans a change as an ADR that records the decision, plus an implementation plan that belongs to it. Use this skill when the user asks to plan a feature or change, or to revise an existing plan or ADR. Do not use for implementing a plan (use implement-plan) or for small changes that involve no real decision.
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
Create a Work Breakdown Structure (WBS) and WBS Dictionary from project charter deliverables. Covers hierarchical decomposition, WBS coding, effort estimation, dependency identification, and critical path candidates. Use after a project charter is approved, when planning a classic or waterfall project with defined deliverables, breaking a large initiative into manageable work packages, or establishing a basis for effort estimation and resource planning.
Detect what changed between two page snapshots with fastCRW — stateless diff as a REST primitive. Use when you need to track content changes, monitor a page for updates, or build a cron-based alert system: "has this page changed?", "alert me when pricing changes", "diff this week's scrape against last week's". Step 7 of the crw workflow ladder.
Find and frame customer conversations through warm intros, communities, casual chats, events, advisors, landing-page replies, and meeting requests. Use when a team needs people to interview, cold outreach is failing, a meeting ask sounds needy or pitchy, or customer discovery needs a credible reason to talk.
Plan and audit customer discovery conversations that produce concrete evidence instead of compliments, opinions, hypotheticals, or feature-request noise. Use when planning customer interviews, rewriting interview scripts, validating startup ideas before building, avoiding biased questions, or applying Mom Test-style customer learning.
Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions. Use when synthesizing raw customer notes, avoiding founder interpretation bottlenecks, extracting quotes and signals, updating beliefs, or deciding what to ask next.
Vercel Daemons guidance — long-running background workers built from a Dockerfile and declared under the `daemons` key in vercel.json. Use when running queue consumers, Celery/Sidekiq/BullMQ workers, workflow workers, or job runners next to an app on Vercel; configuring daemon instances per region, memory, or command; handling SIGTERM; or choosing between Daemons, Functions, Queues, and Workflows.
VGV-specific reference for bumping Dart and Flutter SDK constraints across packages, covering pubspec.yaml environment constraints, CI workflow Flutter versions, and SDK upgrade PR preparation. Use it when upgrading the Flutter or Dart SDK version in any VGV repository, on phrases like "bump Flutter to 3.x", "update SDK constraints", "upgrade Dart SDK", "update CI Flutter version", "bump SDK version", or "prep the SDK upgrade PR", and also when a bump is already underway and something breaks: "pub get fails after I changed the environment block", "version solving failed after bumping the SDK", "a dependency requires an older SDK", "get me unblocked on the Flutter upgrade", or "which Dart version ships with Flutter 3.x". It owns the whole bump, including the conflicts it surfaces, even when the blocking package has a skill of its own.
Answer questions using Darwin's evolutionary thinking, patient observation, and resistance to confirmation bias. Use when the user explicitly asks for this figure's perspective, mentions "darwin-perspective", or wants to apply his core methods to analyze a problem; do not trigger automatically for general questions.
Database performance audit — detects N+1 queries, missing indexes, join opportunities, slow queries, EXPLAIN analysis, and per-endpoint DB call counts. Use when asked to "optimize the database", "find slow queries", "check for N+1", "analyze query performance", or "audit DB calls".
Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows.
Debug web and Node.js applications using console inspection, network analysis, and non-blocking code debugging. Use when the user reports bugs, wants to debug JavaScript (browser or backend), inspect network requests, troubleshoot page/API issues, trace function calls, or monitor exceptions.
Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration. Supports Next.js, Vite, React, Node.js, Python, Go, Rust, Java, and C# applications. Use when the user wants to: (1) Deploy their app to Temps, (2) Set up CI/CD with Temps, (3) Configure deployment settings, (4) Create a Dockerfile for Temps, (5) Deploy a containerized application, (6) Set up automatic deployments from Git. Triggers: "deploy to temps", "temps deployment", "push to temps", "containerize for temps", "temps ci/cd".
Reference for StreamSets Data Collector engines and StreamSets environments — StreamSets environment configuration, StreamSets engine deployment (Docker/Podman), StreamSets job execution, StreamSets engine communication methods (tunneling/direct), StreamSets high availability and failover, StreamSets monitoring and resource management. Use ONLY when the user explicitly mentions StreamSets, Data Collector, or a StreamSets-specific concern.
China city mobility service. Must use this skill whenever the user expresses any transportation need — including ride-hailing/taxi/car-booking, price checks, route planning (transit/driving/walking/cycling), nearby search, and querying orders/driver location/cancelling orders. Keywords: "打车", "叫车", "去[地点]", "回家", "上班", "下班", "查价格", "多少钱", "路线", "怎么走", "步行到", "附近", "周边", "司机", "订单", "查询订单". Note: even if the user does not explicitly say "打车", it should trigger whenever the request involves going from point A to point B, commuting, or choosing a mode of transport. Do not trigger for: building ride-hailing apps, using other navigation apps, ordering food delivery, checking bus timetables, or stock/financial report queries.
Synthesize a fragmented academic conversation into a cohesive, structured markdown report. Use this skill whenever the user has asked many disconnected questions about a topic in one session and now wants a unified write-up that captures what was discussed. Trigger phrases: write a report on our conversation, summarize this discussion into a document, turn this into a readable report, capture everything we talked about, make a note of this whole conversation, write up what we covered. The skill scans the full conversation, groups ideas into themes, identifies gaps, asks 2–4 targeted clarifying questions to fill them, then drafts the report. It does NOT write experimental results sections (use results-writeup), Related Work prose (use related-work-writer), or paper section drafts (use method-section-writer or abstract-and-intro-writer).
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.