AnotherSava

Update stale documentation and comments to match current code

Tag a new version, push to trigger CI, monitor the build, and verify the GitHub release

Extract and persist conversation learnings before context loss. TRIGGER when: user runs /reflect, or before /clear or compaction.

Guidelines for creating and updating Claude Code skills. TRIGGER when: writing a new SKILL.md, modifying an existing skill, or the user asks about skill conventions.

Analyzes changes and generates Conventional Commit messages

Arrange a project's README and GitHub Pages documentation into a consistent user-first layout: short README that links out, just-the-docs Jekyll site with a user-facing index, one page per user-facing feature (split into child pages when long), and a developer guide with technical sub-pages. TRIGGER when: setting up docs/ for a new project, adding a GitHub Pages site, writing or restructuring a README that will link to GH Pages, adding a new user-facing feature page, or asked to align docs with this project or bga-assistant. DO NOT TRIGGER when: editing unrelated docs outside docs/, working on a project that already has an incompatible docs framework (Docusaurus, MkDocs, VitePress, etc.).

Create or update the data flow architecture document (docs/pages/data-flow.md).

Create an implementation plan for a new feature, refactor, or fix. Guides an interactive design discussion and produces a structured plan document.

Guides users through distributing Tauri applications on Windows, including creating MSI and NSIS installers, customizing installer behavior, configuring WebView2 installation modes, and submitting apps to the Microsoft Store.

Assists with managing Tauri application resources including app icons setup and generation, embedding static files and assets, accessing bundled resources at runtime, and implementing thread-safe state management patterns.

Creates and edits Tauri capability JSON files, configures plugin permissions and per-window access control, and sets up platform-specific security boundaries. Use when working with capability.json, Tauri allowlist, IPC permissions, plugin access, Tauri security config, or per-window access control.

Helps users create and initialize new Tauri v2 projects for building cross-platform desktop and mobile applications. Covers system prerequisites and setup requirements for macOS, Windows, and Linux. Guides through project creation using create-tauri-app or manual Tauri CLI initialization. Explains project directory structure and configuration files. Supports vanilla JavaScript, TypeScript, React, Vue, Svelte, Angular, SolidJS, and Rust-based frontends. Use when the user wants to start a new Tauri project, set up Tauri v2, or asks about Tauri project initialization and prerequisites.

Guides the user through implementing Tauri system tray functionality, including tray icon setup, tray menu creation, handling tray events, and updating the tray at runtime in the notification area.

Build and debug Tauri desktop applications using the Rust backend, webview frontend, IPC commands/events, and capability-based security model. Use when scaffolding a Tauri project, defining Rust commands, configuring tauri.conf.json, setting up capabilities and permissions, or debugging cross-platform desktop app issues.

Scaffolds Tauri v2 plugins with `tauri plugin new`, implements Rust commands with desktop/mobile split, configures plugin permissions in TOML, writes Kotlin and Swift native bindings for Android and iOS. Use when creating or extending Tauri plugins, configuring plugin permissions, writing platform-specific native code, or building Tauri plugins for mobile platforms.

Guides developers through testing Tauri applications including unit testing with mock runtime, mocking Tauri APIs, WebDriver end-to-end testing with Selenium and WebdriverIO, and CI integration with GitHub Actions. Use when the user asks about testing Tauri apps, writing tests for Tauri commands, setting up e2e testing for desktop apps, or configuring CI pipelines for Tauri projects.

Debug a game state discrepancy reported by the user. Extracts archive, analyzes all pipeline stages, creates a failing regression test with correct expectations, fixes the logic, and verifies the fix.

Run regression tests for the Innovation tracker extension.