Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
4.8万 件 ・ 関連度順
Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Execute an explicitly authorized exploratory charter and record notes, findings, evidence, and follow-up without claiming false coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.
日本語の概要は準備中です。原文の説明を表示しています。
Export one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.
日本語の概要は準備中です。原文の説明を表示しています。
Review requirements, coverage, results, evidence, and findings without changing the product or recorded state.
日本語の概要は準備中です。原文の説明を表示しています。
Triage defects with independent severity and priority, reproducible evidence, preserved attempt history, and explicit resolution retesting.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any conversation in a repository that uses PWDEV Power - establishes how to find and apply Power skills before any response, including clarifying questions
日本語の概要は準備中です。原文の説明を表示しています。
Build an impact-based regression selection with explicit traceability, inclusions, exclusions, and limitations.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.
日本語の概要は準備中です。原文の説明を表示しています。
Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.
日本語の概要は準備中です。原文の説明を表示しています。
Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.
日本語の概要は準備中です。原文の説明を表示しています。
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 when encountering any bug, test failure, or unexpected behavior, before proposing any fix
日本語の概要は準備中です。原文の説明を表示しています。
Decompose an approved PWDEV Flow specification into dependency-aware waves and atomic executable tasks. Use when design is approved and the user needs exact file scope, test-first actions, verification commands, and an execution gate.
日本語の概要は準備中です。原文の説明を表示しています。
Launch, inspect, and tear down autonomous phase fleets in isolated Git worktrees, on the Codex or the Claude runtime. Use when approved Flow phase slugs should run in parallel, when fleet status is requested, or when a fleet member must be stopped or explicitly merged.
日本語の概要は準備中です。原文の説明を表示しています。
Execute approved PWDEV Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence. Use after the plan gate is approved or for approved Flow correction tasks.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnóstico e tuning de PostgreSQL — EXPLAIN ANALYZE, índice, VACUUM, bloat, lock, replicação, WAL, PITR e particionamento. Use quando o usuário disser "postgres", "query lenta", "índice", "EXPLAIN", "vacuum", "lock", "deadlock", "replicação", "conexões", "banco lento".
日本語の概要は準備中です。原文の説明を表示しています。
Transforma uma peça de conteúdo em várias — case em thread, webinar em posts, artigo em carrossel, vídeo em cortes. Use quando o usuário disser "reaproveitar", "transformar isso em", "adaptar para", "repurpose", "derivar conteúdo", "aproveitar melhor esse material", "do blog para as redes", ou apresentar material longo pedindo derivados. Produz peça nativa de cada canal, nunca copia e cola.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Configuração e diagnóstico de Nginx — reverse proxy, TLS, HTTP/2, HTTP/3, cache, compressão, rate limit e load balancing. Use quando o usuário disser "nginx", "reverse proxy", "502", "504", "certificado", "SSL", "TLS", "rate limit", "cache", "upstream".
日本語の概要は準備中です。原文の説明を表示しています。
Estratégia de quality gates determinísticos e adoção incremental para CI/CD. Use quando o usuário pedir "quality gate", "gate de qualidade", "política de bloqueio", "baseline", "ratchet", "qualidade no CI" ou "SonarQube".
日本語の概要は準備中です。原文の説明を表示しています。