菜单
Helps with FTC robot development workflow including building, deploying, and debugging. Use when connecting to robot, troubleshooting ADB, building code, deploying to Control Hub, viewing logs, or controlling OpModes from the command line.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
DECODE 2025-2026 FTC game reference. Use when programming autonomous routines, calculating scores, understanding field layout, or working with game-specific coordinates.
FTC Dashboard by ACME Robotics - web-based dashboard for real-time telemetry visualization, live configuration variables, field overlay drawing, and camera streaming. Use when teams ask about dashboard setup, telemetry graphing, @Config variables, canvas drawing on field, or streaming camera to browser.
Helps integrate Limelight 3A vision system for FTC robots. Use when working with AprilTag detection, MegaTag2 localization, color tracking, or shooter auto-aim.
Helps write FTC robot code using the NextFTC command-based framework. Use when creating OpModes, commands, subsystems, gamepad bindings, or integrating with Pedro Pathing.
Helps use the Panels dashboard for FTC robot debugging, configuration, and telemetry. Use when adding telemetry, creating graphs, making configurable variables, or setting up the Panels dashboard.
Helps write autonomous and teleop code using Pedro Pathing library. Use when creating paths, building autonomous routines, setting up path following, working with Follower, PathChain, BezierLine, or heading interpolation.
| name | robot-dev |
| description | Helps with FTC robot development workflow including building, deploying, and debugging. Use when connecting to robot, troubleshooting ADB, building code, deploying to Control Hub, viewing logs, or controlling OpModes from the command line. |
| license | MIT |
| compatibility | Claude Code, Codex CLI, VS Code Copilot, Cursor |
| metadata | {"author":"ncssm-robotics","version":"1.1.0","category":"tools"} |
Commands and guidance for the FTC robot development workflow. Designed to help rookies get up and running quickly.
/doctor
This checks if ADB is installed and helps you install it if needed.
/connect
Connects to your robot via WiFi (default) or USB.
/build # Compile your code
/deploy # Build and install to robot
/log # View robot logs
/log --errors # View only errors
/opmodes # List available OpModes
/init TeleOp # Initialize an OpMode
/start # Start the OpMode
/stop # Stop the OpMode
| Command | Description |
|---|---|
/doctor | Check environment setup (ADB, connection) |
/connect | Connect to robot via WiFi or USB |
/build | Compile robot code |
/deploy | Build and deploy to robot |
/log | View filtered robot logs |
/opmodes | List available OpModes |
/init | Initialize an OpMode |
/start | Start the initialized OpMode |
/stop | Stop the running OpMode |
TEAMNUMBER-RC)/connect/connect --usbSee TROUBLESHOOTING.md for solutions to:
See ADB_SETUP.md for platform-specific ADB installation instructions.
When connected, the status line shows:
🤖 Connected (12.4V) │ TeleOp Test [INIT] │ 192.168.43.1
See HUD.md for configuration options.
# BAD - Jump straight to connecting
/connect # "ADB not found" error
# GOOD - Check environment first
/doctor # Identifies missing dependencies
/connect # Now it works
# BAD - Deploy after build fails
/build # Shows errors, you ignore them
/deploy # Deploys old working code, not your changes!
# GOOD - Fix errors before deploying
/build # Fix any errors shown
/build # Verify clean build
/deploy # Now your changes are deployed
# BAD - Deploy fails silently
/deploy # "No device connected" error
# GOOD - Ensure connection first
/connect # Establish connection
/deploy # Deploy succeeds
# BAD - Overwhelmed by system noise
/log # Thousands of unrelated messages
# GOOD - Filter to what matters
/log --errors # Only error messages
/log --tag=MyOp # Only your OpMode's logs