Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Premium neutral-first UI/UX design system and frontend workflow for product interfaces. Use when designing or reviewing pages, components, dashboards, settings screens, editors, forms, tables, modals, drawers, or interaction patterns that should feel calm, premium, responsive, system-driven, and production-ready. Also use when making design decisions about hierarchy, tokens, spacing, dark/light parity, component states, and cross-page consistency.
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
Color master skill. Audits every color decision across the product — balance, hierarchy, harmony, temperature, saturation, shadow construction, hover states — and corrects them using HSB color theory. Extracts the actual rendered color palette from every screen, identifies what's wrong and why, then fixes it systematically. Use when colors feel off, the UI looks flat or garish or cold, brand color is everywhere or nowhere, or the user invokes /uicolor.
Audit a whole project for UX problems, architecture weaknesses, data reliability risks, security boundaries, and performance or delivery risks using parallel specialists and a tabbed HTML report. Use when asked to audit project architecture, review system boundaries, audit the frontend, review UI consistency, check data integrity or failure recovery, audit security or authorization, review sensitive-data handling, audit performance, review build or deployment safety, find bloat, find dead code, unused dependencies, or duplicate helpers, ask what can I delete, or /ultima.
Runs an exhaustive, evidence-backed code review of current git changes by default, or of a user-named path, module, feature, or package. Forces loading every relevant available agent skill for the review surface, and requires external docs or research when libraries, APIs, security, or established practice matter. Use when the user says "ultra-review", "ultra review", "deep review", "exhaustive review", "review this diff", "review my changes", or asks for a thorough review of git changes or a pointed codebase area.
uni-app cross-platform frontend development with Vue 3 + TypeScript. Use for: (1) Creating new uni-app projects or pages, (2) Integrating UI libraries (uView Plus, uni-ui, TuniaoUI), (3) Implementing multi-theme design systems, (4) Building WeChat Mini Programs, H5, and other platforms, (5) Setting up SCSS theming and global styles, (6) Configuring Vite build system. Includes reusable templates, component patterns, and best practices applicable to any uni-app project.
(NS) Generate backend unit and integration test task markdown after implementation tasks exist. Use during SDD planning for PHPUnit/Laravel or equivalent backend test coverage per feature — not for E2E (use e2e-test-generator). Requires requirements and related backend task. Documents cross-tenant and auth P0 scenarios when applicable.
Use when reviewing UnoPim code changes or a pull request for standards compliance, or when asked about conventions, best practices, violations or code quality in an UnoPim codebase. Trigger phrases include “review,” “code review,” “PR review,” “standards,” “conventions,” “violations,” “code quality.”
Use when configuring a UnoPim import or export, building an Exporter, Importer or Validator class, debugging a queued data-transfer job, or wiring exporters.php, quick_exporters.php or importers.php. Trigger phrases include “import,” “export,” “data transfer,” “exporter,” “importer,” “CSV,” “queued job,” “batch.”
Use when building or changing an UnoPim admin listing page — a DataGrid class with columns, search, filters, sorting, row actions or mass actions, or the Blade view that renders it. Trigger phrases include “datagrid,” “admin listing,” “add a column,” “mass action,” “prepareQueryBuilder,” “listing page.”
Use when creating a new UnoPim package, module or third-party connector — service providers, models, repositories, controllers, routes, ACL, menus, migrations, credential storage, cURL clients or attribute mapping. Trigger phrases include “new module,” “new package,” “connector,” “scaffold module,” “service provider,” “credentials,” “attribute mapping,” “WooCommerce,” “Shopify,” “Shopware.”
Builds a client × services cross-sell map for a B2B service company: which active client uses which services, where the gaps are, and which gaps are realistic expansion opportunities — with a prioritized action list. Use when the user says: "карта апсейлів", "upsell map", "cross-sell map", "кому що допродати", "де ростити акаунти", "expansion opportunities", or pastes a client list + service list and asks where the growth is. NOT for account health scoring (use client-health-check) and NOT for new-business offers (use offer tools).
A live, growing registry of agent skills published by Anthropic, OpenAI, Vercel, Microsoft, Cloudflare, Stripe, HashiCorp, Supabase, and many others. Search it before starting any non-trivial task, fetch the top result, follow it instead of going freehand. After using a skill, report back so the registry ranks it correctly for the next agent. If you build something reusable, ask the user, then upload it.
Use when surveying the PUBLISHED user-research evidence for a product's design questions BEFORE an interface is designed — deriving a research vocabulary map, executing ONE search angle across scholarly indexes, preprint servers, practitioner-research corpora and standards-body findings, deep-reading ONE source into the findings it contains, or synthesising the evidence register and report. One source yields N finding-records, because how many findings a paper holds is only knowable after the read. Certainty uses GRADE's four-level vocabulary assigned BY RULE and re-derived by the validator; transferability stays a separate field, because excellent evidence from another population is strong evidence and weak guidance at once. Keywords: user research prior art, HCI literature, usability evidence, published findings, evidence synthesis.
Comprehensive UI/UX design principles covering affordances, visual hierarchy, grids, typography, color theory, dark mode, shadows, icons, buttons, feedback states, micro-interactions, and overlays. Use when designing UI components, reviewing design quality, building new screens, giving design feedback, writing design specs for AI coding assistants, or teaching product/engineering teams correct design vocabulary.
Expert UX design thinking, user psychology, and experience strategy. Activates when building, reviewing, or discussing any user-facing interface -- websites, apps, dashboards, forms, onboarding, checkout, sign-up, settings, landing pages, modals, navigation. Triggers on: user flows, wireframes, prototypes, usability, information architecture, content strategy, error handling, accessibility, interaction design, user testing, conversion. Also activates on: 'how should this flow', 'user experience', 'make it easier', 'onboarding', 'conversion', 'drop-off', 'friction', 'confusing', 'intuitive', 'usability', 'user journey', 'review screen', 'review interface', 'UX audit'. Applies whenever a human uses an interface, even without saying 'UX'. Hands off to ui-designer for visual styling and craft. Hands off to ux-research for evidence gathering and discovery. Hands off to design-system for component infrastructure. Do NOT activate for: purely visual styling, backend logic, database schemas, API design without UI, DevOps, casual mention of UX vocabulary in non-UX contexts (e.g., 'make this API easier to use' is not UX), tasks where the actual problem is data, performance, infrastructure, or content even if a user-facing surface is involved. Require explicit experience/flow/usability intent -- do not activate by reflex on trigger words alone
Reviews UX, accessibility, and microcopy for web and React Native (Expo) applications. Analyzes UI code against established UX principles, WCAG 2.2 accessibility standards, platform guidelines (Apple HIG, Material Design 3), and UX writing best practices. Triggers on: "ux review", "review ux", "check accessibility", "improve the UI", "ux audit", "review this component", "is this accessible", "check usability", "ux feedback", "review the design", "improve usability", "check contrast", "review navigation", "ux writing", "improve copy", "review microcopy", "make this more intuitive", "ux best practices", "/ux".
Deploy 8 radically different visual direction demos for a website or webapp project. Creates self-contained Next.js pages under /demo/ with distinct identities (typography, color palette, layout, animation, accessibility) so the user can compare and choose. After selection, generates production-ready theme tokens, Tailwind config, CSS variables, and base components matching the chosen direction. Use when: starting a new web project, redesigning a site, choosing visual direction, the user says "style selector", "choose styles", "visual alternatives", "pick a design direction", or wants to compare different aesthetic approaches before committing to one. Works with Next.js + Tailwind CSS projects (landing pages, web apps, SaaS, dashboards).
Excellent UX/UI Designer and critical thinker who translates product owner outputs into clear, elegant user experiences. Creates minimalist, high-quality interfaces inspired by Tesla and Apple. Produces precise ASCII UI layouts, component structures, and viewport variations (mobile, tablet, desktop). Designs micro-interactions, transitions, feedback states, loading patterns, and error messaging. Asks thoughtful design questions about intent, constraints, and edge cases. Welcomes feedback and iterates quickly. Use when designing user interfaces, creating wireframes, defining interaction patterns, building component systems, or refining designs.
Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
Apply James's AI trust principle to both outputs and autonomous actions. Use when generating or executing consequential changes, delegating tasks or assessing reliability; require independent verification, bounded permissions/time/data/money and recoverability proportionate to impact.
Use when verifying information (fact, number, quote, event, statement) against authoritative primary sources, or cross-checking a number via one-level metric decomposition (Z = P × Q). Triggers: "verify X", "is this true", "find the original source", "where is this number from", "two sources disagree", "is it true X never did Y". Covers five scenarios: (1) basic truthfulness check, (2) completeness / out-of-context quoting, (3) one-level reasoning verification, (4) negative-statement handling, (5) multi-source conflict side-by-side output. Dig into whitelisted primary sources only (user-supplied files, official websites & databases, authoritative industry sources); cited reports / charts / datasets must be downloaded and read locally to count as verified — if download is blocked, hand the link to the user. If nothing can be found, plainly state "cannot verify" rather than guessing, patching, or citing secondary paraphrases. Always reply in the user's question language.
VHS terminal recording best practices from Charmbracelet (formerly charmbracelet-vhs). This skill should be used when writing, reviewing, or editing VHS tape files to create professional terminal GIFs and videos. Triggers on tasks involving .tape files, VHS configuration, terminal recording, demo creation, or CLI documentation
Vibe Deck — vibe-code professional slide presentations — describe what you want, AI builds it. Scaffolds a React + ECharts project, creates slides with charts, animations, theming, and PDF export. Use PROACTIVELY when the user mentions slides, deck, presentation, PPT, PPTX, slideshow, keynote, pitch deck, quarterly review, board meeting, investor update, sales deck, training deck, onboarding slides, report presentation, add a slide, build a deck, create slides, make a roadmap slide, put this data into a presentation, turn this Excel into slides, visualize this data as a deck. Also trigger when the user wants to modify, reorder, or delete slides in an existing slide-kit project. Also trigger when the user wants to share, export, or package the deck as a single HTML file for email or offline viewing. Chinese triggers: 做PPT, 做个deck, 写pptx, 创建演示, 制作幻灯片, 做幻灯片, 加一页, 新增slide, 做演示文稿, 工作汇报, 述职报告, 季度回顾, 方案展示, 写个汇报, 改一下这页, 调整幻灯片顺序, 删掉这页, 把数据做成图表展示, 帮我做个路线图, 导出单个HTML, 分享给别人看.
Orchestrates end-to-end video generation through sequential workflow steps (audio, direction, assets, design, coding). Activates when user requests video creation from a script, wants to resume video generation, mentions "create video", "generate video", or "video workflow", requests running a specific step (audio, direction, assets, design, coding), asks to "create audio", "generate direction", "create assets", "generate design", or "code video components", or wants to resume a video. Manages workflow state tracking and parallel scene generation.
Records and assembles documentation videos for web apps using Playwright browser automation, TTS narration, and FFmpeg. Generates a React docs site with embedded videos. Use when asked to document an app, record user flows, create tutorial videos, walkthroughs, onboarding videos, step-by-step guides, how-to videos, "make docs", "document my app", "show how to use", or "create a video guide".
Advanced video analysis and selection skill with AI-powered automatic scoring. Integrates Walter Murch's rules and dynamic weighting for professional-grade curation. Supports Bilibili, YouTube, Douyin (抖音), and Xiaohongshu (小红书). Use this skill whenever the user wants to analyze videos, score or rate scenes, extract best shots/highlights, evaluate video quality, curate clips, do competitor video analysis, or mentions terms like "视频分析", "镜头筛选", "场景评分", "视频拆解", "精选片段", "视频质量", "镜头打分", "素材挑选" — even if they don't explicitly ask for "expert analysis".
Create or adopt a repository as a vignette catalog for one dataset. Use when the user asks to start, scaffold, or convert a project into a catalog with catalog.toml and reusable marimo notebooks. Produces the smallest runnable structure and orientation notebook. Do not use for an existing catalog; use vignette-catalog-compose-notebook there.
Build and debug WidgetKit widgets for Apple Vision Pro (visionOS), including mounting styles (elevated/recessed), textures (glass/paper), proximity-aware layouts via LevelOfDetail, interactive widgets with AppIntents, widget rendering modes (accented/fullColor), and timeline update troubleshooting. (visionOS widgets are pinned spatial objects, not watch complications.)
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.