القائمة
Use when planning or verifying user-guide updates for public SHAFT behavior, docs links, release text, or API/config changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | public-behavior-docs-synchronizer |
| description | Use when planning or verifying user-guide updates for public SHAFT behavior, docs links, release text, or API/config changes. |
Use for user-visible SHAFT behavior changes. Keep docs work separate from code unless the task explicitly asks for both.
C:\Users\Mohab\IdeaProjects\shafthq.github.io with targeted rg; update only guide pages affected by the behavior change.README.md, .github/RELEASE_BODY_TEMPLATE.md, and legacy-shaft-engine/pom.xml. Run python3 scripts/ci/validate_modular_documentation.py when those links or examples are touched.python3 scripts/ci/validate_documentation_boundaries.py; for guidance changes also run python3 scripts/ci/validate_agent_setup.py.List the public surface, guide files searched or changed, validation results, and docs PR/blocker.