Agent skill
PicoRuby Development Constraints
Documents memory limits and stdlib constraints for PicoRuby on ESP32. Use this when writing code that will run on ESP32 hardware or designing features for PicoRuby applications.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/picoruby-constraints
SKILL.md
PicoRuby Development Constraints
Memory constraints and stdlib limitations for ESP32 PicoRuby development.
Memory & Runtime Limits
- Total heap: 520KB (strict limit)
- Nesting depth: Avoid deep recursion; prefer iterative solutions
- String handling: Pre-allocate when possible; avoid repeated concatenation
- Arrays: Use fixed-size when known; minimize dynamic growth during tight loops
PicoRuby vs CRuby
| Feature | PicoRuby | CRuby |
|---|---|---|
| Gems | ❌ No bundler/gems | ✅ Full ecosystem |
| stdlib | Minimal (R2P2-ESP32 only) | Complete stdlib |
| Memory | ~520KB heap | GB+ available |
| GC | Simple mark-sweep | Complex generational |
| Float math | ⚠️ Limited precision | Full IEEE 754 |
PicoRuby-safe stdlib
Available:
Array#each,#map,#select(avoid#each_with_indexin tight loops)Hash(simple key-value)String(basic methods, avoid regex for embedded)Time(limited; ESP32 time depends on system clock)File(via R2P2-ESP32 abstraction)
Unavailable:
- Regex (use string matching instead)
- Threads (single-threaded runtime)
- Fiber/Enumerator (complex control flow not needed)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?