Use when writing or rewriting any user-facing line on the OpenRig site (site/index.html, site/sections/*.html, site/i18n/**) — headline, lede, section title, card title, button label or note — in any of the three languages, including when the owner says a…
Use when writing, reviewing, or refactoring Slint (.slint) UI files — covers component design, property bindings, callbacks, state management, layouts, accessibility, translations, theming, and integration with Rust backend
Use when writing, editing, or refactoring code in OpenRig — project-specific rules that COMPLEMENT (do not duplicate) xgodev `dev-rules` and `quality-gate` skills
Use when asked for OpenRig's GitHub release download counts — "how many downloads does the latest release have", "download stats for the last N releases", "how many people downloaded v0.1.1" — instead of hand-rolling gh api calls each time.
Use when writing, reviewing, or refactoring Rust code — covers idiomatic patterns, ownership, error handling, performance, testing, generics, type system, and API design best practices
Use when you need to build, package, sign, render, or test OpenRig — running any of its scripts/tools (macOS .dmg, Linux .deb/Orange Pi image, headless Slint PNG render, coverage, the real-hardware test battery) and you need the exact command plus the…