roo_windows-specific addendum for code authoring and validation. Use with the local embedded-cpp-code-authoring instruction when editing public APIs, adding tests, documenting behavior, running Bazel tests, or checking example-sketch builds.
Install
mkdir -p .claude/skills/roo-windows-code-authoring && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14952" && unzip -o skill.zip -d .claude/skills/roo-windows-code-authoring && rm skill.zipInstalls to .claude/skills/roo-windows-code-authoring
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
roo_windows-specific addendum for code authoring and validation. Use with the local embedded-cpp-code-authoring instruction when editing public APIs, adding tests, documenting behavior, running Bazel tests, or checking example-sketch builds.241 chars✓ has a “when” trigger
About this skill
roo_windows Code Authoring
Use this skill for roo_windows-specific guidance on top of the local
embedded-cpp-code-authoring instruction.
Related instructions: roo-windows-widget-authoring instruction
roo_windows-Specific Guidance
- When a change affects widget behavior, layout, painting, or input handling, also use the widget authoring guidance in roo-windows-widget-authoring instruction.
- Use the repository validation commands below instead of generic build or test guesses.
Validation Commands
roo_windowsis often used from a parent workspace underlib/roo_windows. Run tests from there, for example:(cd lib/roo_windows; bazel test //:overlay_test)- Prefer the narrowest relevant Bazel target first, then widen only if needed.
- To verify that an example sketch compiles under emulation, copy the sketch to
roo_windows/emulation/main.cpp, then run:(cd lib/roo_windows/emulation; bazel build :main)
Checklist
- Widget-related changes also follow the widget authoring instruction when relevant.
- Validation uses the narrowest relevant Bazel target first.
- Example-sketch compile coverage uses the emulation
:mainbuild when relevant.