Addendum for roo_windows specific code authoring, validation, and testing.
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.Key capabilities
- →Provide `roo_windows`-specific guidance for code authoring
- →Apply widget authoring guidance when changes affect widget behavior
- →Run Bazel tests from the parent workspace
- →Prefer the narrowest relevant Bazel target for validation
- →Verify example sketch compilation under emulation
- →Use repository validation commands instead of generic build or test guesses
How it works
The skill provides specific guidance and validation commands for `roo_windows` code authoring, including widget behavior, Bazel testing, and example sketch compilation.
Inputs & outputs
When to use roo-windows-code-authoring
- →Edit public APIs
- →Run Bazel tests
- →Validate widget behavior
- →Test sketch builds
About this skill
roo_windows Code Authoring
Use this skill for roo_windows-specific guidance on top of the local
general C++ 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)- To verify that an example sketch compiles under emulation, build its
hierarchical target from the main workspace, for example:
(cd lib/roo_windows; bazel build //examples/simple/navigation:navigation) - Use
roo_windows/emulationonly as a scratch workspace for local or multi-file experiments.
Checklist
- Widget-related changes also follow the widget authoring instruction when relevant.
- Example-sketch compile coverage uses its main-workspace hierarchical target.
When not to use it
- →When generic build or test commands are sufficient
- →When changes do not affect widget behavior, layout, painting, or input handling
- →When the task is not related to `roo_windows`-specific code authoring
Limitations
- →The skill is specific to `roo_windows` codebase
- →It requires running tests from a parent workspace under `lib/roo_windows`
- →Example sketch compilation requires copying to `roo_windows/emulation/main.cpp`
How it compares
This skill offers specialized guidance and validation commands tailored for the `roo_windows` codebase, unlike generic C++ code authoring instructions.
Compared to similar skills
roo-windows-code-authoring side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| roo-windows-code-authoring (this skill) | 0 | 4mo | No flags | Intermediate |
| add-new-jit-ee-api | 1 | 8mo | No flags | Advanced |
| implement-feature | 1 | 9mo | Review | Advanced |
| feature | 0 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
add-new-jit-ee-api
dotnet
Add a new API to the JIT-VM (aka JIT-EE) interface in the codebase.
implement-feature
tddworks
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
feature
PABERTHIER
>
add-policy
microsoft
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
feature
tanjed
>
unreal-engine-cpp-pro
sickn33
Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.