「va」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

Audit of existing Vue components in the project. Use when reviewing Vue design system consistency, identifying duplicate patterns, evaluating legacy components (Options API), or before implementing something new.

日本語の概要は準備中です。原文の説明を表示しています。

Exporta peças aprovadas do Figma e monta o pacote de entrega — arquivos nomeados, legendas, texto alternativo e instruções de publicação. Use quando o usuário disser "exportar", "baixar as peças", "pacote final", "entregar para publicação", "handoff", "mandar para o social". Só exporta o que passou na revisão.

日本語の概要は準備中です。原文の説明を表示しています。

Generate and safely advance the SDD Composy task projection from approved PRD, stories, and TechSpec: import contracts, list/next/show, and guarded start/block/transition/verify. Use when work must be decomposed or a task's state inspected or moved — 'quebrar a spec em tarefas', 'listar as tarefas', 'qual a próxima task', 'mark TASK-003 blocked'. Do NOT use to implement a task (sdd- execute), reconcile Markdown and JSON (sdd-sync), or for a status overview (sdd- status).

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Canonical design token registry — colors, typography, spacing, sizing, border radius, shadows, z-index, breakpoints, motion, and focus tokens. Used by ui-best-practices rules and all agents that implement or review UI components. Includes CSS variable template for quick project setup.

日本語の概要は準備中です。原文の説明を表示しています。

Responde dimensão, proporção, área segura, tipografia mínima e contagem de slides por plataforma. Use quando o usuário perguntar "qual o tamanho", "que dimensão", "quantos slides", "área segura", "cabe texto onde", "especificação do formato", ou quando outra skill precisar validar medidas. Fonte única desses números.

日本語の概要は準備中です。原文の説明を表示しています。

Estima, confirma e acompanha o gasto com geradores pagos. Use quando o usuário disser "quanto vai custar", "orçamento", "quanto gastei", "controlar custo", "está caro", antes de qualquer lote de geração, ou ao fechar campanha. Com APIs no centro, custo deixa de ser detalhe e vira restrição de projeto.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Recommend context-appropriate QA tools while preserving observed availability, constraints, and safer alternatives.

日本語の概要は準備中です。原文の説明を表示しています。

Export one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to change an existing PRD — 'refinar o PRD', 'adicionar requisito', 'atualizar escopo do PRD', 'update the PRD' — through targeted questions, bumping the version and re-opening approval. Do NOT use to create a PRD (prd-create).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Design traceable functional test conditions across positive, negative, boundary, and error behavior with observable expectations.

日本語の概要は準備中です。原文の説明を表示しています。

Design traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.

日本語の概要は準備中です。原文の説明を表示しています。

Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.

日本語の概要は準備中です。原文の説明を表示しています。

Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the status, progress, completeness, traceability, or next valid action of a PWDEV Power product roadmap is requested

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Use when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.

日本語の概要は準備中です。原文の説明を表示しています。

Create an approval-gated product requirements document or decompose an approved PRD into a traceable roadmap. Use for product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, or roadmap planning.

日本語の概要は準備中です。原文の説明を表示しています。