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).
Ten distilled expert domains for working on SHAFT_ENGINE (Java test-automation framework). Load the ONE matching chapter from references/ before deep work on: Selenium/WebDriver BiDi or the recorder (selenium-bidi), Allure report internals (allure-internals), Appium/mobile toolchains (appium-mobile), Maven Central release engineering (maven-release), TestNG/JUnit listeners and forked-JVM properties (testng-lifecycle), IntelliJ Platform plugin dev (intellij-plugin), MCP protocol engineering (mcp-protocol), GitHub Actions CI forensics (ci-forensics), flaky-test stabilization and wait strategies (wait-strategies), or locator design and self-healing (locator-healing). Read only the chapter you need; each is self-contained and grounded in real SHAFT incidents.
Use when implementing any feature or bugfix, before writing implementation code