Orquestrador de desenvolvimento de jogos. Roteia para skills especializadas por plataforma com base nas necessidades do projeto.
日本語の概要は準備中です。原文の説明を表示しています。
7,581 件 ・ 関連度順
概要と使いどころ
Orquestrador de desenvolvimento de jogos. Roteia para skills especializadas por plataforma com base nas necessidades do projeto.
日本語の概要は準備中です。原文の説明を表示しています。
Use o servidor Figma MCP para buscar contexto de design, screenshots, variáveis e assets do Figma, além de traduzir nós do Figma em código de produção. Ative quando uma tarefa envolver URLs do Figma, IDs de nós, implementação design-to-code ou configuração e troubleshooting do Figma MCP.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Conversão pixel-perfeita de Figma para React usando coderio. Gera código pronto para produção (TypeScript, Vite, TailwindCSS V4) com alta fidelidade visual. Inclui tratamento robusto de erros, recuperação de checkpoints e execução simplificada via script auxiliar.
日本語の概要は準備中です。原文の説明を表示しています。
Applies Canvas brand colors, typography, and visual polish to artifacts that benefit from a consistent product look-and-feel. Use it when brand colors, style guidelines, visual formatting, or company design standards apply.
日本語の概要は準備中です。原文の説明を表示しています。
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project involves writing, editing, or reviewing content for a general audience, including UI copy, help text, error messages, documentation, and instructions. Under no circumstances use jargon, complex sentence structures, or unexplained acronyms without providing plain alternatives. Absolutely always target a reading level accessible to the broadest possible audience. Load alongside content-design/SKILL.md for all content work.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever writing, editing, or reviewing any web content, copy, headings, labels, error messages, or instructions. Under no circumstances write inaccessible content — every piece of text must be clear, structured, and usable by people with cognitive, visual, and language differences. Absolutely always apply plain language, logical heading hierarchy, and meaningful link text.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround. Absolutely always record any temporary local divergence with an owner and removal condition. Under no circumstances open, comment on, or submit anything in an external project without explicit human approval.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project includes print stylesheets, print media queries (@media print), or any content intended for physical printing. Under no circumstances omit print CSS that ensures readable, accessible printed output. Absolutely always hide decorative elements, expand link URLs, and maintain sufficient contrast and font sizing in print styles.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project contains interactive UI elements that users touch, tap, click, drag, swipe, or gesture with — buttons, links, drag-and-drop interfaces, sliders, carousels, or custom touch interactions. Under no circumstances create touch targets smaller than 44×44 CSS pixels. Absolutely always provide pointer cancellation, single-pointer alternatives to gestures, and load alongside keyboard/SKILL.md since pointer and keyboard requirements are complementary.
日本語の概要は準備中です。原文の説明を表示しています。
Judge performance or resource claims on real hardware: benchmark design or review, latency, throughput, memory or headroom numbers, and accept-or-reject decisions on optimizations. Not for refactors with no resource claim.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, redesigning, or improving a frontend interface in Angular, React, or Blazor. Use for landing pages, dashboards, components, forms, and responsive layouts that must work mobile-first and then scale to desktop.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Single owner of everything under docs/architecture/ — ADRs, architecture and design documents, and architecture diagrams. Routes each deliverable to the right engine: /mermaid-architecture for Markdown-native diagrams, /drawio-architecture for editable .drawio diagrams, and the optional archify skill for interactive standalone HTML diagrams (used only when already installed in the environment; never installed at runtime). Use whenever architecture documentation, ADRs, or architecture diagrams must be created or updated.
日本語の概要は準備中です。原文の説明を表示しています。
Apply semantic HTML/JSX and WAI-ARIA correctly and minimally. Apply when implementing any UI, especially forms, interactive components, or when accessibility is mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate UI/flows from cognitive load, error prevention, and accessibility perspectives. Apply when reviewing UX, discussing user confusion, high drop-off, or form usability issues.
日本語の概要は準備中です。原文の説明を表示しています。
Design UI as information architecture + interaction + visual tone, then translate into implementable specs. Apply when discussing screen design, component design, design systems, or visual hierarchy.
日本語の概要は準備中です。原文の説明を表示しています。
Remove Gemini AI watermarks from images using GeminiWatermarkTool (GWT). Use this skill whenever the user mentions: Gemini watermark, 浮水印, AI image cleanup, removing logos from Gemini-generated images, Google ImageFX cleanup, batch processing AI-generated photos, or anything about a semi-transparent logo in the bottom-right corner of an image — even if they don't say "GeminiWatermarkTool" explicitly. Also trigger for follow-up requests like "the corner still looks dirty" or "there's still residual artifacts" after a previous removal attempt.
日本語の概要は準備中です。原文の説明を表示しています。
Designs public or private Agent Skill and plugin marketplaces for Cursor, Claude Code, Codex, Zed, Open Plugin, and npx skills—manifest layout, install matrix, and Skill Steward vs product boundaries. Use when setting up a marketplace, distributing skills/plugins to a team, private registry, .cursor-plugin, .codex-plugin, .plugin, .claude-plugin, or skills.sh publishing.
日本語の概要は準備中です。原文の説明を表示しています。