メニュー
Use when auditing shaft-mcp tool manifests, client fixtures, installers, containers, startup, or local transport contracts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mcp-transport-contract-auditor |
| description | Use when auditing shaft-mcp tool manifests, client fixtures, installers, containers, startup, or local transport contracts. |
Use for shaft-mcp contract changes across tool schemas, fixtures, startup, installers, containers, and transports.
shaft-mcp/src/test/resources/fixtures/mcp-tool-manifest.json and shaft-mcp/src/test/resources/fixtures/shaft-pilot/mcp/** when the public tool contract changes.python3 scripts/ci/validate_shaft_mcp_configuration.py. Also run python3 scripts/ci/validate_modular_documentation.py for client fixture or public docs-link changes.shaft-mcp tests with -DheadlessExecution=true and -Dgpg.skip.shaft-mcp, copy runtime dependencies to shaft-mcp/target/dependency, then run python3 scripts/ci/validate_shaft_mcp_transports.py.python3 scripts/ci/verify_shaft_mcp_installer_release.py or state why it is not applicable.List contract files touched, transport/client impact, checks run, and remaining fixture or installer risk.
Use when analyzing SHAFT Allure results, Doctor reports, trace evidence, healer output, flaky locator/wait/assertion failures, retries, or test-fix recommendations.
Use when creating, reviewing, refactoring, repairing, or generating SHAFT web/mobile locators, smart locators, ARIA locators, XPath/CSS replacements, or codegen element identifiers.
Use when recording browser, Playwright, mobile, Appium Inspector, or user-performed flows into SHAFT tests with MCP Capture, replay, code blocks, or codegen insertion.
Use when reviewing, previewing, applying, guardrail-checking, or verifying generated SHAFT Java before or after inserting it into a repository, especially the coding-partner diff/apply/verify loop from IntelliJ.
Use when writing, reviewing, or repairing SHAFT Java tests, page objects, API tests, mobile tests, CLI/DB tests, assertions, waits, or TestNG/JUnit/Cucumber scenarios.
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).