Randroids-Dojo

Randroid command namespace. Use when the user asks for available Randroid slash commands or invokes /randroid directly. Includes /randroid:loop, /randroid:address-pr-comments, /randroid:vibereview, and /randroid:clean-slop.

HTML-first bootstrap and audit of the structural-discipline scaffold (GDD tree, coverage ledger, progress log, open questions, followups, playtest gate) that takes a vision into a delivered system through small iterations whose state lives in git, not the agent's head. Same methodology as spiral; ledgers, rules, and contracts are written in HTML rather than Markdown. Slash commands /spiral-html-init and /spiral-html-audit live under commands/.

Bootstrap and audit the structural-discipline scaffold (GDD tree, coverage ledger, progress log, open questions, followups, playtest gate) that takes a vision into a delivered system through small iterations whose state lives in git, not the agent's head. Each cycle returns to the same artifacts and finds them advanced. Pairs with /randroid:loop and task-tracking-dots. Use when bootstrapping a new project or auditing an existing one. Slash commands /spiral, /spiral-init, /spiral-audit live under commands/.

Add @randroids-dojo/vibekit (https://github.com/Randroids-Dojo/VibeKit) as a dependency and look up per-module usage patterns. Optional companion to the spiral skill; replaceable with a different shared-library skill if a project prefers another component source. Slash commands /vibekit-add and /vibekit-cookbook live under commands/.

Manages task tracking with the HTML-backed Dots fork from Randroids-Dojo/dots-html. Use when tracking work items across sessions with dot-html CLI files stored as .html documents.

Interact with the SlipBox semantic knowledge engine and read notes from PrivateBox. Use when capturing ideas, searching notes, browsing your knowledge graph, or running semantic analysis passes (link, cluster, tension).

Manages Dots task tracking with the dot CLI, dependencies, and completion reasons. Use when tracking work items across sessions or coordinating task dependencies.

Develop, test, and automate Unreal Engine 5.x projects (WIP). Covers PlayUnreal automation, Remote Control API, Automation Driver, and CI-friendly E2E flows.

Unreal Engine 5 C++ coding conventions, naming standards, and architectural patterns

Pipeline for generating, validating, and importing 3D models, textures, and audio assets

Game design reference for 3D Frogger arcade gameplay, mechanics, and progression

Structured protocol for team retrospectives that produce concrete process improvements

Unreal Engine 5 build system, testing framework, and CI/CD patterns

Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 for GDScript unit tests and PlayGodot for game automation and E2E testing. Supports web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.

Autonomous development loop with research and implementation modes