القائمة
Use for LawnBerry Pi runtime contract work that starts with drift audit and ends with aligned docs, config, scripts, service definitions, and targeted validation. Covers ports, startup behavior, proxies, systemd units, and maintainer-facing runtime guidance.
التثبيت باستخدام 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.
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.
| name | runtime-audit-and-fix |
| description | Use for LawnBerry Pi runtime contract work that starts with drift audit and ends with aligned docs, config, scripts, service definitions, and targeted validation. Covers ports, startup behavior, proxies, systemd units, and maintainer-facing runtime guidance. |
| argument-hint | What runtime contract or startup surface should be audited and aligned? |
| user-invocable | true |
This skill coordinates a full runtime-contract pass: audit first, fix only where evidence shows drift, and verify the updated contract at the end.
docs/developer-toolkit.md and maintainer-reentry.runtime-contract-audit skill or equivalent drift investigation first.backend/src/main.pyfrontend/vite.config.tsfrontend/server.mjsfrontend/playwright.config.tssystemd/docs/OPERATIONS.md, docs/TESTING.md, README.mdmaintainer-doc-sync if runtime behavior, maintainer guidance, or callable interfaces changed.