「que」の検索結果

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

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

Conduz investigação de incidente — triagem, hipótese, mitigação, RCA e postmortem. Use quando o usuário disser "está fora do ar", "incidente", "caiu", "usuários reclamando", "erro em produção", "postmortem", "RCA", "o que aconteceu". Durante incidente, a pressa causa o segundo incidente.

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

Gera e testa ganchos — primeira linha de post, abertura de e-mail, headline de anúncio, texto de miniatura, título de vídeo. Use quando o usuário disser "gancho", "hook", "primeira linha", "abertura", "como começar o post", "ninguém passa da primeira linha", "chamada", "título que prenda", ou quando pedir variações de abertura. Trabalha por biblioteca de 9 padrões nomeados, não por inspiração. Para o texto completo, ver copy-social, copy-email ou copy-ads.

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

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

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

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

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

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.

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

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.

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

Use when the user wants to query the local pwdev audit trail — 'ver auditoria', 'relatório de auditoria', 'audit stats', 'exportar auditoria em PDF' — summary, events, decisions, artifacts, statistics, a Markdown/PDF export or a custom read-only SELECT. Do NOT use to enable the audit (feat-init) or for plan status (feat-status).

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

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

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

Add a Keyboard Shortcuts help window (Ctrl+question) listing all app accelerators, plus the standard GNOME accelerator set. Use when wiring keyboard shortcuts or the Keyboard Shortcuts menu item.

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

Sequential multi-step setup flow (assistant/wizard) with AdwNavigationView, Back/Forward navigation, progress indication. Use when building onboarding or setup flows with ordered steps.

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

Prepare or update a Fabric pull request by proving the changeset-or-skip decision, validation evidence, DCO sign-off, and public-safe PR metadata. Use before the first push, after later revisions, or when asked to create or update a PR. Do not use to review an unrelated PR or authorize relay.

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

Deploy and optimize applications on Vercel with preview deployments, edge functions, environment variables, and performance monitoring. Use when deploying Next.js applications, setting up preview deployments per pull request, configuring environment variables, using Vercel Edge Functions, optimizing build performance, implementing redirects and rewrites, configuring custom domains, or monitoring application performance with Vercel Analytics.

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

Manage source control effectively with Git including branching strategies, commit conventions, merge conflict resolution, rebasing, and collaboration workflows like GitHub Flow or GitFlow. Use when managing feature branches, creating meaningful commits, resolving merge conflicts, rebasing branches, squashing commits, using interactive rebase, implementing branch naming conventions, following commit message standards, managing pull requests, or collaborating in team environments.

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

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.

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

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.

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

Generate comprehensive changelogs from Git history, commit messages, pull requests, and issue tracking for release documentation. Use when preparing releases, documenting changes, creating release notes, categorizing commits, generating version summaries, maintaining project history, or automating changelog updates.

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

Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring techniques like extracting functions, removing duplication, simplifying conditionals, and applying design patterns. Use when reducing technical debt, extracting functions or classes, removing code duplication, simplifying complex conditionals, renaming for clarity, applying design patterns, improving code organization, reducing coupling, increasing cohesion, or maintaining test coverage during structural improvements.

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

Implement real-time features using Convex reactive queries that automatically update when data changes, enabling live collaboration, instant updates, and reactive UIs without manual polling. Use when building live dashboards, implementing collaborative editing, creating chat applications, showing real-time notifications, building activity feeds, implementing presence indicators, creating reactive search, or any feature requiring instant data synchronization across clients.

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

Systematically review pull requests, feature implementations, and code changes to ensure quality, maintainability, security, and adherence to best practices. Use when reviewing code before merging, conducting peer reviews, performing self-reviews, auditing code quality, checking for security vulnerabilities, ensuring consistent coding standards, verifying test coverage, assessing performance implications, evaluating architectural decisions, or providing constructive feedback to improve team code quality.

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

Genera o actualiza una especificación SDD (spec.md) para HagamosTech. Úsala cuando haya que definir una nueva funcionalidad o vertical antes de tocar código, entrevistando al usuario y produciendo requisitos funcionales en notación EARS. Trigger: crear/actualizar spec, nuevo requisito, /spec.

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

Daily per-section review cycle driving a section toward the smallest, clearest form that still does everything it does today. Selects its section live each run (scripted), inventories every file, derives the target shape before any scan, works parallel reading threads into one ranked list and strikes it on a 2-3h budget. One PR per run; each run's report and Needs-Peter queue live in its own docs/health/runs/ file; 'resume' applies Peter's answers later. Use for the morning section-improvement run, 'doctor <section>', or 'run section doctor'.

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

Autonomous themed tech-debt cleanup. Reads docs/architecture/debt-ledger.yml, rotates to the least-recently-served debt theme, works it for a time budget (default 2h) or until drained, opens one PR, and asks judgment questions inline at the end. Use for daily debt burndown without Peter pointing at a target: grandfathered analyzer rules, architecture-test baselines, obsolete-field reads, cross-section stitching.

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

Use when a sprint tracking issue (label `sprint`) on peterdrier/Humans needs working — routine-fired cloud runs, or any unattended session told to execute the sprint queue.

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