القائمة
Keep LawnBerry Pi maintainer documentation synchronized with implementation. Use when runtime behavior, supported hardware scope, subsystem maturity, immediate focus, two-week plan, release notes, or callable interfaces have changed and docs must be updated in the same pass.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for LawnBerry Pi simulation vs real-hardware validation. Covers SIM_MODE selection, .env and config checks, simulation-safe test-first workflow, hardware preflight expectations, and avoiding false claims that local success proves on-device behavior.
Use for improving LawnBerry Pi AI result quality without breaking the existing backend contract. Covers ai_service review, model artifact or rule improvement, conservative evaluation, performance notes, and avoiding premature accelerator-specific churn.
Review regression-sensitive LawnBerry Pi manual control and camera paths: RoboHAT USB handoff, watchdog feeding, motor authorization, joystick responsiveness, MJPEG and snapshot fallback, camera ownership, and stream backpressure handling.
Use when returning to LawnBerry Pi after time away, starting substantial maintenance, or needing a fast project re-entry workflow. Covers docs to read first, runtime ports, hardware baseline, simulation vs hardware mode, important files by task, and validation planning.
Use when a LawnBerry Pi task spans re-entry, specialist routing, implementation, documentation sync, and validation. Covers choosing the right specialist workflow and sequencing investigation, changes, doc updates, and test planning.
Use for LawnBerry Pi mission persistence and recovery work. Covers what mission state should survive restart, safe restart semantics, paused vs running recovery behavior, lifecycle validation, and persistence-backed tests.
| name | maintainer-doc-sync |
| description | Keep LawnBerry Pi maintainer documentation synchronized with implementation. Use when runtime behavior, supported hardware scope, subsystem maturity, immediate focus, two-week plan, release notes, or callable interfaces have changed and docs must be updated in the same pass. |
| argument-hint | What implementation change needs maintainer doc synchronization? |
| user-invocable | true |
This skill keeps the maintainer-facing documentation honest after implementation changes.
Use this skill when a change affects any of the following:
backend/src/**, frontend/src/**, scripts/**, or .specify/scripts/**docs/developer-toolkit.mddocs/RELEASE_NOTES.mddocs/code_structure_overview.mdREADME.md, docs/OPERATIONS.md, or docs/TESTING.md when runtime behavior changedspec/hardware.yaml when supported hardware claims changeddocs/code_structure_overview.md and verify signatures against source.scripts/check_docs_drift.sh may print fatal: depth 0 is not a positive number while still exiting 0; trust the exit status.spec/hardware.yamldocs/code_structure_overview.md matches callable signatures after structural changes