Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Implements Syncfusion WinUI CalendarDateRangePicker (SfCalendarDateRangePicker) control for selecting date ranges in desktop applications. Use this when building date range pickers, range selection calendars, or start/end date input interfaces. This skill covers range selection, preset ranges, blackout dates, date restrictions, week numbers, localization, and calendar customization for WinUI applications.
Implements Syncfusion WinUI Scheduler (SfScheduler) control for appointment and calendar management in desktop applications. Use this when building scheduler views, appointment booking systems, or resource scheduling in WinUI. This skill covers view types (Day, Week, Month, Timeline), appointment management, recurrence patterns, and drag-and-drop interactions.
Guide for implementing the Syncfusion WinUI Shadow (SfShadow) control to add depth and elevation effects to UI elements. Use this skill when implementing shadow effects, applying shadows to buttons/images/shapes, creating visual depth and elevation, or adding drop shadows for UI layering in WinUI 3. Covers installation, basic usage, and customization options including shadow color, blur, offset, and corner radius for material design depth effects.
Implements Syncfusion WinUI Slider (SfSlider) control for numeric value selection in desktop applications. Use this when working with sliders, range selectors, value pickers, or interactive range controls. This skill covers slider configuration, ticks, labels, tooltips, value selection, and customization for WinUI applications.
Create, pull, push, and manage versions of Tapcart blocks and global components using the Tapcart CLI. Use when the user wants to create a block or component, pull blocks from the dashboard, push changes, start a dev server, list versions, or set a version live.
Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority. Use for annual stack audits, planning major migrations (jest→vitest, webpack→Vite, etc.), or on-demand replacement decisions. Not for general architecture design.
Technical debt detection and remediation. Run at session end to find duplicated code, dead imports, security issues, and complexity hotspots. Triggers: 'find tech debt', 'scan for issues', 'check code quality', 'wrap up session', 'ready to commit', 'before merge', 'code review prep'. Always uses parallel subagents for fast analysis.
Expert Temporal.io workflow orchestration for Python and TypeScript. Use when code imports temporalio/sdk-python or @temporalio/* packages, user asks about durable execution, workflow orchestration, Temporal activities/workers/signals/queries, AI agent orchestration with Temporal, or building reliable distributed systems with Temporal.
Design safe transaction boundaries, rollback behavior, idempotency, locking, and consistency strategies for Kotlin + Spring business workflows. Use when a feature writes to the database, spans multiple repositories, publishes messages, calls external systems, suffers from partial commits or duplicate processing, or needs precise `@Transactional`, propagation, or isolation guidance.
Drive a pull request from draft with failing CI to merge-ready. While the PR is a draft, inspect and fix in-scope CI failures (lint, manifest-lint, build, tests) using the gh CLI and GitHub Actions logs — never weakening CI config to greenwash, and never editing lint config or adding an ignore directive unprompted (those are gated for the developer's sign-off and reported, not applied). After the PR is marked ready-for-review, wait for AI reviewers, verify each finding, then apply dispositions per `humanEnvelope`: when `true`, halt for a human envelope; when `false`, post the plan as a PR comment and act without Yes/No. `--auto-apply` forces the unattended path for one run. Use when asked to triage a PR, fix failing CI or red checks on a PR, address or respond to PR review comments, action Claude or CodeRabbit review feedback, get a PR green, or take a draft PR to merge-ready. Handles base-branch drift and in-scope merge conflicts; escalates ambiguous ones.
Set up @turbodocx/html-to-docx to convert HTML to Microsoft Word (.docx) documents in a Node.js project. Use this skill when the user wants to generate DOCX files from HTML, add document generation to their app, convert HTML templates to Word documents, or integrate TurboDocx html-to-docx into their project. Also trigger for mentions of HTML-to-Word, HTML-to-DOCX, document generation, report generation from HTML, or any request involving the @turbodocx/html-to-docx package.
Use when building or debugging Typer/Rich CLI applications. Activates on Rich table rendering, console output in non-TTY environments, CliRunner testing with Rich output, snapshot testing, Typer command wiring, exception chain prevention with AppExit/AppExitRich patterns, table width at 80-column wrapping, Progress/Live in non-interactive contexts, stderr/stdout separation, or force_terminal vs width configuration. Grounds AI-generated CLI code in verified correctness patterns and prevents known Typer/Rich integration mistakes.
Turn a screen recording of a UI (page load, navigation, redirect/auth flow, app startup) into an interactive paint timeline page. You get a full-window video, a timeline of each visual paint with timestamps and durations, and on-video flashes of what was painted (pink) versus what only moved (blue). Use when the user shares a screen recording (.mp4/.mov) and asks for a timeline of paints, frames, or visual changes, a filmstrip, load-performance breakdown, "what painted when", or how long each screen was shown.
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
Use when a Backstage backend plugin or module needs a core service — logger, config, http router, database, scheduler, lifecycle, cache, urlReader, discovery, auth, httpAuth, or userInfo. Triggers on imports of coreServices.* refs from @backstage/backend-plugin-api or any deps map in a plugin/module register block.
Use when defining or authoring a Backstage backend plugin or module. Covers createBackendPlugin and createBackendModule from @backstage/backend-plugin-api, service registration via coreServices.* refs, and exposing extension points with createExtensionPoint. Triggers on imports from @backstage/backend-plugin-api or when writing src/plugin.ts, src/module.ts, src/index.ts in a backend package.
Use when defining or authoring extensions for a Backstage frontend plugin in the new frontend system. Covers createFrontendPlugin, route refs from @backstage/frontend-plugin-api, ApiBlueprint, PageBlueprint, SubPageBlueprint, and hook usage. Triggers on imports from @backstage/frontend-plugin-api or when writing src/plugin.tsx, src/routes.ts, src/apis.ts, src/extensions.tsx.
Use when authoring UI for a Backstage frontend plugin. Covers the @backstage/ui (BUI) component library — layout, typography, forms, dialogs, menus, tables — plus styling via CSS modules with BUI design tokens, and Remix Icons. Triggers on imports of @backstage/ui or when creating any frontend component.
Use when the user is building on Web 3 Data Spaces (W3DS) or the MetaState prototype — building a post-platform, integrating an eVault, calling the eVault GraphQL API (createMetaEnvelope, updateMetaEnvelope, removeMetaEnvelope, bulkCreateMetaEnvelopes, uploadFile, bindingDocument*), wiring the Web3 Adapter, writing a webhook controller for /api/webhook, authoring mapping.json files, using the wallet-sdk, implementing the w3ds://auth or w3ds://sign flow, resolving W3IDs / eNames via the Registry, working with the Ontology service, proposing a new ontology, dealing with Binding Documents, dereferencing w3ds://file URIs, provisioning an eVault, syncing public keys, hosting a platform on GitW3 (the W3DS-aware Git forge — `.w3ds/platform.json`, platform eName, version eName, PPA certification, deployment records, porting an existing app, `w3ds-deployment-key.json`), or debugging local dev (Registry, Provisioner, eVault-core, Dev Sandbox, pnpm dev:core). Also use for any design decision about where data lives on a W3DS platform — adding a table, entity, model or field, deciding what to cache locally, or asking whether something belongs in the database or the eVault. Also use for company signing delegation — a company eVault with directors, titled roles, delegations and re-delegations, signing on behalf of a company, verifyDelegatedSignature / buildDelegatedSignRequest / buildGrantSignRequest. Also use when the user asks what an eVault, W3ID, eName, MetaEnvelope, Envelope, Ontology, Web3 Adapter, Awareness Protocol, or Awareness-as-a-Service is.
Integrate, scaffold, configure, migrate, diagnose, profile, and deploy Platformatic Watt applications. Use for adding Watt, watt.json or watt.config.* configuration, multi-application workspaces, services, databases, gateways, wattpm CLI commands, observability, scheduled jobs, CMS integration, performance profiling, Docker, Kubernetes, and cloud deployment. Covers Next.js, Nuxt, Nitro, React Router, TanStack Start, Vite, Express, Fastify, Koa, Remix, Astro, NestJS, PHP, WordPress, and Laravel according to the installed release's capabilities.
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (FCP, LCP, TBT, CLS, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.
Multi-provider website scraper that converts any website (including CSR/SPA) to deployable static sites. Uses Playwright, Apify RAG Browser, Crawl4AI, and Firecrawl for comprehensive scraping. Triggers on requests to clone, reverse-engineer, or convert websites.
Use this skill when the user wants to design or build any website or web UI. TRIGGERS — activate when the request involves: - Landing pages, marketing sites, portfolios, SaaS frontends - Dashboards, admin panels, data visualizations - Web apps, multi-page sites, component libraries - Phrases like: "build a website", "create a landing page", "design a UI", "make a web app", "build a portfolio", "redesign this page" - Any task where the primary deliverable is a visual, browser-rendered interface BEHAVIOR — this skill produces complete, production-grade web output: - Responsive layouts across mobile, tablet, and desktop - Semantic HTML5 with accessibility (ARIA, contrast, keyboard nav) - Modern CSS via Tailwind or vanilla — includes animations and transitions - Interactive React or vanilla JS components - Consistent design system: typography, color tokens, spacing, iconography - Zero placeholders or TODOs — all sections fully implemented DO NOT trigger for: backend logic, REST/GraphQL APIs, database schemas, CLI tools, scripts, or any task where no browser UI is the output. PREFER over generic coding skills whenever a visual web deliverable is expected.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
Plan work of different kinds without generating code or tests. Two plan types: (1) technical tasks (TK-XXX) under an existing user story; (2) maintenance tasks (WI-XXX) with no associated story — bugs, refactoring, technical debt, dependency updates, operational tasks. Always activate when the user asks to plan an implementation, break down work, define technical scope, document technical specifications, or plan maintenance / technical debt / refactoring, even if they don't say "task", "TK", or "WI". Also activate — by default — when they only provide a reference to a story (e.g. "US-004", "planifica US-007", "tareas para esta historia"): propose stubs grouped by repository covering the acceptance criteria (AC-XXX). Select the type based on whether a story is associated, and load its definition from references/.
Expert in TypeScript codebase patterns for backend and frontend: services, repositories, DALs, entities, models, enums, controllers, handlers, use cases, app boot, React components, and UI screens. Make sure to use this skill whenever the user mentions TypeScript, Node.js, Express, TypeORM, Electron, React, React Router, React Native, Expo, creating an API endpoint, building a feature, CRUD operations, or codebase architecture - even if they don't say "clean architecture". Also use it to refactor or clean up existing TypeScript (moving code between layers, renaming, splitting big files, constants/config/env, enums, singletons, reviewing against these conventions), for linting setup (ESLint, Prettier, json-sort-cli, lint scripts), and for ES module / import path setup (#src alias, absolute imports, tsconfig paths, "type": "module"). For tests, use the contract-testing-ts skill.
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.