テスト設計、脆弱性診断、品質保証（1.4万 件）
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
日本語の概要は準備中です。原文の説明を表示しています。
Generate test scenarios from git branch changes. Compares current branch to main/master, identifies changed files, classifies them by type (frontend, API, backend, config), and generates test scenarios covering those changes. Produces a Markdown report with embedded screenshots for UI changes and CSV files compatible with the e2e-test skill for automated execution. Captures screenshots for frontend changes via the playwright-cli skill (no MCP browser server required). Diff-driven — not to be confused with the test-scenario skill, which works from a natural-language feature description instead. Use when the user asks to generate test scenarios, create test cases from changes, analyze branch for testing, generate test plan from diff, create e2e scenarios from code changes, or build test coverage for a branch. Trigger phrases include "generate test scenarios", "test scenarios for this branch", "create test cases from changes", "what should I test", "generate test plan", "test coverage for my changes", "scenario generator", "test scenario generator", "generate scenarios from diff", "create e2e scenarios", "test scenario from branch".
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
日本語の概要は準備中です。原文の説明を表示しています。
Senior QA/QC engineer that evaluates existing codebases for test quality. Runs existing tests, diagnoses failures, identifies missing test coverage, and writes missing tests. Framework-agnostic — works with any language and test runner. Use when the user asks to run tests, diagnose failures, do test gap analysis, QA, quality assurance, test coverage analysis, find missing tests, test audit, quality check, quality report, fix failing tests, evaluate test quality, or assess test health of a codebase. Trigger phrases include "run tests", "QA", "quality assurance", "test audit", "test coverage", "missing tests", "gap analysis", "quality report", "fix failing tests", "diagnose test failures", "quality check", "evaluate test quality", "test health".
日本語の概要は準備中です。原文の説明を表示しています。
Drive an already-running, LOGGED-IN Chromium browser on macOS via AppleScript — navigate, click, fill forms, scroll, and extract page content from the user's REAL session, with the browser left open and NO profile copy and NO restart. Use when the task needs the existing logged-in session (cookies, auth, current tabs) reused as-is. Trigger phrases: "chrome-use", "ブラウザから取得", "ログイン済みの Chromeで", "ブラウザを操作して", "このページ読んで", "Xのスレッド読んで", "ログインしたまま取得", "自分のセッションでスクレイプ", "read this page in my browser", "scrape with my session", "drive my chrome", "execute JS in my (logged-in) browser", "automate my logged-in browser". Chromium family (Chrome default; Brave/Edge/Arc/Vivaldi via --app). NOT for isolated/throwaway automation where login reuse is unneeded — use playwright-cli for that. macOS only.
日本語の概要は準備中です。原文の説明を表示しています。
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user names an operational control to implement, asks who handles what when something breaks, or wants audit or inspection readiness with evidence behind every pass.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions "salary negotiation", "contract terms", "handling objections", "mirroring and labeling", "difficult conversation", "deal terms", "BATNA", "anchoring", "how do I ask for a raise", "get a better deal", or "they wont budge on price". Also trigger when preparing for a vendor negotiation, resolving a pricing dispute, or navigating a high-stakes conversation where both sides need to feel heard. Covers accusation audits, Black Swan discovery, and the "Thats Right" technique. For persuasion in product and marketing, see influence-psychology.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a page the way a search engine reads it: what it is about, whether that is obvious, and the three fixes worth doing before anything else.
日本語の概要は準備中です。原文の説明を表示しています。
Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user-research questions, interpreting ambiguous feedback, or designing customer-discovery that avoids false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.
日本語の概要は準備中です。原文の説明を表示しています。
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint. For non-leading interview technique, see mom-test.
日本語の概要は準備中です。原文の説明を表示しています。
Create a structured interview loop that tests each rubric criterion once and captures independent evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a large deal needs procurement, legal, security, and pricing orchestration: mutual close plans, deal-desk runs, and signature.
日本語の概要は準備中です。原文の説明を表示しています。
Triage an intermittent test from run history, environment, and failure pattern before naming a cause.
日本語の概要は準備中です。原文の説明を表示しています。
Read an ad test by sample size and spread, and say whether there is a winner yet.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deals must clear compliance gates: licensing, suitability, audit readiness, and regulated-ops checks before close.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare a neutral brief for counsel or the security lead on a matter that needs their judgement.
日本語の概要は準備中です。原文の説明を表示しています。
Set up compliance work from policies, system inventory, audit reports, approved answers, and counsel contacts.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.
日本語の概要は準備中です。原文の説明を表示しています。
Review a dependency change for breaking APIs, runtime shifts, supply-chain risk, test gaps, rollout risk, and rollback quality.
日本語の概要は準備中です。原文の説明を表示しています。
Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.
日本語の概要は準備中です。原文の説明を表示しています。
Review a deal for evidence gaps across need, scope, stakeholders, process, competition, delivery, security, legal, and commercial approval.
日本語の概要は準備中です。原文の説明を表示しています。