「tor」の検索結果

Route supported legacy PWDEV Code command intent to canonical PWDEV Flow skills. Use when the user mentions old /pwdev-code:* commands, asks for PWDEV Code compatibility, or wants to adopt an existing .planning workspace without losing history.

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

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

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

Diagnose repository and PWDEV Flow health without changing the project. Use when the user asks for a health check, workspace consistency check, dependency assessment, readiness report, or evidence-based scorecard.

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

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.

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

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 the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).

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

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

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

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.

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

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

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

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

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

Métricas, logs, traces, dashboards, alertas e SLO — Prometheus, Grafana, Loki, Tempo, Mimir, Zabbix, Alertmanager. Use quando o usuário disser "dashboard", "alerta", "métrica", "PromQL", "Grafana", "SLO", "golden signals", "não temos visibilidade", "monitoramento".

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

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

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

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

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

Define, documenta e aplica a voz da marca — formalidade, personalidade, vocabulário preferido, palavras proibidas e tratamento do leitor. Use quando o usuário disser "voz da marca", "tom de voz", "brand voice", "guia de estilo", "padronizar o tom", "não parece nossa marca", "manual de redação", ou quando precisar auditar se um texto está aderente. Extrai a voz de amostras reais em vez de inventar adjetivos, e grava o resultado na seção 5 de .claude/pwdev-copy-context.md para todas as demais skills consumirem.

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

Design security-conscious interfaces that protect users without frustrating them. Use when the user asks about MFA, password UX, breach notifications, trust indicators, secure forms, account recovery, or making security feel safe rather than scary.

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

Add moments of joy, personality, and surprise through success states, empty states, loading moments, hover details, and celebratory polish once the fundamentals already work. Use when the user wants delight, charm, personality, or memorable micro-interactions—not when the main need is baseline cleanup or stronger visual impact.

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

Extract reusable components, product patterns, and design tokens into a clearer design system with shared APIs, documented defaults, and better reuse. Use when the user wants to refactor repeated UI, consolidate buttons/cards/forms/sections, build a component library, or turn one-off values into reusable tokens.

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

Super-skill for developing Haskell projects with cabal nix-style builds. Orchestrates HLS diagnostics, Haddock, Hoogle, source formatting, and cabal-gild into one workflow. Use when writing, editing, refactoring, building, typechecking, fixing compiler errors, renaming symbols, looking up APIs, or changing dependencies in Haskell projects. Treat cabal.project as the source of truth, prefer HLS before full builds, and prefer local docs over remote lookup.

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

Read Haskell package documentation, Haddock HTML, Hackage pages, or dependency source for cabal nix-style projects. Prefer locally built/cached docs and source from the cabal store, dist-newstyle, plan.json, and repo-cache; fall back to Hackage only for packages outside the project dependency set or when local docs are unavailable.

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

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.

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

Build real-time, reactive backend applications with Convex using TypeScript queries, mutations, and actions with automatic reactivity and optimistic updates. Use when building real-time collaborative applications, implementing reactive data synchronization, writing serverless backend functions, creating queries that auto-update, implementing mutations with transactional guarantees, handling file uploads with Convex storage, implementing authentication with Convex Auth, designing reactive database schemas, or building applications requiring instant data synchronization.

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

Create comprehensive technical documentation including API docs, component libraries, README files, architecture diagrams, and developer guides using tools like JSDoc, Storybook, or Docusaurus. Use when documenting APIs, creating component documentation, writing README files, generating API references, documenting architecture decisions, creating onboarding guides, maintaining changelogs, documenting configuration options, or building developer documentation sites.

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

Build modern Next.js 13+ applications using App Router architecture with Server Components, Client Components, and advanced routing patterns. Use when implementing server-first rendering, creating nested layouts, building parallel routes, implementing intercepting routes, using React Server Components, optimizing data fetching with server-side async components, implementing streaming with Suspense, managing client-side interactivity boundaries, or leveraging Next.js 13+ app directory features for performant, SEO-friendly React applications.

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