「rev」の検索結果

Run a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a task até passar', 'start a loop on task 4'. Do NOT use for the host's recurring loop runner, for fleets (sdd-fleet), or for a task without human approval.

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

Canonical UI/UX best practices ruleset with 14 sections and 70+ rules prioritized P0–P3. Use when implementing, reviewing, or auditing UI components. P0 rules are mandatory — violations are bugs. All rules reference tokens from ui-theme-reference.

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

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

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

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

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

Use when a user asks for QA planning, execution, review, release assessment, reporting, status, or test-tool recommendations and the correct PWDEV QA workflow must be selected safely.

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

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.

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

Analyze a completed phase diff for high-confidence behavior-preserving simplifications and apply only explicitly approved proposals. Use after execution and before review to reduce duplication, dead code, needless complexity, or avoidable inefficiency.

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

Use when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks

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

Deliver a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

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

Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.

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

Use when the user wants to execute an existing pwdev-feat action plan — 'executar o plano user-crud', 'exec latest', 'rodar o plano', 'retomar a execução'. Dispatches the executor (subagent when the runtime has one, inline otherwise) in IMPLEMENT or REPORT mode, handles NEEDS_ADVICE with the advisor, and supports --resume. Do NOT use to create plans (feat-feature, feat-backend, feat-frontend, feat-test, feat-review) or for tasks without a plan (feat-quick).

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

Delegate a bounded repository task to an allowlisted external coding CLI through the guarded Flow runner. Use for automatic provider selection or explicit Codex, OpenCode, Kimi, Gemini, or Kiro delegation that requires timeout handling and independent local review.

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

Escreve copy para redes sociais — post avulso, carrossel, thread e legenda — respeitando limite, formato e cultura de cada plataforma. Use quando o usuário disser "post para", "legenda", "conteúdo para LinkedIn", "carrossel", "social media", "adaptar para as redes", "texto do Instagram". Para o gancho isolado ver copy-hooks; para derivar de material existente ver copy-repurpose.

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

Escreve sequências e e-mails isolados — onboarding, nutrição, recuperação de carrinho, lançamento, newsletter e cold email. Use quando o usuário disser "e-mail marketing", "sequência de e-mails", "newsletter", "cold email", "fluxo de nutrição", "recuperação de carrinho", "automação de e-mail".

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

Arquitetura e diagnóstico AWS — VPC, EC2, ECS, EKS, ALB, NLB, RDS, ElastiCache, S3, CloudFront, Route53, IAM, WAF, GuardDuty. Use quando o usuário disser "AWS", "VPC", "ALB", "RDS", "revisar a arquitetura", "Well-Architected", "subnet", "security group", "IAM", ou citar qualquer serviço AWS. Leitura livre; qualquer mudança passa pelo portão de confirmação.

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

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

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

Confiabilidade da plataforma — SLO, error budget, capacidade, resiliência, ponto único de falha e revisão de prontidão. Use quando o usuário disser "SLA", "SLO", "disponibilidade", "resiliência", "aguenta?", "single point of failure", "production readiness", "quanto de folga temos".

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

Escreve roteiros de vídeo e VSL — gancho, abertura, desenvolvimento, prova, CTA e fechamento, com marcação de tempo e indicação visual. Use quando o usuário disser "roteiro", "VSL", "script de vídeo", "vídeo de vendas", "reels", "roteiro para YouTube".

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

Planeja estratégia de conteúdo — pilares, clusters de tópico, pauta por estágio de compra e priorização ponderada. Use quando o usuário disser "estratégia de conteúdo", "sobre o que escrever", "pauta", "calendário editorial", "cluster de tópicos", "plano de blog".

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

Otimiza a estrutura e a conversão de páginas de marketing — hierarquia, ordem das seções, posicionamento de CTA, sinais de confiança e pontos de atrito. Use quando o usuário disser "CRO", "essa página não converte", "melhorar conversão", "por que ninguém clica", "otimizar a landing". Cuida de estrutura; para reescrever o texto ver copy-page.

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

Audita e diagnostica SEO — técnico, on-page e qualidade de conteúdo. Use quando o usuário disser "auditoria de SEO", "não estou rankeando", "SEO técnico", "meta tags", "Core Web Vitals", "revisar SEO do site".

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

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

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

Implement React Server Actions in Next.js 14+ for secure, progressively enhanced form handling and server mutations without API routes. Use when handling form submissions, performing server-side mutations, implementing progressive enhancement, creating actions that work without JavaScript, validating data on the server, revalidating cached data after mutations, handling file uploads server-side, implementing optimistic UI updates, or building forms that gracefully degrade without client-side JavaScript.

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