randroidRoute requests to the focused Randroid development workflows and explain which capability to use. Use when the user asks what Randroid skills are available, invokes the Randroid namespace without naming a workflow, or needs help choosing among loop execution, PR feedback handling, VibeReview playtes
randroid-address-pr-commentsAddress actionable pull-request review feedback end to end by locating the PR, resolving each current comment, implementing focused fixes, verifying them, and replying with evidence. Use when the user asks to handle PR comments, requested changes, unresolved review threads, or reviewer feedback.
randroid-clean-slopDiagnose generic visual and copy patterns in existing interfaces, games, and 3D assets through actual screenshots or renders. Use when asked to de-slop, avoid cookie-cutter design, or refine an existing game's visual identity. Does not implement missing gameplay or replace a modeling workflow.
randroid-game-feelImprove a game's core interaction, responsiveness, feedback, and playable iteration. Use when a game feels like an app or menu, the user asks for game feel or juice, a prototype needs its first playable loop, or game-not-app rules need installing. Preserve the chosen genre, including turn-based, car
randroid-loopRun a bounded research or implementation loop with persistent Dots task tracking and an explicitly selected git workflow. Use when the user asks for an autonomous multi-iteration development loop, research loop, implementation loop, or work-until-complete cycle. Do not use for an ordinary one-pass c
randroid-vibereviewRun VibeReview browser-game playtests, capture screenshot and browser-state evidence, and feed findings into Spiral-HTML review ledgers. Use when the user asks to playtest a browser game, capture VibeReview evidence, inspect an existing VibeReview session, or turn playtest findings into durable foll