2,765 件 ・ 関連度順
概要と使いどころ
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
日本語の概要は準備中です。原文の説明を表示しています。
Activate for any ticket that touches a Supabase RPC, edge function, or TypeScript client function in src/lib/. Ensures both caller and callee are verified before state:ready-for-qa.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: Good night Team, EOD, Wrapping up, or end-of-day consolidation. Archives session context, promotes durable patterns, and compacts live agent memory files for the next session.
日本語の概要は準備中です。原文の説明を表示しています。
Analytical methodology skill for intelligence-grade research. Covers cognitive security, logical fallacy detection, source epistemology, and probability discipline. Load when evaluating sources, building analytical assessments, or detecting manipulation in information.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: analysing a project's delivery health — CI/CD, commit patterns, and working tree state.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: writing or reviewing a SKILL.md file, improving skill descriptions, organizing skill content, or needing guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
日本語の概要は準備中です。原文の説明を表示しています。
Activate for any ticket that changes React components, user-facing flows, or UI state. Ensures all five observable UI states are verified before state:ready-for-qa.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: analysing a project's architecture, structure, and infrastructure health from the System perspective.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: Tester runs a full QA session, processes a Builder handoff, executes test steps, writes a GitHub test report, or aligns ticket state after verification.
日本語の概要は準備中です。原文の説明を表示しています。
Token budgeting discipline for all agents. Treats tokens as a resource from session start — not just when the buffer hits 60%. Covers prompt compression, context hygiene, handoff packing, and HOT memory pruning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: UI standards discovery, UI pattern research, UI audit, pre-handoff UI state coverage review, or when a business-specific child skill needs a stack-agnostic UI methodology to load first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: investigating a legacy, inherited, third-party-built, or otherwise newly-unfamiliar codebase before scoping a migration or major refactor. Formalizes a repeatable five-step investigation pass — entry-point census, business-rule classification, side-effect/idempotency cataloging, implicit-contract discovery, semantic-duplication detection — plus a canonical per-project Open Questions document. Requires checkable signals: ticket keywords or prior documentation gaps. Not a mandatory gate; reserved for entry-point-heavy work in code areas with no prior investigation record.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: planner mode, planning mode, proposal, scope definition, estimate, timeline, client message, external communication, pricing, delivery confidence, commercial risk, or project delivery planning.
日本語の概要は準備中です。原文の説明を表示しています。
Universal guardrails loaded by every agent. Defines Verify Before Reporting (VBR), Write-Ahead Log (WAL), and the security baseline. Always-on, role-independent.
日本語の概要は準備中です。原文の説明を表示しています。
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
One-question-at-a-time design interrogation. Use when: 'grill me', 'interrogate this', 'one question at a time', 'brainstorm', 'let's brainstorm', 'let's discuss', or design review start. Produces ADRs and glossary as decisions settle. Do not use for settled designs — load architecture-mode instead.
日本語の概要は準備中です。原文の説明を表示しています。
Activate for any ticket that adds or changes a Supabase migration, environment variable, edge function deployment, or runtime configuration. Ensures infrastructure is live in the target QA environment before state:ready-for-qa.
日本語の概要は準備中です。原文の説明を表示しています。
Behavioral guardrails for implementation work. Reduces common LLM coding mistakes: overcomplication, silent assumption-picking, scope drift, and unverifiable success criteria. Load on Builder and software-engineer-mode.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: Good morning Team, start-of-day briefing, or morning status request. Architect orchestrates; Builder, Tester, and Router return their sections as subagents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: assessing how much context a deployed agent profile consumes before real work starts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: analysing a project's user-facing health — discoverability, documentation, and product clarity.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: a general codebase assessment, pre-migration/pre-rewrite review, or explicit security-focused request needs a structured, repeatable security audit pass covering hardcoded secrets, injection-prone constructs, auth/debug backdoors, and insecure config defaults. Complements (does not replace) the built-in /security-review command. Not a mandatory gate on every ticket.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: reviewing or producing any external-facing prose — ADRs, proposals, GitHub comments, Telegram messages, cover letters, client drafts, or planner-mode wording. Removes AI-tell patterns and raises writing quality before output leaves the team.
日本語の概要は準備中です。原文の説明を表示しています。