Skills
98,873 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Use this skill when the user asks to explore a repository, get familiar with a project, “repo explorer”, “tell me about this repo”, “repo-explorer”, “what does this repository do”, or wants an overview of a Gitee repository. Requires Gitee MCP Server to be configured.
Implement the Syncfusion React DateRangePicker component for date range selection, booking systems, and reporting interfaces. Use this when working with date range pickers for appointment booking, event scheduling, date filtering, or vacation requests. Covers date range validation, preset ranges, format customization, event handling, and form integration.
Implement Syncfusion WPF CardView for card-based data display with grouping, sorting, filtering, and editing. Use this when implementing card panels, binding data with ItemsSource, or customizing card layouts in WPF. Covers CardViewItem population, GroupCards, CanSort, CanEdit, EditItemTemplate, HeaderTemplate, ItemTemplate, and SfSkinManager theming.
Comprehensive guide for implementing Syncfusion WPF Tabbed Window control that combines SfChromelessWindow with SfTabControl for document-based applications. Use this skill when implementing chromeless tabbed windows, browser-style tabs, document management windows, or Visual Studio-style tabs in WPF. Covers tear-off tabs, floating tab windows, tab merging between windows, drag-drop tab reordering, and MVVM tab binding scenarios.
Create and customize WPF time picker controls using Syncfusion's SfTimePicker component. Use this when implementing time selection UI, time input fields, or time value formatting. This skill covers SfTimePicker setup, time selector customization, value binding, and appearance styling in WPF applications.
Giải thích MỘT thứ (một file, hàm, tính năng, cơ chế, khái niệm, lỗi, hay hệ thống) theo cấu trúc cố định BẢY BƯỚC — Tên gọi → Nguồn gốc → Lý do tồn tại → Cơ chế hoạt động (+ sơ đồ hệ thống & code) → Trade-off → Giới hạn → Vị trí trong toàn bộ hệ thống — và CĂN THEO NGƯỜI NGHE (engineer, sếp/manager, designer, PM, sinh viên, bố mẹ, trẻ 5 tuổi…): cùng bảy bước, đổi độ sâu, từ vựng, phép so sánh, giọng. CHỨNG bước "Cơ chế hoạt động" bằng RUNTIME thật — chạy code với đầu vào cụ thể, thêm instrument/breakpoint (pdb/debugpy · node --inspect · print/log), quan sát state THẬT — thay vì đọc-rồi-đoán, rồi dọn sạch instrument. Gọi khi user nói "teach me", "giải thích", "dạy tôi", "cái này chạy thế nào", "sơ đồ hoá", "ELI5", "explain like I'm…", "giải thích như cho trẻ 5 tuổi", "nói dễ hiểu", "giải thích cho sếp/manager/designer/bố mẹ/vợ tôi…", "làm sao nói với sếp cái này", "/teach-me". KHÁC /onboard-codebase và /join-project (cả dự án → wiki): teach-me phạm vi MỘT thứ, sâu, có sơ đồ, chứng bằng chạy thật, không ghi wiki.
Use this skill when the user asks to “create a 3D scene,” “add a mesh,” “implement OrbitControls,” “load a GLTF model,” “add bloom post-processing,” “write a custom shader,” “create particle effects,” “optimize Three.js performance,” “use WebGPU,” “add shadows,” or “animate a model,” or mentions Three.js, threejs, WebGL, WebGPU, GLTF, raycaster, shader material, PBR material, or post-processing effects. IMPORTANT: This skill is for VANILLA Three.js (imperative JavaScript). For React Three Fiber (@react-three/fiber, R3F, drei), check the `r3f-best-practices` skill, although the three-js skill also helps when working with R3F since R3F is a React renderer for Three.js. Provides a complete Three.js reference for 3D web graphics, including scene setup, geometry, materials, textures, lighting, cameras, loaders, animation, controls, interaction, shaders, post-processing, performance optimization, TSL/node materials, WebGPU, physics, and VR/XR integration.
ALWAYS use when writing, debugging, or reviewing code that imports “@vue/test-utils” or mentions vue test-utils, VTU, mount, shallowMount, findComponent, wrapper queries, or migrating from Vue Test Utils v1. Provides the current API surface, mounting options, wrapper methods, and testing recipes for @vue/test-utils 2.5.1 on Vue 3
Renderless components and directives from @vueuse/components 15.x (VueUse). Use when writing, converting, or debugging code that imports @vueuse/components, using Use*/On* components or v* directives in Vue 3 templates, or mapping VueUse composables to component or directive usage. Provides props, slot data shapes, emits, directive binding syntax, and version limits
Generate a copy-paste-ready GPT prompt that produces a polished architecture or workflow diagram image, and optionally render the image directly via Codex CLI image generation. Trigger when the user wants to create, make, generate, draw, or visualize a diagram, architecture image, system workflow picture, or flowchart, or pastes a Mermaid diagram asking for a polished image.
Expert knowledge for Azure Quantum development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when submitting Q#/OpenQASM jobs, configuring workspaces, managing IonQ/Quantinuum/Rigetti usage, or running hybrid workflows, and other Azure Quantum related development tasks. Not for Azure HDInsight (use azure-hdinsight), Azure Databricks (use azure-databricks), Azure Synapse Analytics (use azure-synapse-analytics), Azure Machine Learning (use azure-machine-learning).
Not tax or accounting advice. Integrate Cardcom payment processing and Israeli invoice generation into applications, covering Low Profile payments, tokenization, recurring billing, and automatic tax invoice/receipt creation per Israeli law. Use when user asks to accept payments via Cardcom, generate Israeli invoices with payments, set up "slikat ashrai" with hashbonit, handle recurring billing (hora'ot keva), or mentions "Cardcom", "CardCom API", "Low Profile", Israeli payment with invoicing, or needs combined payment plus document generation. Targets the REST API V11. Do NOT use for Tranzila integration (use tranzila-payment-gateway), general accounting, or non-payment queries.
Save the builder's work to git at every point the app works, and get them back to a working version when something breaks. Use the moment a feature works end to end, before any risky change, before a long build step, at the end of a session, and whenever they say something broke, "it worked before", "undo that", or "start over". Also use when they have been building a while with nothing committed.
Compose a premium, animated landing page section by section in Next.js + Tailwind + Motion (Framer Motion) — built on a real design system, with editorial copy and motion that feels human-crafted, not template-generated. Use when building or rebuilding a landing page, marketing site, or hero/feature/pricing/CTA sections that need to look production-ready and bespoke from day one
Based on the results of cleanddd-requirements-analysis, outputs CleanDDD-compliant aggregates, commands, events, queries, API endpoints (Endpoints), and scheduled task models; used to quickly derive a modeling blueprint from decomposed requirements
Discover code by MEANING and DEPENDENCY structure, not by matching text — with the `codemap` CLI: hybrid vector+BM25 semantic search, symbol lookup, incoming/outgoing dependency tracing, file summaries, PageRank importance, afferent/efferent coupling, and cycle detection over an indexed repo. Only authoritative when the index exists and is fresh — a stale or empty index is called out, not trusted. Use for architecture-aware code discovery instead of plain text search.
Product and technical document creation through guided discovery, including project PRDs, feature PRDs, feature design docs, audit reports, positioning docs, Design Docs, and ADRs, plus archiving of feature folders. Use when defining requirements, consolidating findings from external audits, feature proposals, strategy, trade-offs, or architecture decisions, or when archiving a feature. Not for running audits, UI design, implementation, or meeting notes.
Record a video walkthrough of a feature and add it to the PR description. Use when a PR needs a visual demo for reviewers, when the user asks to demo a feature, create a PR video, record a walkthrough, show what changed visually, or add a video to a pull request.
The repo front-door for a Flutter/Dart app — the cross-cutting house rules (feature-first layered MVVM, immutable state with a single write path, Riverpod 3.x for state + DI, typed Result/Failure errors, dumb widgets, injected side effects, complexity limits) plus a routing table that sends each task to its deep-dive skill and a recommended feature build order. Use at the start of any Flutter/Dart work, before writing or reviewing a feature, when deciding which layer or package code belongs in, when unsure which skill governs a task (architecture, state, widgets, persistence, testing, i18n, design), or when onboarding to the conventions.
Port TON smart contracts from FunC (.fc/.func) to modern Tolk (.tolk) with Acton: use acton func2tolk when helpful, then refactor storage/messages/opcodes into typed structs and serialization, implement Acton-style entrypoints, generate wrappers, migrate JS/TS tests to native Tolk tests, and use acton build/test/script/verify/disasm to preserve TL-B compatibility and behavior. Use when asked to convert, port, or modernize FunC contracts into idiomatic Tolk.
Godot Expert Analyst: Anara. Visionary project scoring and certification for Godot 4.7+ architecture. Use when evaluating project health, modernity, scalability, dependency graphs, or generating Visionary Certificates. Keywords: analyst, Anara, scoring, certification, architecture audit, ResourceLoader.get_dependencies, typed Dictionary, folder-by-feature, Visionary Certificate, Godot 4.7.
Expert-level GraphQL API development with schema design, resolvers, and subscriptions. Use when the user mentions API, apollo, schema, resolvers, subscriptions, or relay, or when the task involves Schema Design, Queries and Mutations, Apollo Server 4, or DataLoader for N+1 Prevention.
Enforces an on-device reminder engine where the local database is the only source of truth and the OS pending-notification set is a disposable cache reconciled through one idempotent syncNotifications() entrypoint; keeps flutter_local_notifications behind a single NotificationGateway port, all scheduling math pure and Clock-injected, recurring schedules stored as wall-clock + recurrence rule (never UTC instants) and resolved to a TZDateTime in tz.local for DST correctness, inexact-alarm default with SCHEDULE_EXACT_ALARM as an opt-in, iOS ~64-cap budgeting, isolate-safe @pragma('vm:entry-point') tap handlers, and Android boot re-arm. Use when writing or editing notification_gateway.dart, fln_notification_gateway.dart, reminder_scheduler.dart, recurrence_rule.dart, syncNotifications, zonedSchedule wiring, snooze or mark-done re-anchoring, or diagnosing missed or wrong-hour notifications.
Framer Motion (Motion) animation patterns for React — springs, staggers, layout animations, micro-interactions, scroll effects, and page transitions. Use when building or improving UI animations, adding polish, or making interfaces feel premium.
Turn a scoped learning project into a sectioned build plan with learning as the primary objective, walking through every design decision with understanding checks, and seed the living knowledge graph. Use after /start-project, when the user says "plan my project", "build the learning plan", or invokes /plan-journey.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
Scaffolds React 19 / React 19.2 code in TypeScript — components, Server Component pages, client islands, form actions with useActionState, context providers, custom hooks, reducers, or document metadata + resource hints. Generates production-grade code that follows React 19 idioms (ref-as-prop, <Context value={...}>, useActionState, inline metadata, useSyncExternalStore) and refuses deprecated React 18 patterns (forwardRef, <Context.Provider>, useFormState, react-dom/test-utils). Trigger even when the user says "create a component", "new page", "add a form", "new hook", or "scaffold X" without explicitly mentioning React 19.
Convert classic Splunk Simple XML dashboards (version 1) into Dashboard Studio (version 2). Takes classic Simple XML as input, preserves every SPL query verbatim, and returns the Studio JSON definition to the caller. Use when the user asks to convert, migrate, upgrade, modernize, port, or make a v2 / Dashboard Studio version of an existing classic Splunk dashboard, form, or Simple XML view.
Comprehensive guide for implementing the Syncfusion React DateTimePicker component. Use this when working with combined date and time inputs, datetime formatting, localization, or keyboard-accessible UIs in React applications. Covers component setup, event handling, and accessibility patterns.
Implement the Syncfusion React TimePicker component for time selection, scheduling interfaces, and appointment booking. Use this skill whenever users need time picker inputs for appointment systems, scheduling apps, time-based filtering, shift management, or time range selection. Covers installation, time format customization, min/max constraints, event handling, form integration, validation patterns, and mobile responsive behavior.
Implements the Syncfusion WPF DockingManager control for Visual Studio-like docking interfaces with MDI/TDI support, floating windows, and auto-hide panels. Use when creating docking layouts, window management systems, tabbed document interfaces, or IDE-style layouts in WPF applications. Covers dock panels, floating windows, auto-hide functionality, state persistence, and window management.
Comprehensive guide for implementing Syncfusion WPF IntegerTextBox control for integer value input with validation, formatting, and customization. Use this skill when implementing integer input controls, numeric validation for integers, or integer value entry in WPF. Covers integer data entry forms, min/max value restrictions, number formatting with culture support, integer value scrolling, range adorner progress visualization, and integer-specific input control implementation.
Use when initializing a Three.js renderer, setting up the render loop, handling window resize, configuring tone mapping, or managing color spaces. Prevents the common mistake of not capping pixel ratio, using wrong color space, or forgetting to enable shadow maps. Covers WebGLRenderer, render targets, tone mapping, color management. Keywords: WebGLRenderer, render loop, setSize, setPixelRatio, toneMapping, outputColorSpace, shadowMap, WebGLRenderTarget, dispose, resize, responsive, canvas size, window resize, fullscreen. setAnimationLoop, compileAsync.
Guides collaborative requirements discovery before implementation. Creates a task directory, seeds a PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
Turn a complete beginner's app idea into a buildable plan, then keep them oriented as they build. Use it when someone who has never coded wants to build or “vibe code” an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the full journey, a validate-only pass (“is my idea worth building”, “reality-check this idea”), and a plan-only path for someone arriving with validation done (“I already validated my idea”, “I have the research, just plan my MVP”, “skip the research”). Also use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, “commit and push,” local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. Use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask “is my code organized” or “can you clean it up.” Built for people who don't know what an API, database, or GitHub is, so use it even when they never say “plan” or “architecture.” Not for an experienced dev debugging, refactoring, or setting up CI/CD.
Set up and troubleshoot browser access from WSL2: native Linux Chrome, a Windows Chrome or Edge CDP bridge, or `agent-browser` on either path. Use for WSL browsing, sign-in, CDP connectivity, and `agent-browser` runtime setup; not for browsers outside WSL2.
Enforces a fixed main() cold-launch order — crash-log sink + FlutterError.onError + PlatformDispatcher.onError installed BEFORE any code that can throw, settings/theme read before runApp so the first frame paints correct, real infra constructed in a composition-root bootstrap() and injected via ProviderScope overrideWithValue over throwing placeholder providers, non-blocking warm-up deferred to addPostFrameCallback, exactly two error handlers with NO runZonedGuarded, ProviderException unwrapped before logging, and a WidgetsBindingObserver that flushes durable state on background/resume. Use when editing lib/main.dart, main_<flavor>.dart, bootstrap.dart or app.dart, reordering anything in main(), adding a splash/onboarding/permission gate, restoring theme before first paint, wiring a DB or service into ProviderScope, handling app-lifecycle background/resume flushes, or chasing cold-start latency, ANRs, or first-frame jank.
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.