9.4万 件 ・ 関連度順
概要と使いどころ
Use quando um roadmap pwdev-roadmap/1 (roadmap.json) precisar ir para o GitHub — 'publicar o roadmap', 'criar as issues do roadmap', 'publish roadmap.json' — com issues, sub-issues, milestones, blocked-by e campos do Project, com dry-run, idempotente e retomável. Não use para uma issue avulsa (github-issues).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize, inspect, resume, or migrate portable PWDEV Flow project state. Use when the user asks to set up PWDEV Flow, adopt an existing repository or legacy PWDEV Code workspace, resume its workflow, or diagnose its current state.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repository has no PWDEV Power workspace yet, when resuming one, when the codebase map needs refreshing, or when the setup should be checked
日本語の概要は準備中です。原文の説明を表示しています。
Use when approved phases should run in parallel — visually in a cmux panel or unattended — when fleet status is requested, or when a fleet member must be stopped or merged
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product requirement, PRD, or executable roadmap is requested, or when an approved requirement needs decomposing into phases, epics, features and tasks
日本語の概要は準備中です。原文の説明を表示しています。
Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation
日本語の概要は準備中です。原文の説明を表示しています。
Curate durable PWDEV Flow project decisions, lessons, and conventions. Use when the user asks to capture, list, show, link, supersede, or select project memory, or when an approved workflow decision should persist across phases.
日本語の概要は準備中です。原文の説明を表示しています。
Implementa e valida dados estruturados schema.org em JSON-LD — Organization, Article, FAQPage, Product, BreadcrumbList. Use quando o usuário disser "schema", "dados estruturados", "JSON-LD", "rich snippet", "FAQ schema", "schema.org".
日本語の概要は準備中です。原文の説明を表示しています。
Infraestrutura para IA — GPU, servidores MCP, gateway de LLM, pipeline de inferência, custo de token, cache semântico e observabilidade de modelo. Use quando o usuário disser "GPU", "MCP server", "LLM", "inferência", "modelo", "gateway de IA", "custo de token", "rate limit da API de IA", "self-host de modelo".
日本語の概要は準備中です。原文の説明を表示しています。
Diagnóstico e operação de Kubernetes — pods, deployments, ingress, HPA, PVC, StorageClass, NetworkPolicy, Secrets, Helm, ArgoCD, cert-manager. Use quando o usuário disser "kubernetes", "k8s", "pod", "deployment", "ingress", "CrashLoopBackOff", "não sobe", "escalar", "helm", "argocd". Leitura livre; apply, scale, delete passam pelo portão.
日本語の概要は準備中です。原文の説明を表示しています。
Dockerfile, multi-stage build, Compose, buildx, registry, otimização e segurança de imagem. Use quando o usuário disser "docker", "dockerfile", "imagem", "container", "build", "compose", "imagem muito grande", "trivy", "vulnerabilidade na imagem".
日本語の概要は準備中です。原文の説明を表示しています。
Proxmox VE e PBS — cluster, quorum, Ceph, LXC, VM, HA, replicação, storage e backup. Use quando o usuário disser "proxmox", "PVE", "ceph", "LXC", "container LXC", "VM não sobe", "cluster sem quorum", "PBS", "backup da VM". Sem MCP nem CLI padrão instalada — opera via SSH no nó ou API REST.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Wire up GSettings: schema authoring, key naming, settings binding to widgets, window state persistence. Use when persisting app settings or window size/state in a GNOME app.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Flat page switching with AdwViewStack + AdwViewSwitcher (3-5 top-level views) and ViewSwitcherBar on narrow widths. Use when an app needs tabs/views in the header bar.
日本語の概要は準備中です。原文の説明を表示しています。
Build or improve UI test coverage for visual regression, interactions, and accessibility. Use when the user asks for a test strategy, automated tests, testing setup, or fixes to flaky UI tests. A one-time browser inspection or visual review does not require a new test suite.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify cluttered UI by removing unnecessary elements, choices, features, and structural complexity. Use when the problem is too many controls, options, features, or competing elements—not when the structure is sound and the real issue is only visual intensity or lack of personality.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
日本語の概要は準備中です。原文の説明を表示しています。