Individual skill
robotics-software-principles
Foundational software design principles applied specifically to robotics module development. Use this skill when designing robot software modules, structuring codebases, making architecture decisions, reviewing robotics code, or building reusable robotics libraries. Trigger whenever the user mentions SOLID principles for robots, modular robotics software, clean architecture for robots, dependency injection in robotics, interface design for hardware, real-time design constraints, error handling strategies for robots, configuration management, separation of concerns in perception-planning- control, composability of robot behaviors, or any discussion of software craftsmanship in a robotics context. Also trigger for code reviews of robotics code, refactoring robot software, or designing APIs for robotics libraries.
skills/robotics-software-principles/SKILL.md
Source commit f9bc5467ff9ee3d23f1a1b0b29a649843bb6ad11
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 399
- Repository last updated
- Aug 12, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-coding-assistant Repository topic
- claude-skills Repository topic
- robotics Repository topic
- engineering Derived category
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytesSKILL.mdcore · 30,984 bytes
Read excerpt
# Robotics Software Design Principles
## Why Robotics Software Is Different
Robotics code operates under constraints that most software never faces:
1. **Physical consequences** — A bug doesn't just crash a process, it crashes a robot into a wall
2. **Real-time deadlines** — Missing a 1ms control loop deadline can cause oscillation or damage
3. **Sensor uncertainty** — All inputs are noisy, delayed, and occasionally wrong
4. **Hardware diversity** — Same algorithm must work on 10 different grippers from 5 vendors
5. **Sim-to-real gap** — Code must run identically in simulation and on real hardware
6. **Long-running operation** — Robots run for hours/days; memory leaks and drift matter
7. **Safety criticality** — Some failures must NEVER happen, regardless of software state