「xp」の検索結果

Design platform-specific Android and iOS checks with explicit SDK, driver, device, lifecycle, and evidence prerequisites.

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

Define auditable QA metrics with explicit numerators, denominators, populations, windows, and treatment of every result state.

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

Review a code diff or explicit file set through independent correctness and QA lenses. Use when the user asks for a code review, test-coverage assessment, pre-merge audit, or review gate in a PWDEV Flow workflow.

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

Use when the user wants tests planned for existing code or a test audit — unit, integration, E2E scenarios exportable to Playwright, playwright-cli UI checks, a coverage matrix — 'criar testes para o UserService', 'plano de testes E2E do login', 'auditar a cobertura'. Writes .planning/feat/features/{slug}/plan.md. Do NOT use for code review (feat-review), for implementing features (feat-feature) or to run an existing plan (feat-exec).

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

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 encountering any bug, test failure, or unexpected behavior, before proposing any fix

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

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.

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

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.

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

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.

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

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.

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

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.

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

Analisa custo AWS e identifica desperdício em EC2, RDS, S3, EKS, EBS, Elastic IP, NAT Gateway e tráfego. Use quando o usuário disser "custo", "fatura", "está caro", "FinOps", "reduzir gasto AWS", "Cost Explorer", "otimizar custo". Quase todo leitura — seguro por natureza.

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

Quality gates determinísticos para PostgreSQL. Use quando o usuário pedir "quality gate PostgreSQL", "quality gate Postgres", migrations ou schema drift PostgreSQL, constraints ou índices PostgreSQL, EXPLAIN, plano de consulta ou baseline para PostgreSQL.

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

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.

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

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

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

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.

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

Segurança de infraestrutura e pipeline — Trivy, Falco, CrowdSec, Fail2Ban, WAF, TLS, IAM, secrets, OWASP, Security Hub. Use quando o usuário disser "segurança", "vulnerabilidade", "CVE", "hardening", "WAF", "secrets", "exposto", "auditoria de segurança", "pentest".

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

Search Haskell APIs using Hoogle. Use when working with Haskell projects to look up function signatures, find functions by type, discover library documentation, or identify which module exports an item.

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

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.

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

Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement minimal code to pass, then refactor. Essential for ensuring code reliability, preventing regressions, improving design through testability requirements, documenting expected behavior through tests, enabling confident refactoring, and maintaining high code quality standards throughout the development process.

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

Implement comprehensive security patterns to protect applications against OWASP Top 10 vulnerabilities including XSS, CSRF, SQL injection, authentication bypass, and data exposure. Use when handling user data, implementing authentication and authorization, validating input, encrypting sensitive data, preventing injection attacks, securing API endpoints, managing sessions and tokens, implementing rate limiting, configuring security headers, or building security-critical features that require defense-in-depth protection.

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

Create well-structured, comprehensive Claude skills with clear activation criteria, detailed descriptions, usage examples, and proper documentation following best practices. Use when documenting new workflows, creating reusable skill patterns, establishing coding standards as skills, building team knowledge base, or expanding the skills library with new capabilities.

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

Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.

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

Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems.

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