القائمة
Use when auditing Maven module boundaries, BOM wiring, legacy coordinates, bundled examples, or clean consumer fixtures.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | modular-boundary-auditor |
| description | Use when auditing Maven module boundaries, BOM wiring, legacy coordinates, bundled examples, or clean consumer fixtures. |
Use for module boundary and packaging drift across Maven reactor modules, examples, BOM, legacy coordinate, and clean consumer fixtures.
shaft-bom, legacy-shaft-engine, bundled examples, and tools/modularization/consumer-fixtures/** before changing checks.shaft-engine; fix the owning module, BOM, or fixture instead.python3 scripts/ci/validate_reactor_versions.py when versions or inter-module coordinates change.python3 scripts/ci/validate_modular_documentation.py, python3 scripts/ci/validate_maven_publication.py, and the relevant tests/scripts/test_*_boundary.py.python3 scripts/ci/validate_shaft_pilot_release.py and affected clean-fixture mvn --batch-mode -f ... verify "-Dshaft.version=..." checks.State the boundary touched, owning module, BOM/fixture/example impact, checks run, and any untested fixture matrix.
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).