Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
Design & UI
Cross-platform and native mobile development. Frameworks: React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose. Capabilities: mobile UI, offline-first architecture, push notifications, deep linking, biometrics, app store deployment. Actions: build, create, implement, optimize, test, deploy mobile apps. Keywords: iOS, Android, React Native, Flutter, Swift, Kotlin, mobile app, offline sync, push notification, deep link, biometric auth, App Store, Play Store, iOS HIG, Material Design, battery optimization, memory management, mobile performance. Use when: building mobile apps, implementing mobile-first UX, choosing native vs cross-platform, optimizing battery/memory/network, deploying to app stores, handling mobile-specific features.
Comprehensive Odoo i18n toolkit for extracting translatable strings, validating .po files, generating translation reports, managing Arabic/RTL layouts, and handling multilingual deployments across Odoo 14-19. <example> Context: User wants to extract translatable strings user: "Extract all translatable strings from my Odoo 17 module to a .pot file" assistant: "I will use the odoo-i18n skill to scan Python _() calls, XML translate attributes, and field strings, then generate a properly structured .pot template file." <commentary>Core trigger - translation extraction workflow.</commentary> </example> <example> Context: User wants Arabic translation user: "Generate an Arabic .po file for my Odoo module" assistant: "I will use the odoo-i18n skill to create an ar.po file with RTL-aware formatting and placeholder translations for all extractable strings." <commentary>Language-specific trigger - Arabic/RTL translation generation.</commentary> </example> <example> Context: User wants to validate a translation file user: "Validate my Arabic .po file for errors" assistant: "I will use the odoo-i18n skill to check syntax, encoding, empty translations, fuzzy entries, and RTL-specific issues." <commentary>Validate trigger - .po file validation.</commentary> </example> <example> Context: User wants to find missing translations user: "Find all strings missing Arabic translation in my module" assistant: "I will compare the .pot template against ar.po and report all untranslated or fuzzy entries." <commentary>Missing trigger - translation gap analysis.</commentary> </example> <example> Context: User wants RTL/SCSS help user: "Fix the RTL layout issues in my Odoo theme for Arabic" assistant: "I will use the odoo-i18n skill to apply CSS logical properties, [dir='rtl'] overrides, and Font Awesome icon swaps for Arabic support." <commentary>RTL trigger - Arabic layout and styling guidance.</commentary> </example> <example> Context: User needs to export/import translations via Odoo CLI user: "Export translations for my module using Odoo CLI" assistant: "I will use the odoo-i18n skill to run the Odoo export command and generate the .po file." <commentary>Export trigger - Odoo CLI translation export.</commentary> </example> <example> Context: User needs to load a language into Odoo user: "How do I activate Arabic language in my Odoo database?" assistant: "I will use the odoo-i18n skill to load the Arabic language pack and activate it via shell or CLI." <commentary>Language activation trigger.</commentary> </example> <example> Context: User has translation issues after deployment user: "My translations are not showing after I updated the module" assistant: "I will diagnose the issue: check encoding, language activation, module update, and browser cache." <commentary>Troubleshooting trigger - translation visibility issues.</commentary> </example>
Render DNA codes to Pencil .pen frames. Does ONE thing well. Input: DNA code + component type (hero, card, form, etc.) Output: .pen frame ID + screenshot Use when: design-exploration or other orchestrators need to render visual proposals using Pencil MCP backend.
Reproduce a live website from its URL as a clean, deployable Vite + React project by running the complete agent-driven Perfect Web Clone harness: capture source evidence, plan the full page, author every section, implement common interactions, build, compare, repair, and hand the measured result to the user for review. Use whenever the user asks an agent to clone, copy, reproduce, replicate, rebuild, or 复刻 a website or web page, including a minimal request containing only an action and URL. The user gives one natural language instruction; the current agent runs the internal multi-step loop through the deterministic pwc hands and eyes.
Design slide decks as HTML/CSS (custom or reveal.js): slide layouts on a fixed 16:9 canvas, presentation typography, slide charts, builds and transitions, speaker notes, and PDF export. Use for decks presented or shared from the browser; for native .pptx files use a PowerPoint-specific tool. Trigger phrases: "presentation", "slide deck", "slides", "pitch deck", "keynote", "reveal.js", "slide design", "presentation template", "speaker notes"
Improve Roblox localization and accessibility readiness. Use for UI text scaling, language-ready copy, icon clarity, color contrast, younger-player comprehension, readable HUDs, input accessibility, and reducing text-heavy onboarding.
Implements Syncfusion ASP.NET Core Grid component for feature-rich data tables and grids. Use this when working with data display, sorting, filtering, grouping, aggregates, editing, or exporting. This skill covers grid configuration, CRUD operations, virtual scrolling or infinite scrolling, hierarchy grids, state persistence, and advanced data management features for data-intensive applications.
Symfony UX TwigComponent for reusable UI building blocks -- server-rendered components with PHP classes and Twig templates. Use when creating buttons, cards, alerts, badges, navbars, or any reusable UI element with props, blocks/slots, computed properties, or anonymous (template-only) components. Code triggers: AsTwigComponent, #[AsTwigComponent], ExposeInTemplate, PreMount, PostMount, <twig:Alert />, <twig:Button>, component(), computed properties, anonymous component, HTML syntax. Also trigger when the user asks "how to create a reusable component", "how to make a component library", "how to pass props to a component", "how to use slots/blocks in a component", "how to build a design system in Symfony", "what is the HTML syntax for components", "how to create a component without a PHP class". Do NOT trigger for components that re-render dynamically on user input (use live-component), for JS behavior (use stimulus), or for page navigation (use turbo).
Vue 3 components for the Unovis data visualization framework, @unovis/vue 1.7.0. Use when writing, debugging, or updating code that imports @unovis/vue or renders Vis* components such as VisXYContainer, VisSingleContainer, VisArea, VisLine, VisStackedBar, VisCrosshair, or VisTooltip. Covers the component catalog, props, events, tooltips, colors, patterns, SSR, and the 1.7.0 API changes.
Apply Design Thinking's five stages — Empathize, Define, Ideate, Prototype, Test — to solve user-centered problems. Use this skill when the user needs to solve an ambiguous problem, redesign a user experience, facilitate an innovation workshop, or develop a new product concept from scratch — even if they say 'we don't know what to build', 'how do we innovate', or 'the users aren't happy but we're not sure why'.
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
Audit web interfaces against WCAG 2.1 AA/AAA standards, identify violations, and produce actionable remediation reports with code fixes. Use when the user requests accessibility testing or provides relevant inputs for this workflow.
Apply official brand colors and typography to professional artifacts. Use for presentations, reports, and documents to ensure corporate visual identity. Use proactively when a "client-ready" look-and-feel is requested. Examples: - user: "Brand this report" -> apply corporate colors and fonts - user: "Apply brand guidelines to these slides" -> update colors/fonts in XML - user: "Check if this document is on-brand" -> verify against color/font standards
Create and refine image files from Claude Code using a Codex subscription. Handles short creative interviews, distinct visual directions, reference-based edits, consistent asset sets, and verified transparent PNGs. Use for image generation, imagegen, GPT Image, hero art, product photos, icons, posters, 이미지 생성, 시안, 이미지 수정, or 투명 배경. Exclude image analysis and code-native SVG edits.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics
Working profiles of Saul Bass, Massimo Vignelli, Dieter Rams, Paula Scher, Josef Müller-Brockmann, David Carson, and Paul Rand: key works, principles, and how to apply each in UI work. Use when a design needs a proven approach, a named reference to follow, or a lesson from a specific master.
Core visual design principles (visual hierarchy, Gestalt grouping, composition, balance, contrast, white space, color, typography) with UI fixes, a checklist, and deep-dive references. Use when making or defending a layout, type, or color decision, or when a design feels off and you need to name why.
[devup-ui] Routing-first front door for Devup UI — a zero-runtime CSS-in-JS library whose Rust + WebAssembly preprocessor extracts every style at build time, so no styling JavaScript ships at runtime. Use to adopt/integrate Devup UI, wire the build-time plugin into Next.js/Vite/Rsbuild/Webpack/Bun, write styles with Box/css props or the styled-components-compatible styled() API, set up type-safe theming with devup.json, or migrate off styled-components/Emotion/Tailwind/Panda/vanilla-extract to zero runtime.
Turn a feature-walkthrough recording into a short, sound-off-safe clip meant to be embedded inside the product itself: a tooltip, onboarding checklist step, or help-widget video, not a standalone shareable video. Trims to the single feature the widget sits next to, adds on-screen text so the point lands muted, and reflows to a compact aspect ratio if the embedding surface needs one. Clueso produces the exported clip; embedding it into the guidance tool is the user's own step. Use when the user says "make an in-app guidance clip for this feature", "turn this walkthrough into an embeddable tooltip video", "create a short in-product help clip", or "I need a muted clip for our onboarding checklist widget".
Build MATLAB apps from requirements to working code. Asks discovery questions (or skips them when the path is known), recommends UIFigure or UIHTML architecture, identifies layout archetype (Dashboard, Explorer, Tabbed, Wizard, Canvas), produces an implementation plan, and executes the build. For UIFigure apps, optionally serializes as App Designer (.mlapp or plain-text .m + .xml). Use when a user wants to build a MATLAB app, create a GUI, make an interactive tool, build a uifigure app, build a uihtml app, build an App Designer app, build a .mlapp app, build a plain-text App Designer app, or asks which approach to use. Also use when user describes spatial layout needs: dashboard, control panel, sidebar, tabs, wizard, stepper, canvas, workspace.
Apply and review Point's official visual brand system for logos, typography, colors, artwork, photography, and comparison layouts. Use when creating, editing, or auditing Point-branded web pages, ads, decks, documents, social assets, illustrations, photo direction, design systems, CSS, or UI components where visual brand compliance matters.
Build presentation plans for PPT / slides / decks through a conversation-first workflow, then propose multiple visual directions with preview images before writing deck specs. Use when the user asks to create a PPT, presentation, deck, 答辩稿, 路演 deck, 产品介绍 PPT, 汇报 PPT, or when the user has only a topic or rough materials and needs help clarifying structure, style, and page planning before generation.
Design and produce raster images, native SVG artwork, brand-controlled visuals, and documented image edits with Recraft's API. Use for Recraft model and route selection, exact request construction, image-to-image, inpainting, outpainting, background work, vectorization, remix/exploration, palette and typography control, API migration, safety and rights review, and production QA.
Use when reviewing or judging a finished design-system document — a product's reusable visual + interaction language — deciding whether an engineer can build a consistent, accessible UI from it. Reviews an AMEND delta-scoped. A gate, not authoring. Judges against a single-sourced usability/consistency/accessibility bar: tokens DTCG-typed and referenced by intent, not raw values; components fully specced in one API vocabulary; the catalog covers the screens' components plus an archetype-sized standard set; accessibility numeric (WCAG 2.2 contrast, focus appearance, target size, keyboard); i18n addressed or scoped out; governance present above its threshold; nothing fabricated. Emits exactly `VERDICT: approve|revise` plus actionable findings, and does not false-revise a proportionally-sized system. Not for authoring it, not per-screen layout, not navigation paths, not engineering design docs.
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
Audit the visual quality of a UI against established visual-design principles — hierarchy, emphasis, contrast, spacing, alignment, grouping, consistency, and depth. Produces a severity-rated issue list with concrete fixes. Specializes in catching overdesign, clutter, and competing focal points. Use when reviewing whether a screen looks professional, or as a validation step after generating UI.
Use when the user needs an end-to-end article illustration workflow in this repository that preserves Type x Style planning, loads article-illustration preferences, recommends Alibaba Cloud image backends, and produces a Markdown article with inserted local image references.
Use when authoring a design-system document — the reusable visual + interaction language a product's UI draws on: principles, design tokens (color, typography, spacing, elevation, motion, iconography) in the W3C DTCG format, a component catalog, patterns, layout + internationalization conventions, WCAG 2.2 AA accessibility, voice, and lifecycle/governance. Guides the METHOD, not the outline: grounding tokens/components in established practice, naming tokens by intent in a primitive/semantic/component tiering, theming via alias-swap (light/dark + multi-brand), sizing the catalog to the archetype, specifying each component with anatomy + states + variants + usage + accessibility, and amending an existing system as a scoped, versioned delta. Composes with a design-system template tool + deep-research. Targets a textual markdown artifact, not rendered swatches. Not for reviewing a design system, not per-screen layout (wireframing), not a coded component library.
Greenfield design pipeline for any digital product (landing pages, websites, web apps, mobile apps): extract content, author a single-file visual identity in .agents/design/ (DESIGN.md, tokens plus rationale), define layout or screen flow, preview and refine designs, push to an external design tool when available. Use when building pages or app screens from references, images, briefs, or an existing codebase; defining layout or screen flow; previewing and tuning designs; authoring or refreshing DESIGN.md from a source. Triggers: "extract copy", "extract design", "extract from codebase", "web capture", "wireframe", "screen flow", "layout the page", "preview the design", "creative variants", "tune design", "mockup", "redesign this app", "modernize this app", "brand refresh", "validate DESIGN.md", "refresh design tokens", "push design to external tool", "generate hero banner", "create product image". Not for feature implementation spec, system architecture, or PR/code review.
End-to-end frontend design engineering workflow for improving React, Next.js, Vite, docs sites, dashboards, component systems, product websites, and studio-style apps. Use when the user asks to make UI/UX/design/frontend/website/docs/app screens more polished, curated, premium, usable, production-grade, responsive, animated, or visually consistent; when editing TSX/JSX/CSS/Tailwind/Fumadocs/shadcn/Radix/lucide interfaces; when choosing design-engineering tools or inspiration resources; or when adding loaders, icons, empty/loading/error states, motion, interaction details, and visual QA.
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool surface on its own, with no design to convert, use storybook-mcp-integration.
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
Use when creating or customizing Workspace pages in Frappe v14-v16. Covers Workspace DocType structure, shortcuts, number cards, dashboard charts, custom HTML blocks, JSON content format, shipping workspaces with custom apps, and role-based access control. Prevents common mistakes with content/child-table desync and missing fixtures. Keywords: workspace, desk, dashboard, number card, chart, shortcut, customize desk, dashboard setup, add shortcut, module page, sidebar customize, workspace builder, module, fixtures, sidebar.
Design, build, review, or refine production frontend interfaces for SaaS products, web apps, dashboards, onboarding flows, and landing pages. Use for frontend design work where Codex must turn requirements into clear, restrained, consistent, trustworthy UI; remove AI-generated visual clutter; improve hierarchy, states, copy, navigation, responsiveness, or usability; or polish an existing interface so users can complete their main job without confusion.
Use when integrating Stigg's drop-in UI components — paywall / pricing table, customer portal, checkout, and the credit widgets (balance, utilization, usage chart, grants table, auto-recharge status, auto-recharge configuration). Triggers include "Stigg paywall", "pricing table", "customer portal", "Stigg checkout", "credits widget", "credit balance widget", "Paywall component", "CustomerPortal component", "render Stigg widget", "widget designer", "client-side security", "stigg widgets storybook". Skip for headless gating logic — use stigg-entitlements.
Create beautifully designed travel guidebook PDFs from trip itineraries. End-to-end workflow from deep research to Playwright PDF export, featuring zero AI-generated images, Tabler Icons, inline SVG decorations, and Claude's warm parchment aesthetic. Use this skill whenever the user mentions 路书, 旅行指南, travel guidebook, 行程手册, trip planner, 自驾游攻略, itinerary book, 攻略, 出行指南, 旅行计划, 行程规划, or wants to turn trip notes into a printable guide. Also triggers for multi-day travel planning, route guides, road trip planners, 旅行攻略制作, 旅行PDF, or converting travel research into a professionally designed document.
Use this skill when planning, redesigning, or reviewing Xiaohongshu carousel visuals, covers, 3:4 image posts, page-by-page visual direction, image-generation prompts, style selection, layout critique, or XHS captions. It acts as a senior visual director for 小红书图文, not a generic copywriting assistant.
Add branded lower-third labels to an existing video - section names, feature names, speaker names - that slide in at the start of each segment. Use when the user says "add lower thirds", "add section labels", "label each part of the video", "add name titles", or "add branded segment titles".
Draw DIAGRAMS and CHARTS with tools, not by letting the model invent shapes. Call when the user says — Vietnamese "vẽ sơ đồ", "vẽ biểu đồ", "vẽ luồng", "sơ đồ kiến trúc", "sơ đồ hệ thống", "sơ đồ quy trình", "luồng xử lý", "flow", "graph", "đồ thị", "biểu đồ", "chart", "trực quan hoá", "visualize", "mô hình hoá", "vẽ hộ", "diagram hoá", "chuyển mô tả thành hình", "so sánh hai luồng"; English "draw a diagram", "architecture diagram", "workflow diagram", "sequence diagram", "data flow", "state machine", "lifecycle", "dependency graph", "org chart", "chart", "plot", "dashboard", "visualize this", "turn this into a diagram", "convert Mermaid", "diff two flows". Covers both families — RELATIONSHIP/FLOW diagrams (boxes + arrows) and DATA charts (numbers). NOT for UI/landing page screens — that's `hallmark`.
Coded HTML email templates that render across Outlook, Gmail, Apple Mail, and mobile: table layout, fluid-hybrid responsiveness, bulletproof buttons, email dark mode, and size limits. Use when the user asks to "design an email", "build an email template", "create a newsletter", "HTML email", "email layout", "transactional email", "welcome email", "promotional email", or any email template work. Not for web landing pages (landing-page-design) or web dark themes (dark-mode).
Extracts design data from Figma via the REST API and converts designs to React code. Use when syncing Figma tokens to CSS variables, exporting icons as SVG components, generating code from Figma designs, or automating design-to-code workflows. Use for design token extraction, icon export, component generation, and CI-based Figma sync.
Use when building portal pages, Web Forms, website routes, or configuring themes and SEO in Frappe. Prevents 404 errors from wrong route resolution, broken Web Form submissions, and missing meta tags for SEO. Covers Web Page, Web Form, Portal Settings, Website Settings, website routes, Jinja templates, Blog, Web Template, has_web_view, meta tags, sitemap. Keywords: website, portal, Web Form, Web Page, route, theme, SEO, meta tags, has_web_view, Blog, Web Template, sitemap, customer portal, self-service, public form, web page, website not showing, 404 on portal.
Generally-applicable frontend/UI best practices. Use whenever building, modifying, or reviewing UI — adding a form/button/dialog/modal, wiring keyboard shortcuts, creating any interactive surface that submits a form, or any time TSX/JSX is being written or edited. Consult BEFORE writing the code so the patterns are baked in, not retrofitted. If a scenario described in the skill body matches the work, apply the pattern — don't ask, just follow it (call out the choice in one line so the user can override).
Develop art direction for image generation with curated style cards distilled from Open Image Prompts. Use when choosing or comparing visual directions, improving an existing generation prompt, or translating a subject, use case, or supplied image into a compact creative spec. Use img-gen-prompts for real archive examples, exact source prompts, or gallery browsing.
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.