792 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Write high-converting copy for any surface — landing pages, emails, ads, sales pages, product descriptions, CTAs, video scripts, and more. Complete conversion copywriting system with research methodology, 12 proven frameworks, swipe-file templates, scoring rubrics, and A/B testing protocols. Use when you need to write or review any copy meant to drive action.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, prioritize, and design rigorous A/B tests using the Test Velocity Method. Use when a user wants to test a landing page, CTA, email, signup flow, pricing page, or any digital experience — this skill produces a complete, dev-ready test plan with hypothesis, sample size, duration, segmentation strategy, and guardrail metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-ready frontend interfaces with high visual quality. Use this skill whenever the user asks to build, design, or improve any web UI — including landing pages, dashboards, components, app screens, forms, or interactive widgets. Also trigger when the user says "make this look better", "redesign this", "add polish", "build a UI", "create a page", "style this", or references HTML/CSS/JS, React, Vue, Svelte, or any frontend framework. If the request involves any visible output rendered in a browser, use this skill — even if the user hasn't explicitly said "design." This skill produces intentional, memorable interfaces that avoid generic AI patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare Azure environments and prerequisites before deployment. Use this skill when users ask for readiness checks, environment setup, or preflight planning. Covers landing zones, networking, identity, governance, and cost controls per Cloud Adoption Framework.
日本語の概要は準備中です。原文の説明を表示しています。
Revisa o produce textos visibles para la persona usuaria (texto de UI, encabezados, botones, mensajes de error, marketing) con la voz y el tono del proyecto. Úsalo cuando la persona pida escribir/mejorar textos, corregir la redacción, revisar el tono o redactar microcopy (p. ej. "escribe el texto del estado vacío", "haz este mensaje de error más amable", "revisa el titular de la landing").
日本語の概要は準備中です。原文の説明を表示しています。
Multi-pass structural code review with adversarial analysis, scope-aware dispatch, adversarial persona passes, and forced-finding protocol. Supports input modes: branch diff (default), PR number (#123), commit hash, pending changes (--pending). Use when asked to "review this PR", "code review", "pre-landing review", "check my diff", or "review #123". Proactively suggest when the user is about to merge or land code changes. NOT for behavioral verification against a running build (see mk:evaluate); NOT for post-implementation simplification (see mk:simplify).
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a GitHub PR with a single shallow correctness/security/breaking/AI-slop checklist and emits a verdict; optionally posts it via gh pr review. Use to review an external or teammate PR. NOT for deep pre-landing audit of your own diff (see mk:review); NOT for responding to received review comments (see mk:respond-pr).
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow Phase 11 — Commit Preparation and Execution. Stages and commits the work. Requires `/grant-commit` first (Git Commit Guard enforces a 15-min ad-hoc consent window; inside a workflow the grant is slug-scoped and one grant covers the whole landing).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Practical UI refactoring and visual design review inspired by Refactoring UI by Steve Schoger and Adam Wathan. Use when an AI coding agent needs to improve an existing interface, audit visual polish, redesign a rough UI, review frontend code for hierarchy/spacing/typography/color/depth/image issues, or turn a plain implementation into a cleaner product-quality screen. Do not use for creating UI from scratch, scaffolding a new app, building a new landing page, or designing a new design system unless the user explicitly asks to review or refactor an existing interface.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Design one-off HTML artifacts (landing, deck, prototype).
日本語の概要は準備中です。原文の説明を表示しています。
Frontend UI design, critique, audit, polish. Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
日本語の概要は準備中です。原文の説明を表示しています。
Opinionated constraints for building better web interfaces with coding agents. Use this skill whenever the user asks you to build, review, or fix a UI — landing pages, dashboards, components, or any frontend code — and whenever you write Tailwind CSS, motion/react animations, accessible component primitives (Base UI, React Aria, Radix), or review agent-generated interface code for quality, accessibility, and performance. Also trigger for "make the UI better", "review my interface", "clean up this component", or any frontend work in React, Next.js, or plain HTML/CSS.
日本語の概要は準備中です。原文の説明を表示しています。
Crie designs de websites premium com qualidade Awwwards como componentes React (.jsx) que pareçam ter sido construídos por uma agência de primeira linha cobrando R$250k+ por projeto. Use esta skill sempre que o usuário pedir um website, landing page, portfólio, ou componente web que deve parecer caro, premium, luxo, editorial, high-end, ou de qualidade agência. Também dispare quando o usuário mencionar Awwwards, FWA, design premiado, ou referenciar marcas como Apple, Aesop, Bottega Veneta, Stripe, ou qualquer marca luxury/fashion/design-forward. Dispare quando o usuário disser coisas como "faça parecer profissional", "faça parecer caro", "quero que fique realmente bom", "design de alta qualidade", "não genérico", ou expressar insatisfação com aesthetics típicos de websites gerados por IA. NÃO dispare para dashboards, admin panels, ferramentas internas, ou UI funcional onde aesthetics são secundárias à utilidade — a skill padrão frontend-design cuida disso.
日本語の概要は準備中です。原文の説明を表示しています。
Inteligência de design UI/UX. 50 estilos, 21 paletas, 50 combinações de fontes, 20 gráficos, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Ações: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projetos: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elementos: button, modal, navbar, sidebar, card, table, form, chart. Estilos: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Tópicos: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrações: shadcn/ui MCP para busca de componentes e exemplos.
日本語の概要は準備中です。原文の説明を表示しています。
Criar interfaces frontend distintas e de qualidade produtiva com alto padrão de design. Use essa habilidade quando o usuário pedir para construir componentes web, páginas, artefatos, pôsteres ou aplicações (exemplos incluem websites, landing pages, dashboards, componentes React, layouts HTML/CSS, ou ao estilizar/embelezar qualquer UI web). Gera código criativo e polido com UI design que evita estéticas genéricas de IA.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer otimizar, melhorar ou aumentar conversões em qualquer página de marketing — incluindo homepage, landing pages, páginas de preços, páginas de features ou posts de blog. Também use quando o usuário menciona "CRO," "otimização de taxa de conversão," "essa página não está convertendo," "melhorar conversões," ou "por que essa página não funciona." Para fluxos de signup/registro, veja signup-flow-cro. Para ativação pós-signup, veja onboarding-cro. Para formulários fora de signup, veja form-cro. Para popups/modals, veja popup-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer escrever, reescrever ou melhorar copy de marketing para qualquer página — incluindo homepage, landing pages, páginas de preço, páginas de funcionalidade, páginas "sobre" ou páginas de produto. Também use quando o usuário disser "escreva copy para", "melhore essa copy", "reescreva essa página", "copy de marketing", "ajuda com headline" ou "copy de CTA". Para copy de email, veja email-sequence. Para copy de popup, veja popup-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer criar páginas de comparação com concorrentes ou alternativas para SEO e ativação de vendas. Use também quando o usuário menciona 'página de alternativas', 'página vs', 'comparação com concorrentes', 'página de comparação', '[Produto] vs [Produto]', '[Produto] alternativa', ou 'landing pages competitivas'. Cobre quatro formatos: alternativa singular, alternativas plurais, você vs concorrente, e concorrente vs concorrente. Enfatiza pesquisa profunda, arquitetura de conteúdo modular e tipos de seção variados além de tabelas de recursos.
日本語の概要は準備中です。原文の説明を表示しています。