7,510 件 ・ 関連度順
概要と使いどころ
Bidirectional Figma skill — read designs and write back to Figma. READ: extract tokens, map Vue/Reka UI components, translate Auto Layout to Tailwind. WRITE: push components, screens, and design tokens from code to Figma. Requires /figma:figma-use skill before every use_figma call.
日本語の概要は準備中です。原文の説明を表示しています。
Create or revise the problem-first SDD Composy PRD (tasks/prd-SLUG/prd.md) with stable RF/CA identifiers, stopping at the human approval gate. Use when a user problem needs a product contract — 'criar o PRD', 'documento de requisitos', 'revisar o PRD do slug X', 'write the requirements for…'. Do NOT use for user stories (sdd-stories), technical design (sdd-techspec), or PRDs outside an initialized SDD workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation, standardization, and governance of the Vue + shadcn-vue design system. Use when creating component documentation, auditing consistency, defining naming conventions, or generating usage guides for the team.
日本語の概要は準備中です。原文の説明を表示しています。
Compõe a peça final no Figma sobre os ativos gerados — texto, marca, layout e grid. Camada OPCIONAL: use quando houver Figma conectado e o time precisar do arquivo editável. Dispara em "montar no Figma", "compor a peça", "colocar o texto na imagem", "aplicar a marca", "arquivo editável". Sem Figma, entrega especificação de composição.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for analyzing a project's existing UI in Vue. Activates when the user uses /pwdev-uiux:scan or asks to "analyze the project UI", "map existing components", "understand project patterns", or "create project skill". Generates .planning/ui/project-ui-skill.md with project-specific patterns and tokens.
日本語の概要は準備中です。原文の説明を表示しています。
Traduz copy aprovada em conceito visual — ideia central, hierarquia, sistema de peças e especificação de ativos. Use quando o usuário disser "como fica visualmente", "conceito da campanha", "direção de arte", "qual a ideia da peça", "transformar a copy em criativo", ou antes de montar qualquer coisa no Figma. É a ponte entre pwdev-copy e a produção.
日本語の概要は準備中です。原文の説明を表示しています。
Monta carrossel completo — estrutura de slides, hierarquia por slide e construção no Figma como componente com variantes. Use quando o usuário disser "carrossel", "slides", "carrossel do LinkedIn", "carrossel do Instagram", "post em sequência", "documento do LinkedIn". Recebe a copy slide a slide e entrega frames montados e revisados.
日本語の概要は準備中です。原文の説明を表示しています。
Extrai o brand kit do Figma — tokens de cor, tipografia, grid, logo e componentes — e grava na seção 3 do contexto. Use quando o usuário disser "extrair a marca", "pegar os tokens", "quais as cores", "design system", "importar do Figma", "montar brand kit", ou quando a seção 3 estiver vazia. Lê do Figma; não inventa paleta.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a design or set of requirements exists and work needs decomposing into tasks, before touching any code
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
日本語の概要は準備中です。原文の説明を表示しています。
Design an approval-gated feature specification from approved requirements. Use when PWDEV Flow discovery is complete and the user needs architecture decisions, component boundaries, quality constraints, and a definition of done.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.
日本語の概要は準備中です。原文の説明を表示しています。
Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation
日本語の概要は準備中です。原文の説明を表示しています。
Design precise, production-grade enterprise UI — dashboards, admin panels, SaaS interfaces, and data-heavy applications. Use this skill for professional software interfaces that need Jony Ive-level craft: clean, minimal, functional, with intentional personality. Do NOT use for creative landing pages, marketing sites, or experimental/artistic frontends.
日本語の概要は準備中です。原文の説明を表示しています。
Transforma análise de desempenho em plano de ação priorizado por tiers — ganhos rápidos, mudanças estruturais, experimentos e o que parar de fazer. Use quando o usuário disser "o que eu faço agora", "como melhorar", "plano de ação", "por onde começo", "otimizar campanha", ou logo após perf-analyzer e perf-patterns. Fecha o ciclo: escrever → medir → aprender → escrever melhor.
日本語の概要は準備中です。原文の説明を表示しています。
Revisa e melhora copy existente através de 7 passes focados (clareza, voz, e daí, prove, especificidade, emoção, risco zero) somados à detecção determinística de padrões de escrita de IA. Use quando o usuário disser "revisar copy", "melhorar esse texto", "revisão", "está parecendo IA", "polir", "dar uma olhada nesse texto", "feedback de copy", ou logo após qualquer skill copy-* gerar um rascunho. Não reescreve do zero — aprimora preservando a mensagem central.
日本語の概要は準備中です。原文の説明を表示しています。
Escreve microcopy de interface — mensagens de erro, estados vazios, tooltips, rótulos de botão, onboarding e notificações. Use quando o usuário disser "UX writing", "microcopy", "mensagem de erro", "empty state", "texto do botão", "texto da interface", "onboarding do sistema".
日本語の概要は準備中です。原文の説明を表示しています。
AdwHeaderBar layout rules: button placement, flat/icon-only buttons, tooltips, title widgets, split buttons. Use when designing or fixing a GNOME app's header bar.
日本語の概要は準備中です。原文の説明を表示しています。
Add a standard GNOME preferences dialog (AdwPreferencesDialog) with Ctrl+comma shortcut, PreferencesPage/Group rows, and GSettings bindings. Use when adding settings or preferences UI to a GNOME app.
日本語の概要は準備中です。原文の説明を表示しています。
Exclusive-choice UI: CheckButton radio groups in list rows, when to use them vs ComboRow vs ToggleGroup. Use when presenting mutually exclusive options in GNOME preferences or dialogs.
日本語の概要は準備中です。原文の説明を表示しています。
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
日本語の概要は準備中です。原文の説明を表示しています。
Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs.
日本語の概要は準備中です。原文の説明を表示しています。
Create and maintain comprehensive brand guidelines including visual identity, tone of voice, messaging, color palettes, typography, and usage rules for consistent brand expression. Use when establishing brand identity, creating style guides, defining visual standards, setting tone of voice, creating brand assets, or ensuring brand consistency.
日本語の概要は準備中です。原文の説明を表示しています。