4,595 件 ・ 関連度順
概要と使いどころ
Finalize documentation changes for production readiness by discovering existing conventions, verifying code-doc alignment, reviewing format/terminology/tone consistency, verifying branch/worktree intent, and structuring clean commits with a post-publish branch/worktree cleanup decision. Counterpart of finalize-and-commit for documentation projects.
日本語の概要は準備中です。原文の説明を表示しています。
Finalize code changes for production readiness by removing duplicate logic, auditing hardcoded values, verifying branch/worktree intent, verifying build integrity, structuring clean commits with Conventional Commits format, and forcing a post-publish branch/worktree cleanup decision.
日本語の概要は準備中です。原文の説明を表示しています。
Verify that the current Git branch, upstream state, and dirty working tree match the user's intended task before staging, committing, pushing, or continuing work from another session. Use this to detect stale branch reuse, leftover dirty files from previous sessions, unrelated commits on the current branch, cases where work should be split into a new branch or worktree, and post-publish cleanup decisions after push, PR creation, or PR merge.
日本語の概要は準備中です。原文の説明を表示しています。
Use BEFORE any verbose CLI run, large file read, doc conversion, or near-context handoff — decision tree keyed by intent citing the canonical token-saving asset.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stakeholders pull a decision in different directions — frames each lens, builds a trade-off matrix, surfaces the cost of every choice — even if the user just says 'PO and ops disagree'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "write a spec", "create RFC", "write a PRD", or "document this decision". Writes technical specifications, PRDs, RFCs, and ADRs with clear structure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reasoning about cash runway — burn shape, fundraise triggers, layoff-vs-cut-vs-grow decisions. Triggers on 'how long do we have', 'should we raise', 'cut or grow'.
日本語の概要は準備中です。原文の説明を表示しています。
When picking a secrets store, designing rotation, or wiring scanning gates — multi-cloud (Vault, AWS, Azure, GCP), CI and Kubernetes — decision framework, provider deep-dives externalized.
日本語の概要は準備中です。原文の説明を表示しています。
Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized.
日本語の概要は準備中です。原文の説明を表示しています。
When co-authoring a PRD, design doc, RFC, decision doc, or technical spec — 3-stage flow (context → section-by-section → reader-test) — even if the user just says 'help me write this spec'.
日本語の概要は準備中です。原文の説明を表示しています。
Shared corpus-grounding engine — BM25 + structured filters + decision rules over CSV corpora via a domain manifest. Use when a skill needs grounded pre-action option-space constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.
日本語の概要は準備中です。原文の説明を表示しています。
Route codebase-structure questions (who calls X, where used, change-impact) to an existing code-graph first: impact, tests-for, dead cheaper, never more precise; grep routine. Also 'call graph'.
日本語の概要は準備中です。原文の説明を表示しています。
When writing Python asyncio code — picking between gather / TaskGroup / wait, structured concurrency, timeouts, cancellation, sync-bridging — decision framework only, cookbook externalized.
日本語の概要は準備中です。原文の説明を表示しています。
Grounded brand decisions from a curated corpus — archetype, voice, naming, colour psychology, logo-style fit, messaging frameworks, archetype→type mapping. Use to ground brand strategy and identity.
日本語の概要は準備中です。原文の説明を表示しています。
All agents have equal voice; decisions made by majority vote.
日本語の概要は準備中です。原文の説明を表示しています。
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
日本語の概要は準備中です。原文の説明を表示しています。
Combine independent work from two or more selected agents into one decision-ready research report, design, or proposal. Preserve useful complementary findings, develop stronger combined options, and present material alternatives only when they exist. Use when multiple perspectives should improve the product without forcing consensus or staging disagreement.
日本語の概要は準備中です。原文の説明を表示しています。
Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.
日本語の概要は準備中です。原文の説明を表示しています。
Criar um plano conciso. Use quando um usuário solicitar explicitamente um plano relacionado a uma tarefa de codificação.
日本語の概要は準備中です。原文の説明を表示しています。
Padrões pragmáticos de codificação - conciso, direto, sem over-engineering, sem comentários desnecessários
日本語の概要は準備中です。原文の説明を表示しています。
Esta habilidade deve ser usada quando o usuário pede para "criar um slash command", "adicionar um comando", "escrever um comando personalizado", "definir argumentos de comando", "usar frontmatter de comando", "organizar comandos", "criar comando com referências de arquivo", "comando interativo", "usar AskUserQuestion em comando", ou precisa de orientação sobre estrutura de slash command, campos de frontmatter YAML, argumentos dinâmicos, execução bash em comandos, padrões de interação com usuário, ou melhores práticas de desenvolvimento de comando para Claude Code.
日本語の概要は準備中です。原文の説明を表示しています。
Princípios de design de banco de dados e tomada de decisão. Design de schema, estratégia de indexação, seleção de ORM, bancos de dados serverless.
日本語の概要は準備中です。原文の説明を表示しています。
Princípios de deploy em produção e tomada de decisão. Workflows seguros de deployment, estratégias de rollback e verificação. Ensina raciocínio, não scripts.
日本語の概要は準備中です。原文の説明を表示しています。