andrian-syh

best-practices

Framework-agnostic Roblox/Luau coding standards. Use when writing, implementing, or refactoring any Luau code (Script, LocalScript, ModuleScript) in a Roblox project, or when the user asks to keep best practices in mind as standing guidance — enforces the VARIABLES/FUNCTIONS/INITIALIZATION layout, naming, performance, memory, networking, and security rules regardless of framework, folder structure, or genre. Two modes: Default (apply these conventions as-is) and Adaptive (study the project's existing style first, confirm, then apply). Adapts to community libraries (ProfileStore, Packet, Trove, Knit, Fusion, ...) and honors supervision levels (!ask / !bal / !go). Not for reviewing or auditing code that already exists (the code-review skill owns that), not for finding the cause of a reported symptom when no file has been named yet (the diagnose skill owns that), not for sync toolchains, Studio MCP, or playtests (the studio-ops skill owns those), non-Roblox Lua, or game design with no Luau to write.

code-review

Reviews and audits existing Roblox/Luau code instead of writing it. Use when the user asks to review a file, diff, or pull request, to audit a place or system, to score architectural health or maturity, to find leaks, exploits, or data-loss risks in code that already exists, or asks how good or how safe their current implementation is. Reports one severity per finding (Blocker / Correctness / Advisory) behind a confidence gate, and scores a whole project 1-5 across security, lifecycle, performance, and replication. Not for writing or refactoring code — hand that to the best-practices skill; not for chasing a reported symptom down to its cause when no file has been named yet — that is the diagnose skill; not for Studio tooling, sync, or playtest questions - that is the studio-ops skill.

diagnose

Diagnoses a reported Roblox symptom down to its cause before anything is changed. Use when the user reports that something is broken, wrong, missing, duplicated, intermittent, or works in Studio but not in a live game - leaderstats resetting, players falling through the map, a shop granting free items, a server dying after a while, an event firing twice - and no file has been named yet. Classifies the symptom, asks which side owns the state and whether a client could have caused it, narrows the surface, reproduces, and confirms the cause before handing the fix over. Not for judging code that was handed to it (the code-review skill owns that), not for writing the fix (the best-practices skill owns that), and not for sync toolchains or driving Studio tools (the studio-ops skill owns those).

AI & Automation Listed

studio-ops

Operating a Roblox project's tooling safely: Studio MCP connections, filesystem sync with Rojo, Argon, Script Sync, or Azul, and proving a change actually works in the running engine. Use when the user asks why their edits are being overwritten, how to set up or diagnose a sync toolchain, what a Studio MCP tool will do before it runs, how to playtest or verify a fix, or how to test replication and multi-client behaviour. Governs how the agent drives its tools, not how Luau is written. Not for authoring Luau — that is the best-practices skill; not for judging code that already exists — that is the code-review skill; not for working out why a reported symptom happens — that is the diagnose skill, which calls on this one to run the probe.

roblox-best-practices

Framework-agnostic Roblox/Luau coding standards. Use when writing, reviewing, or refactoring any Luau code (Script, LocalScript, ModuleScript) in a Roblox project, or when the user asks to keep best practices in mind as standing guidance — enforces the VARIABLES/FUNCTIONS/INITIALIZATION layout, naming, performance, memory, networking, and security rules regardless of framework, folder structure, or genre. Two modes: Default (apply these conventions as-is) and Adaptive (study the project's existing style first, confirm, then apply). Adapts to community libraries (ProfileStore, Packet, Trove, Knit, Fusion, ...) and honors supervision levels (!ask / !bal / !go). Not for non-Roblox Lua, Studio UI or asset questions that do not touch code, or game design discussion with no Luau to write or review.

7 Updated 4 weeks ago