2,984 件 ・ 関連度順
概要と使いどころ
Use when a component library needs a workshop — one story per concept, JSDoc summaries the manifest can carry, stories run as tests, and an opt-in MCP channel that replaces guessing with querying.
日本語の概要は準備中です。原文の説明を表示しています。
Use BEFORE writing any test — enumerate cases per behavior (happy / boundary / error / abuse), prioritize by likelihood × impact, cross-check via subagent — even if the user just says 'add tests'.
日本語の概要は準備中です。原文の説明を表示しています。
Writes or edits PHP code — controllers, classes, type hints, SOLID refactors, modern idioms — even without naming PHP. NOT for writing tests (use pest-testing) or explaining PHP concepts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a Playwright suite — locator strategy, Page Object boundaries, fixture composition, flake-prevention architecture, CI-vs-local split — even on 'design our E2E tests'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.
日本語の概要は準備中です。原文の説明を表示しています。
When scoring a roadmap, PR review, ADR, or ticket for completeness — risk, tests, migration, maintainability. Dispatched by /refine-ticket, /adr-create, /review-changes; never auto-gates.
日本語の概要は準備中です。原文の説明を表示しています。
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'.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill when writing, reviewing, or interpreting behavioral accessibility automation — tests that manipulate a rendered page (resizing the viewport, pressing real keys, capturing and comparing screenshots) rather than only inspecting static markup or a single computed accessibility tree. Covers Reflow risk (SC 1.4.10) and Focus Visible risk (SC 2.4.7) checks. Absolutely always report indicator results separately from confirmed failures. Under no circumstances treat a clean behavioral scan as WCAG conformance, or collapse `cantTell`/test-error/indicator outcomes into a single pass/fail signal.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when you need to run tests locally and analyze the summary report.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the E2E testing workflow to generate, update, or maintain Playwright/E2E tests. Pick mode with --source={changes|recording|update-ui}.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code alignment.
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when you need to verify integration tests pass after writing and reviewing them.
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when you need to generate or review integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
[Implementation] Use when you need to start coding & testing an existing plan. Flags: --approval=off (auto/trust mode, no approval gate), --tests=off (skip the test step), --parallel={auto|on|off} (default off — sequential; --parallel/=on opts in to parallel sub-agent waves; =auto fans out only when the plan declares PAR/SEQ tags and write sets).
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when generating, updating, or maintaining E2E tests from recordings, specs, or code changes.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need to review artifact quality (PBI, user story, test spec, design spec) before handoff. Supports --type={pbi|story|spec-tests|design}.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing, fixing, or verifying a pull request. Focus on correctness regressions, missing tests, permission mistakes, unsafe behavior, and minimal fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
日本語の概要は準備中です。原文の説明を表示しています。