Skills
98,873 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Cache and refresh remote git repositories under ~/.cache/checkouts/<host>/<org>/<repo> so future references can reuse a local copy. Use this skill when the user points you to a remote git repository as reference or you encountered a remote git repo through other means.
Create, deploy, and operate Streamlit apps in PostHog via the streamlit-apps MCP tools — create an app, set its source, read and patch its code, start and stop its sandbox, poll status, list versions, delete, and share the app with humans via its PostHog URL. Use when asked to "create a streamlit app", "deploy a data app", "ship a dashboard app", "restart/stop my app", "why is my app not running", or "give me a link to the app".
NEAR Protocol smart contract development in Rust. Use when writing, reviewing, or deploying NEAR smart contracts. Covers contract structure, state management, cross-contract calls, testing, security, and optimization patterns. Based on near-sdk v5.x with modern macro syntax.
Builds accessible, customizable component libraries using shadcn/ui with Radix UI or Base UI, Tailwind CSS 4, and React 19. Covers component ownership, oklch CSS theming, type-safe forms with Field and Zod, CLI workflows, and registry patterns. Use when adding shadcn/ui components, configuring themes, building forms with Zod, creating custom registries, or composing accessible component variants. Use for shadcn CLI, dark mode, component variants, form validation.
Run GitHub's Spec-Driven Development (SDD) workflow via the `specify` CLI — install spec-kit, initialize a project for one of 30+ AI coding agents (Claude Code, Copilot, Gemini, Cursor, Codex, Qwen, opencode, Kiro, etc.), and drive the constitution → specify → plan → tasks → implement command pipeline. Use when the user wants to bootstrap a Spec-Driven Development project, install `specify-cli`, generate executable specs before code, or invoke the `/speckit.*` slash commands (`/speckit.constitution`, `/speckit.specify`, `/speckit.plan`, `/speckit.tasks`, `/speckit.implement`, `/speckit.clarify`, `/speckit.analyze`, `/speckit.checklist`). Triggers on: spec-kit, speckit, specify, specify init, spec-driven, spec driven development, SDD, /speckit, executable spec.
Resolve Git merge or rebase conflicts based on each side’s intent, preserving behavior and validating integration. Use when an operation with unmerged files already exists; do not abort, rewrite remote history, or choose one entire side without authorization.
Use when implementing gesture composition (simultaneous, sequenced, exclusive), adaptive layouts (ViewThatFits, AnyLayout, size classes), or choosing architecture patterns (MVVM vs TCA vs vanilla, State-as-Bridge). Covers advanced SwiftUI patterns beyond basic views.
Implement Blazor Inline AI Assist component for seamless AI-powered text editing and content generation. Covers setup in WebAssembly and Web App projects, event handling, AI provider integration (Azure OpenAI, OpenAI, Ollama, Gemini), customization, accessibility, and enterprise deployment patterns.
Implement Syncfusion WPF SfAccordion for collapsible and expandable panel layouts. Use this when working with accordion controls, expandable panels, or collapsible section navigation in WPF. Covers populating items declaratively or via data binding, selection modes (One/OneOrMore/ZeroOrOne/ZeroOrMore), programmatic selection, appearance customization (AccentBrush, HeaderTemplate, ContentTemplate), and theming with SfSkinManager.
Implement Syncfusion WPF SfAIAssistView for AI chat and conversational assistant interfaces. Use this when building AI assistant UIs, message threads with AI responses, or integrating OpenAI/SemanticKernel in WPF. Covers typing indicators, suggestions, input/response toolbars, stop-responding features, conversation history, input placeholder text, empty view templates, and PromptRequest events using Syncfusion.SfChat.Wpf.
Implements the Syncfusion WPF ColorPickerPalette control for color selection from themed and standard color palettes. Use this when adding color pickers with predefined palettes, customizing color options, or handling color selection events in WPF applications. Covers setup, color management, appearance customization, and interaction patterns.
Implement Syncfusion WPF ColorPicker for color and gradient selection. Use this skill whenever users need to add color picking functionality, select solid colors, create linear/radial gradients, customize palettes, apply themes, or handle color-changed events in WPF applications. Covers XAML and C# implementations.
Implement Syncfusion WPF Ribbon component for modern desktop applications. Use this skill when creating ribbon interfaces in WPF with tabs, groups, buttons, menus, and galleries. Covers advanced features like application menus, backstage views, state persistence, multi-document ribbon merge, keyboard accessibility, touch support, and ribbon customization.
Create and configure WPF TileView controls for organizing and displaying content in tile layouts. Use this skill whenever users need to implement tile-based layouts, arrange tiles in matrix positions, add drag-drop functionality to tiles, maximize/minimize tile items, customize tile headers and appearance, bind data to tile views, or create responsive dashboard-like layouts. Essential for building WPF applications with interactive tiled interfaces.
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.
Use when a Three.js scene renders incorrectly: black screen, invisible objects, wrong colors, z-fighting, or broken shadows. Prevents the common mistake of wrong color space, missing material.side, or forgetting updateProjectionMatrix. Covers all common rendering errors with diagnosis steps and fix patterns. Keywords: black screen, invisible, wrong color, z-fighting, shadow artifact, rendering error, debug, nothing visible, dark, broken, nothing shows, model not appearing, screen is blank.
Always invoke for `.xaml`/`.cs` workflow files. UiPath RPA (Modern or Legacy): create, edit, validate, build, pack, run, debug coded `.cs` and `.xaml` workflows; UI automation with Object Repository selectors; live desktop/browser UI exploration/control; test case authoring; Integration Service connector calls. Packing stays here; solution-level `.uipx` deployment→uipath-solution; non-solution Orchestrator ops→uipath-platform; test reports→uipath-test; agents→uipath-agents
Use when the user asks to execute, implement, continue, or apply an existing implementation plan, specification, acceptance criteria, task plan, or prior planning output. Do not use for plan creation or coding requests with no concrete plan to bind.
Strict design and UX rules for React 19 + Next.js 16 (App Router) + Tailwind CSS 4. Covers navigation, interaction design, accessibility, user feedback, UX patterns, and visual design. Use when designing, building, or reviewing any user-facing web feature on this stack. Trigger when the user asks to “build a settings page”, “add a dialog”, “design this form”, “review for accessibility”, “fix dark mode”, or requests any Next.js App Router / React 19 / Tailwind UI task. Also trigger when the user says the output “looks off”, “isn't accessible”, or “doesn't follow best practices”.
Best practices for integrating with Yeepay’s open platform. Covers product selection, integration guidance, joint testing, and troubleshooting across merchant onboarding (sub-merchant onboarding by service providers/platform merchants, merchant information changes, unfreezing dormant merchants, WeChat/Alipay identity verification); payment acceptance (mini program, APP, browser H5, WeChat H5 and Official Account payments, scanned payment codes, standalone/aggregated QR codes, PC/H5 checkout, bank transfers); refunds (original-route, express, supplemental card details, combined-order); split payments (order and balance splits, beneficiary management); payouts (settlement, withdrawals); reconciliation; Hydrogen Wallet (ledger opening, bank transfer prepayments, ledger payments and refunds, freezing/unfreezing); financial services (corporate fast loans/joint loans, cross-bank credit card repayments, agreement-based payment signing and card binding/debit, batch payments); and Air Travel Easy (ticket issuance/refunds/changes, airline NDC2C/NDC2B/NDC2T/B2B, OTA distribution, CDP channels). Use this Skill when users mention “integrate Yeepay,” “connect to Yeepay payments,” “yeepay,” “YOP,” “aggregated payments,” “onboarding,” “merchant filing,” “merchant registration,” “sub-merchant onboarding,” “merchant reporting,” “identity verification,” “create a payment,” “mini program payment,” “APP payment,” “H5 payment,” “Official Account payment,” “payment code,” “QR-code collection,” “aggregated QR code,” “checkout,” “Yeepay checkout,” “hosted checkout,” “cashierUrl,” “bank transfer payment,” “corporate transfer collection,” “dynamic collection account,” “dynamic remittance note,” “refund,” “split payment,” “beneficiary,” “settlement,” “withdrawal,” “reconciliation statement,” “Hydrogen Wallet,” “ledger,” “prepayment,” “incoming payment notification,” “ledger payment,” “loan,” “corporate fast loan,” “joint loan,” “credit card repayment,” “cross-bank repayment,” “agreement-based payment,” “debit,” “signing and card binding,” “one-click card binding,” “existing agreement,” “card binding id,” “batch payment,” “recurring debit,” “auto-renewal,” “premium debit,” “Air Travel Easy,” “TSP,” “air ticket API,” “NDC2C,” “NDC2B,” “NDC2T,” “airline B2B,” “ticket issuance,” “ticket refund,” “ticket change,” “availability and fare check,” “electronic itinerary,” “ticket invoicing,” or “policy pool”; mention airline ticket integrations for China Southern, XiamenAir, Air China, China Eastern, Shenzhen Airlines, Shandong Airlines, Kunming Airlines, Hong Kong Airlines, and others; or ask about signature verification failures, missing callbacks, order queries, error-code troubleshooting, sandbox testing, or launch checks. Also use this Skill for troubleshooting that requires real-time platform data, including “troubleshooting assistant,” “integration diagnosis,” “real-time diagnosis,” “diagnostic credentials,” “check why the notification wasn’t received,” or “help me check this transaction.”
Load this skill whenever the project contains dynamic content updates, status messages, alerts, notifications, loading indicators, or any use of aria-live, role="status", role="alert", or role="log". Under no circumstances add or modify live-region markup without applying these rules. Prioritize correct politeness levels and avoid redundant announcements. Never use a fixed-delay clear-and-reinsert workaround — no standard guarantees it works.
Migrate an app's charts from Recharts or TanStack Charts to Bklit UI. Detects Recharts usage — direct `recharts` imports or shadcn/ui's `components/ui/chart.tsx` wrapper (ChartContainer, ChartConfig, ChartTooltipContent, ChartLegendContent) — and `@tanstack/charts` definitions (defineChart with lineY / areaY / barY marks), inventories every chart, classifies each as clean / needs workaround / keep, installs the matching `@bklit/*` shadcn registry items, and rewrites each chart with the equivalent bklit components while preserving data, colours, and labels. Tiny axis-less charts (Recharts "Tiny" line/area/bar charts, TanStack KPI sparklines) become LineSparkline / AreaSparkline / BarSparkline. Use when the user asks to replace, migrate, convert, or port Recharts, shadcn charts, or TanStack Charts to bklit, to swap sparklines or tiny charts, to remove the recharts or @tanstack/charts dependency, or asks what it would take to switch chart libraries.
Plans structure for a component library with props/slots and right-sized component granularity. Run before building or adding Canvas components (new component folders, component.yml, implementation), or for plan-only / breakdown-only work, whenever UI must map to a coherent tree. Mandatory for every new Figma frame or greenfield screen—repository drafts do not replace phases A–G
Configure a DataHub instance to load and display a Micro Frontend (MFE) app. Use when the user wants to register an MFE with DataHub, add an MFE to the nav sidebar, set up MFE config for local dev or production/k8s, or troubleshoot MFE loading issues.
Remove AI slop from the code a branch changed, before a commit and without changing behavior: narrating comments, guards on states the types or the boundary already rule out, dead compatibility paths, unrelated edits, one-caller wrappers and speculative abstractions, casts that silence the type checker, and nesting an early return flattens. Use for /deslop, deslop it, clean the diff, strip the slop, or before any commit. Code only. The unslop skill cleans prose and the no-comments skill reviews comments.
Docker Compose Watch mode for hot reload during local development (2025 GA). PROACTIVELY activate for: (1) docker compose watch setup, (2) watch action types (sync, rebuild, sync+restart, sync+exec), (3) configuring path filters and ignore patterns, (4) hot-reload for Node/Python/Go/Rust apps in Compose, (5) sync-only vs rebuild trade-offs, (6) using watch with profiles, (7) debugging watch mode (verbose logs), (8) integrating watch with bind mounts, (9) Compose watch vs nodemon/air/cargo-watch. Provides: watch action reference, per-language hot-reload examples, path filter patterns, and troubleshooting steps
Keep gbrain current. When a `gbrain` invocation prints an `UPGRADE_AVAILABLE <old> <new>` marker (or `gbrain self-upgrade --check-only` reports an update), apply it per the configured self_upgrade.mode: notify (prompt the operator with a 4-option question + snooze) or auto (apply silently). The action is always the hardcoded `gbrain self-upgrade` — never a command read from the marker.
Guidelines for developing and packaging applications for 懒猫AI算力舱 (AI Pod). Trigger when building an AI app for deployment to the compute pod, writing ai-pod-service's docker-compose.yml, configuring Traefik routing rules, packaging an AI browser extension, or publishing an AI app to the store.
Local-first architecture decision framework for web applications. Covers when to go local-first vs. server-based vs. hybrid, sync engine selection (ElectricSQL, Zero, PowerSync, Replicache, LiveStore, Triplit), client-side storage options (IndexedDB, OPFS, SQLite WASM, PGlite), and conflict resolution strategies (LWW, CRDTs, server-wins, field-level merge). Use when deciding whether to adopt local-first architecture, choosing a sync engine, selecting client storage, or designing conflict resolution strategies.
Optimizes Magento 2 indexing for search performance and database efficiency. Use when optimizing search performance, configuring Elasticsearch, designing database indexes, or improving reindexing strategies. Masters indexer optimization, Elasticsearch configuration, and database indexing.
Applies Qt Canvas2D (QtCanvas2D / Qt Canvas Painter, Qt 6.12+) best practices when producing or working with Canvas2D QML source code. Use whenever Canvas2D, Canvas2DContext, path2d, boxshadow2d, boxgradient2d, gridpattern2d, conicalgradient2d or transform2d is the subject: writing, reviewing, fixing, optimizing, or porting Qt Quick Canvas / HTML5 canvas drawing code to Canvas2D. Also use for GPU-accelerated imperative 2D drawing in QML — gauges, dials, charts, waveforms, oscilloscopes, clocks, freehand drawing — including choosing between Canvas2D and Shape/ShapePath when the renderer has not been decided yet. Do NOT trigger for plain Qt Quick Canvas work that must stay on the old CPU element, or for reviewing existing Shape/ShapePath code where the renderer is already settled.
Generates individual Remotion scene components from visual direction. Input is a visual/animation description for a specific scene. Output is SCENE_COMPONENT.md with complete TSX implementation. Use when implementing scenes or when asked to "create a scene component", "implement scene from spec", "build Scene1Intro"
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.