テスト設計、脆弱性診断、品質保証（1.3万 件）
Audit web pages for accessibility issues, WCAG compliance, and screen reader compatibility. Trigger when the user asks to: check accessibility, run an a11y audit, test WCAG compliance, check screen reader support, audit ARIA attributes, verify keyboard navigation, find accessibility issues, or check for missing alt text or labels.
日本語の概要は準備中です。原文の説明を表示しています。
Write or update the CLI `--help` text and README section for a new or changed rezolus feature (a subcommand, flag, mode, or behavior change), then prove the help is usable by dispatching a fresh subagent that has never seen the code. Use this whenever you add or change how rezolus is invoked — new `rezolus <subcommand>`, new flags/args on an existing mode, renamed options, or changed defaults — and any time the user says the help/README is thin, stale, confusing, or "an agent couldn't figure this out." Treats help text as an interface under test, not prose.
日本語の概要は準備中です。原文の説明を表示しています。
Run the end-to-end viewer smoke test (`tests/viewer_smoke.sh`). Spawns `rezolus view` in upload-only, file, A/B, and proxy modes, exercises the API endpoints, and verifies experiment attach/detach. Use after any change touching `src/viewer/` or before opening a viewer-related PR.
日本語の概要は準備中です。原文の説明を表示しています。
A/B Testing Plan Generator. Creates structured testing roadmaps with prioritized test sequences, duration calculators, sample size requirements, statistical significance thresholds, hypothesis templates, and 90-day testing calendars for Meta, Google, and LinkedIn.
日本語の概要は準備中です。原文の説明を表示しています。
Ad Performance Auditor — analyze existing ad campaigns and identify optimization opportunities
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive product launch planning including GTM strategy, launch checklists, stakeholder communication, beta testing plans, and post-launch analysis. Execute successful product launches with coordinated teams.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing any feature or bugfix, before writing implementation code
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
日本語の概要は準備中です。原文の説明を表示しています。
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Aikido Security integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aikido Security data.
日本語の概要は準備中です。原文の説明を表示しています。
Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites, navigate pages, fill forms, click buttons, take screenshots, share a live browser view, narrate browser actions, extract structured data, run assertions, test web apps, mock network requests, or automate any browser task. Triggers include "open a website", "fill out a form", "take a screenshot", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data", "test this web app", "login to a site", "visual regression test", or any task requiring programmatic web interaction.
日本語の概要は準備中です。原文の説明を表示しています。
Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites — navigating pages, filling forms, clicking buttons, taking screenshots, sharing a live browser view, narrating browser actions, extracting structured data, running assertions, 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", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", "visual regression test", "check for prompt injection", or any task requiring programmatic web interaction.
日本語の概要は準備中です。原文の説明を表示しています。
Design, configure, test, bake, and validate Blender physical effects including Cloth, Soft Body, Rigid Body, collisions, constraints, Fluid, smoke, fire, Dynamic Paint, Ocean, Wave, particles, Boids, force fields, fracture, debris, and secondary effects. Use when gravity, inertia, collision, flexibility, pressure, flow, flocking, emission, or breaking causes the requested result.
日本語の概要は準備中です。原文の説明を表示しています。
Build and validate Blender 5.2 Cycles 3D-to-2D materials using four camera-plane-offset Shader Raycast tests to derive an editable silhouette mask, combined with Cycles-compatible toon or flat shading. Use when a Cycles render needs an in-material outline without Shader to RGB.
日本語の概要は準備中です。原文の説明を表示しています。
Audit Blender scenes and assets for topology, transforms, normals, surface continuity, classified connections, intersections, modifier/node intent, procedural performance, simulation stability, protected-scene changes, and fixed-view visual evidence. Use after every major modeling or simulation stage and before render, bake, export, or claims of completion.
日本語の概要は準備中です。原文の説明を表示しています。
Build, inspect, audit, and refactor Blender Geometry Nodes systems for procedural models, instancing, modular effects, curves, scattering, flocks, data visualization, fields, simulation zones, and node-graph cleanup. Use whenever a Blender task specifically calls for Geometry Nodes, reusable procedural node graphs, node connections/layout, or a scalable procedural asset.
日本語の概要は準備中です。原文の説明を表示しています。
Before removing code that looks redundant, wasteful, or "wrong" based on log observations or code review instinct, grep the test suite for tests whose names describe the exact behavior you're about to remove. A test whose title literally describes the "weird" thing (e.g. "calls play() even when player reports playing", "retries even when first call succeeded", "skips cache even when fresh") is a load-bearing workaround, and the production log you're reacting to is probably the workaround working as designed — not a bug. Use when: (1) Tempted to remove a function call that "looks redundant" based on a production log, (2) About to "simplify" a conditional that seems to always take the same branch, (3) Reviewing code and thinking "why would anyone write this?", (4) A log line shows a state that seems impossible or contradictory (e.g. playing=true but positionMs=0 for seconds), (5) CI surfaces a failing test whose name describes exactly what your fix removed.
日本語の概要は準備中です。原文の説明を表示しています。
Fix "ref.listen can only be used within the build method of a ConsumerWidget" assertion error in Flutter Riverpod 3.x. Use when: (1) ConsumerStatefulWidget crashes with "Failed assertion: line 492 pos 7: 'debugDoingBuild'" in flutter_riverpod consumer.dart, (2) ref.listen is called inside initState, addPostFrameCallback, or any lifecycle method other than build(), (3) All widget tests fail with this assertion from scheduler callback. Applies to flutter_riverpod 3.0+ with ConsumerStatefulWidget.
日本語の概要は準備中です。原文の説明を表示しています。
Fix misleading Flutter/Dart test failures where expected data is empty ([]) or default values instead of the mocked response, caused by stale Mockito generated mocks or missing stubs being silently swallowed by try/catch in provider/repository code. Use when: (1) Test expects non-empty data but gets [], (2) Mock stubs for a method are set up but the code under test returns fallback/empty results, (3) A PR added new methods to a service class and tests that previously passed now fail with misleading "expected X, actual: empty" assertions, (4) "Generated files are out of date" CI error alongside test failures. The root cause is MissingStubError thrown by unstubbed mock methods, caught by production try/catch blocks, causing silent fallback to empty state.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Gorse recommendation engine pods crashing with "user: unknown userid 65532" error. Use when: (1) Gorse master/server/worker pods show CrashLoopBackOff or Error status, (2) Logs show "failed to get user directory" with unknown userid, (3) Running gorse containers with runAsNonRoot security context and custom UID. The gorse images call os.UserHomeDir() at startup which requires the UID to exist in /etc/passwd.
日本語の概要は準備中です。原文の説明を表示しています。
Fix black camera/microphone preview in Flutter macOS apps launched via `flutter run` from a terminal emulator (cmux, iTerm, Terminal.app, VS Code integrated terminal, Cursor, etc.). Use when: (1) camera plugin reports initialized but preview is black with no frames, (2) logs show "initialization completed via timeout" or similar first-frame timeout fallback, (3) AVCaptureSession.startRunning() returns without error but zero frames arrive, (4) the app's Info.plist has NSCameraUsageDescription and entitlements (com.apple.security.device.camera, audio-input) are correctly set, (5) no permission dialog ever appears, (6) same failure mode for microphone. Root cause is macOS TCC attributing camera/mic requests to the *responsible process* (the parent terminal) rather than the Flutter app itself. TCC refuses to prompt because the terminal is hardened-runtime without a camera entitlement, and silently denies. Not a bug in the camera plugin — would reproduce with ANY camera code.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a GitHub issue and produce a structured implementation plan. Fetches issue details, explores the codebase, identifies affected layers (UI, BLoC, Repository, Client), and outputs a step-by-step plan with files to modify, testing strategy, and risk assessment. Works for bugs, features, and tasks. Invoke with /plan.
日本語の概要は準備中です。原文の説明を表示しています。
Fix test failures when adding retry/fallback logic causes mock call count mismatches. Use when: (1) Test fails with "Expected: <1>, Actual: <2>" or similar call count errors after adding retry or fallback mechanisms, (2) MissingStubError appears for methods in new fallback code paths, (3) Mockito verify().called(N) assertions fail after behavior changes. Applies to Dart/Flutter with Mockito, but pattern is universal.
日本語の概要は準備中です。原文の説明を表示しています。