rommapp

Internationalization for the RomM frontend. Use whenever adding, renaming, or removing any user-visible string / translation key under frontend/src/locales/. Covers the en_US-is-source rule, the requirement to add every new key to ALL locale directories in…

Theming, design tokens, colors, and visual language in the RomM v2 frontend. Use when styling v2 components, picking colors, adding/using CSS variables, working with light/dark themes, or whenever you'd reach for a hex/rgba literal. Covers the token pipeline…

Building or modifying components in the RomM v2 frontend (frontend/src/). Use when creating/editing v2 primitives (R* components in src/lib/), shared composites, or feature composites. Covers the three-tier model, file/folder conventions, SFC structure,…

Work through the Greptile and Copilot review comments on a RomM PR. Triage each finding (valid, introduced by this PR, consistent with what the PR intends), fix the ones that hold up, then reply on every thread with the fix or the reason for declining and…

Universal input (mouse, touch, keyboard, gamepad) and responsive/universal-viewport layout in the RomM v2 frontend. Use when adding interactive v2 components, focus management, spatial navigation, gamepad/keyboard handling, modality-gated focus rings,…

Cross-cutting feature patterns for the RomM v2 frontend: error/snackbar handling, loading & skeleton states, real-time Socket.IO updates, UI state persistence (URL vs localStorage vs ephemeral), pagination/infinite scroll, forms & validation, permissions…

Read Greptile's synthesized knowledge base for this repository through the Greptile MCP (list_knowledge_bases, list_knowledge_base_documents, get_knowledge_base_document, search_knowledge_base). Use whenever you want context about the codebase, such as how a…

The before-review and before-handoff pass for RomM, covering both stacks. First shapes the code the checks can't see: comment and docstring discipline (the single most-corrected thing in this repo), duplicated constants/types/getters, imprecise names, loose…

Dual-screen development reference. Load this before implementing any dual-screen feature.

Menu system patterns for building settings screens, modals, and preference items. Use BEFORE building any menu UI to ensure consistency with input handling, visibility, and footer hints.

Verify RetroAchievements hardcore compliance and RA Connect wire shapes. Use before any release touching RA, AND whenever editing RAApi, RAModels, RetroAchievementsRepository or any dorequest endpoint. Checks save state blocking, cheat blocking, rewind…

Code quality standards and patterns for Argosy. Use BEFORE writing or modifying code to ensure consistency with project patterns.

Turn a rough goal into a fully-scoped, edge-case-complete plan safe to hand off for execution. Use when the user says /investigate "<goal>" or wants to scope wide-spanning work before building. Interview-first; routes through Argosy's coupling map so no…

Drive the running app on an Android emulator and visually verify UI/UX by capturing screenshots and reading them back. Use to confirm a screen renders, navigate a flow (e.g. first-run/quickstart), check dual-modality input, or catch visual regressions. Knows…

Drive the connected debug build on a real device - install, fetch logs, send gamepad/keyboard input, grab screenshots. Use whenever testing a change on-device, reproducing a bug, or verifying UI behavior so the adb workflow is one approved command instead of…

Argosy design tokens system. Use BEFORE adding colors, dimensions, typography, motion specs, or component defaults to ensure they go in tokens.json (the single source of truth), not as hardcoded literals in Composables.

RomM's house style for docs pages, covering what the general humanizer doesn't. Use whenever you write, edit or review prose under docs/ in this repo, including new pages, release-notes passes and PR review. Covers restated context, "RomM" as a filler…

Run the vendored humanizer and the docs-style house rules over the documentation pages a change adds or edits, as the last step before opening a PR. Rewrites prose only, leaving headings, front matter, snippet partials and MkDocs syntax untouched.

Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language,…

Run local checks before pushing code or cutting a release. Use before commits, releases, or when validating code quality. Catches issues before they reach the remote.

Create RomMP releases with version bumps, APK builds, and GitHub releases. Use when asked to release, bump version, cut a beta, or prepare for deployment.