Menu
Use when auditing SHAFT agent guidance, host adapters, skill bridges, guidance budgets, Codex config, or Memory setup.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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).
| name | agent-guidance-boundary-guard |
| description | Use when auditing SHAFT agent guidance, host adapters, skill bridges, guidance budgets, Codex config, or Memory setup. |
Use for agent guidance and memory/config surfaces. Keep AGENTS.md canonical and host adapters thin.
.agents/skills/**, the canonical .github/skills/** playbook, .github/skills/README.md, and scripts/ci/agent_guidance_budget.json..agents skill bodies under their configured budget and include agents/openai.yaml with allow_implicit_invocation: true..codex or .memory changes, preserve the restricted Memory MCP setup and avoid routine diary/end-session saves.python3 scripts/ci/validate_agent_setup.py --skip-external; run the full command when network/npm access is stable..github/workflows/refresh-agent-instructions.yml allowlist before widening scope.List guidance surfaces changed, budget/metadata changes, validation command results, and any intentional budget headroom.