TingxiaoDong/FeishuCLassmate - Page 2

robotics-execution-diagnose-no-movement

Use when a robot acknowledges a navigation command but does not move. Follow systematic diagnostics before assuming location name issues.

robotics-execution-verify-navigation-completion

Use when sending navigation commands to a robot. Always verify the robot actually reached the destination by checking position or arrival status, not just command acknowledgment.

skip-exploration-for-known-operations

When the conversation already contains the function name or parameters needed for the requested task, use them directly instead of searching for them.

synthesize-diagnostic-results-into-actionable-hypothesis

Use when multiple diagnostic commands have been run and their outputs need to be combined into a coherent hypothesis and next action.

use-direct-script-invocation

Use when executing Python or Node scripts. Always invoke scripts with the direct `python <file>.py` or `node <file>.js` pattern to avoid preflight validation failures.

verify-directory-structure-before-write

When instructed to write or append to a file, always verify the parent directory exists before attempting the write operation.

verify-fix-completeness-before-testing

Use after making code fixes to verify the change is complete and logically sound before running tests, preventing wasted test cycles on incomplete fixes.

verify-robot-movement-execution

Use after sending any movement command to a robot. Always verify that is_moving becomes true or poll for position change to confirm execution.

verify-robot-navigation-completion-before-reporting-success

After sending a navigation command to the robot, verify the robot has arrived at the destination before confirming success to the user.