テスト・セキュリティのスキル

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

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

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

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

Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.

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

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

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

QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.

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

Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"

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

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

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

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

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

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

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

Skill for the Tests area of paddock. 44 symbols across 6 files.

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

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

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

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

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

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

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

Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).

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

Test, fold or refute hypotheses beside the knowledge record, and reconcile records across branches. Use when open or check say hypotheses wait or an id is CONTESTED, when a write was refused into a hypothesis, before merging a branch whose record changed, and when a pull request's dry run or remeasure is red. Covers consolidate --dry-run, the fold, --refute, --from, same and distinct at the fold, and remeasure.

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

[Workflow] Build or extend idempotent, environment-gated development/QC seeders with realistic data, change review and verified tests.

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

[Documentation] Use when a workflow step or the user asks for canonical feature specs and test scenarios: author, audit, amend, tests and sync. discovery maps overlaps; clarify confirms decisions; index derives navigation/ERD.

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

[Dev Data] Use when a workflow step or the user asks for idempotent QC happy-path seeders using public commands. --mode=review audits seeder conventions read-only.

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

[Process] Use when a developer needs to understand and judge scoped work: a change set, subsystem, decision, plan or concept — flow, rationale, trade-offs, testing. Bugs: investigate --mode=debug; one feature's code flow: investigate.

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

[Workflow] Use when E2E tests need to be written, updated or fixed: resolves the scope, authors tests only when needed, then verifies them through the configured runner in a bounded fix/retest loop.

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

[Testing] Use when a workflow step or the user asks for a local test run and read-only results summary.

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

[Workflow] Audit project architecture, scalability and production readiness without changing code; deliver one consolidated health report.

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

[Documentation] Use when generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. Generator only, never authors business content. generate|audit|sync.

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