القائمة
Audit LawnBerry Pi runtime contract drift across ports, startup behavior, systemd units, frontend proxies, docs, scripts, and config. Use for port mismatches, startup confusion, README vs runtime checks, and source-of-truth comparison work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | runtime-contract-audit |
| description | Audit LawnBerry Pi runtime contract drift across ports, startup behavior, systemd units, frontend proxies, docs, scripts, and config. Use for port mismatches, startup confusion, README vs runtime checks, and source-of-truth comparison work. |
| argument-hint | What runtime surface or port/startup behavior should be audited? |
| user-invocable | true |
This skill performs a focused drift audit for ports, startup wiring, proxy behavior, and maintainer-facing runtime instructions.
Read and compare these first:
docs/developer-toolkit.mdREADME.mddocs/OPERATIONS.mddocs/TESTING.mdfrontend/vite.config.tsfrontend/server.mjsfrontend/playwright.config.tssystemd/backend/src/main.pyscripts//apibackend/src/main.py, service units, and active frontend config as stronger truth than prose docs8081, 3000, and 4173 unless intentionally changing the contract everywhereUse 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.