Inspect repository session replay and verify configured MetaHarness field memory boundaries before reusing outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
2,547 件 ・ 関連度順
概要と使いどころ
Inspect repository session replay and verify configured MetaHarness field memory boundaries before reusing outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Captures, masks, compares, and updates screenshot baselines for web and mobile suites, with per-region thresholds and a reviewed-diff rule for every baseline change. Use when a screenshot assertion fails, a baseline needs updating, or visual checks are being added; not for deciding what to verify.
日本語の概要は準備中です。原文の説明を表示しています。
Drives iOS/Android mobile devices via Appium MCP. Runs a preflight, picks local emulator/simulator/USB or a device cloud, captures screenshots/page source into a named evidence dir. Use for verifying mobile bugs, E2E tests, and navigating real device clouds (LambdaTest/BrowserStack).
日本語の概要は準備中です。原文の説明を表示しています。
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
日本語の概要は準備中です。原文の説明を表示しています。
Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce Red-Team verification and adversarial protocol audit. Use only when verifying completion, performing self-scans, or checking protocol violations; do not activate for ordinary implementation, configuration, or unit-test requests.
日本語の概要は準備中です。原文の説明を表示しています。
Long-running iterative cycle — one entry, seven modes (debug|improve|planex|review|security|defensive|ui). Shared archaeology/audit → fix → verify → generalize → discover → persist skeleton with mode-specific dimensions. User-invoked campaign entry; single-step fixes route via /maestro-next
日本語の概要は準備中です。原文の説明を表示しています。
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when the runtime supports them.
日本語の概要は準備中です。原文の説明を表示しています。
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when Amp makes them available.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
日本語の概要は準備中です。原文の説明を表示しています。
Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
日本語の概要は準備中です。原文の説明を表示しています。
Runs plugin health checks (venv packages, skill registration, and album slug collisions). Use when the user asks to check plugin health, verify setup, or troubleshoot missing skills.
日本語の概要は準備中です。原文の説明を表示しています。
Performs quality control, citation validation, and fact-checking before human review. Use after research is complete to verify all sources and claims before production.
日本語の概要は準備中です。原文の説明を表示しています。
Runs automated tests to validate plugin integrity across 14 categories. Use before creating PRs, after making changes to skills or templates, or to verify plugin health.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Verify or select a SageMaker execution role before creating models, endpoints, or training jobs. Use when a role ARN is missing or IAM access fails; inspect existing roles before proposing role creation.
日本語の概要は準備中です。原文の説明を表示しています。
Select and verify the current region-specific serving container URI for a SageMaker model deployment. Use after the deployment pathway is chosen and before endpoint code; never infer an image URI from memory.
日本語の概要は準備中です。原文の説明を表示しています。
Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.
日本語の概要は準備中です。原文の説明を表示しています。
Safely update an existing oh-my-design installation in place and verify it afterward. Use when the user asks to update, upgrade, refresh, reinstall, or check whether their OmD skills, agents, hooks, or reference catalog are current.
日本語の概要は準備中です。原文の説明を表示しています。
Safely update an existing oh-my-design installation in place and verify it afterward. Use when the user asks to update, upgrade, refresh, reinstall, or check whether their OmD skills, agents, hooks, or reference catalog are current.
日本語の概要は準備中です。原文の説明を表示しています。
Run Open Claude Code (OCC) for coding tasks and verify its CLI installation. Use when asked to use OCC, select its provider, or perform a bounded coding task through its CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
日本語の概要は準備中です。原文の説明を表示しています。
Completion Check: Verify Infrastructure Is Wired
日本語の概要は準備中です。原文の説明を表示しています。