メニュー
Use for coordinating a LawnBerry Pi hardening pass across high-risk subsystems such as navigation, mission recovery, manual control/camera, and AI quality. Covers routing to the right hardening skill, sequencing focused changes, and keeping validation and docs aligned.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
| name | subsystem-hardening-orchestration |
| description | Use for coordinating a LawnBerry Pi hardening pass across high-risk subsystems such as navigation, mission recovery, manual control/camera, and AI quality. Covers routing to the right hardening skill, sequencing focused changes, and keeping validation and docs aligned. |
| argument-hint | Which subsystem should be hardened: navigation, mission recovery, control/camera, or AI? |
| user-invocable | true |
This skill routes hardening work to the right specialized pass so risk-heavy subsystems get focused treatment instead of generic maintenance.
Choose the leading pass based on the subsystem:
navigation-hardening-passmission-recovery-passcontrol-camera-regression-reviewai-model-quality-passmaintainer-reentry.maintainer-doc-sync if maturity, limitations, or interfaces changed.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.
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.
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.
