Map SHAFT_ENGINE before broad search.
Use for shaft-mcp manifests, fixtures, installers, Dockerfiles, tool schemas, workflows, or transport behavior.
Use for SHAFT UI design/review/validation across tools, reports, plugin UI, or public guide; include UX and evidence rules.
Use for SHAFT module wiring, POMs, BOM, legacy coordinates, examples, or consumer fixtures.
Use for SHAFT UI design, redesign, optimization, review, visual QA, UX copy, accessibility, responsive behavior, reports, core tools, and public guide work.
Use when AGENTS.md, CLAUDE.md, .agents, .github skills/instructions, .codex, or .memory guidance surfaces change.
Use when Allure or Extent report generation, artifacts, summaries, upload actions, failure extraction, or report paths change.
Use when public SHAFT APIs, config, behavior, README links, release text, or docs routing may need user-guide synchronization.