테스트·보안 스킬

Use when a change adds or changes a host decision (a stop, park, decline, refusal, retry, deadline or cap growth), when the bench loop exports a round's traces, or when replay-corpus.test fails. Keeps the bench-trace replay corpus complete and current.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate test outlines (living documentation) and test code from natural language feature descriptions. Supports .NET (xUnit/NUnit/MSTest), Python (pytest), TypeScript (Vitest/Jest). Strict mode: no internal module mocking, real DB, AAA pattern, Design by Contract (DbC). Use when the user asks to generate tests from a feature description, create test cases from requirements, write test outlines, scaffold test files, generate test code from spec, convert TODO tests to real tests, or create tests for a function. Trigger phrases include "test scenario", "テストシナリオ", "generate tests", "テスト生成", "テストケース作成", "write tests for", "scaffold tests", "tests from requirements", "テストアウトライン", "convert todo tests", "implement test outline", "test outline", "test cases from spec".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review local git changes or an architecture document against the Security, Privacy, and Compliance pillar of Google's Cloud Well-Architected Framework. Identifies gaps across 7 principles (security by design, zero trust, shift-left, preemptive defense, AI used securely, regulatory/privacy, shared responsibility), and for each non-trivial risk asks the user to decide Accept / Mitigate / Defer / Block — producing a documented risk register, not just a finding list. GCP-principle-based but cloud-agnostic. Use when the user asks for a security architecture review, Well-Architected security check, threat / risk review, or zero-trust assessment. Trigger phrases include "well architected security", "GCP security review", "security pillar review", "security risk review", "zero trust review", "セキュリティレビュー", "セキュリティリスクレビュー", "Well-Architected セキュリティ".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run Playwright CLI commands via Bash for test execution, code generation, browser management, reporting, and debugging. Covers the full `npx playwright` surface: test, codegen, install, show-report, show-trace, screenshot, pdf, open, clear-cache, merge-reports, and more. Use when the user asks to run playwright tests, generate test code, install browsers, view a test report or trace, take a page screenshot or PDF, open a URL in a specific browser, clear the playwright cache, merge shard reports, debug tests, or use playwright UI mode. Also covers the guided workflow for turning a codegen recording into a structured test suite with assertions, resilient selectors, and page objects. Trigger phrases include "playwright test", "run playwright", "npx playwright", "codegen", "install browsers", "show report", "show trace", "playwright screenshot", "playwright pdf", "open in chromium", "open in firefox", "open in webkit", "clear playwright cache", "merge reports", "shard tests", "playwright debug", "playwright ui mode", "record test", "run e2e tests with playwright cli", "playwright headed", "playwright retries", "update snapshots", "playwright grep", "list playwright tests", "codegen to test", "generate playwright test", "create test from recording", "turn recording into test", "bootstrap test suite", "record browser test", "generate spec from codegen".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run frontend E2E tests with video evidence. Generates a Playwright test from the scenario CSV and runs it via CLI with video recording. Supports Chrome profile reuse (--chrome-profile) for testing with existing cookies, sessions, and extensions via launchPersistentContext. Generates a test report with video, screenshots, and trace. Does NOT modify application code — only creates documents (markdown, CSV, test scripts). Supports --non-interactive for fork / CI use (fails fast on scenario gaps instead of asking). Use when the user asks to run E2E tests, verify frontend behavior, do end-to-end testing, check UI flows, or test a web app. Trigger phrases include "e2e", "E2E test", "end-to-end test", "e2e testing", "frontend test", "UI test", "playwright test", "browser test", "verify the UI", "test this page".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Senior-level .NET development guidance for architecture, code review, scaffolding, EF Core, ASP.NET Core, Blazor, and MAUI targeting .NET 8 and .NET 10. Provides opinionated best practices, modern C# idioms, security hardening, performance optimization, and testing strategies at a staff/senior engineer level. Trigger patterns (match any variation): .NET / dotnet / dot net / .net / C# / csharp / c sharp / c-sharp / ASP.NET / aspnet / asp.net core / Entity Framework / EF Core / ef core / Blazor / MAUI / maui / NuGet / nuget / Clean Architecture + .NET / CQRS + .NET / DDD + .NET / {review, scaffold, create, design, architect, optimize, migrate} + {C#, .NET, dotnet, csharp} / "dotnet new" / "dotnet build" / "dotnet test" / "dotnet publish" / ".NET best practices" / "C# patterns" / "senior .NET" / ".NET architecture"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage an intermittent test from run history, environment, and failure pattern before naming a cause.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a large deal needs procurement, legal, security, and pricing orchestration: mutual close plans, deal-desk runs, and signature.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.