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.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install bash0c7-picotorokko-picoruby-constraints
Repository
Skill path: .claude/skills/picoruby-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.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: bash0C7.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install PicoRuby Development Constraints into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/bash0C7/picotorokko before adding PicoRuby Development Constraints to shared team environments
- Use PicoRuby Development Constraints for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: PicoRuby Development Constraints description: 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. --- # 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_index` in 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)