roblox-luau-patterns
Skill1 starsChanged 4 months agoMITView on GitHub
Use for Luau metatable classes, inheritance, Promises, coroutines, pcall, module structure, services, and Roblox coding patterns.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- TabooHarmony/roblox-braintheir own version, first seen Sep 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- TabooHarmony/roblox-brain★ 150same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roblox-analyticsSkill
- roblox-animated-modelsSkill
- roblox-animation-vfxSkill
- roblox-architectureSkill
- roblox-assetsSkill
- roblox-audioSkill
- roblox-buildingSkill
- roblox-cameraSkill
- roblox-cloudSkill
- roblox-code-reviewSkill
- roblox-dataSkill
- roblox-debugSkill
- roblox-guiSkill
- roblox-inputSkill
- roblox-lightingSkill
- roblox-localizationSkill
- roblox-luau-coreSkill
- roblox-luau-typesSkill
- roblox-monetizationSkill
- roblox-networkingSkill
- roblox-npc-aiSkill
- roblox-oauthSkill
- roblox-performanceSkill
- roblox-physicsSkill
- roblox-publish-checklistSkill
- roblox-securitySkill
- roblox-server-dataSkill
- roblox-sharp-edgesSkill
- roblox-studio-mcpSkill
- roblox-toolingSkill
- roblox-ui-designSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
OOP (metatables): Use for multiple instances with shared behavior.
- Very specific: line 31
Always set __index. Constructors use ., methods use :.
- Very specific: line 37
Task Library: Always use task.*. wait()/spawn()/delay() are deprecated.
- Very specific: line 56
No connection cleanup → use Trove or manual :Disconnect()
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to Load
Load for Luau patterns: classes with metatables (constructors, methods, inheritance), async control flow (Promises, coroutines, pcall/xpcall), module structure (service pattern, singletons), Roblox-specific patterns (Instance creation, service access, events, task library). For syntax questions, use roblox-luau-core. For type annotations, use roblox-luau-types.
Hand off when: Pure syntax → roblox-luau-core · Type annotations → roblox-luau-types · Networking/data/security → roblox-networking, roblox-data, roblox-security · Performance → roblox-performance.
Full examples and code samples: references/full.md
Quick Reference
OOP (metatables): Use for multiple instances with shared behavior.
local MyClass = {}
MyClass.__index = MyClass
function MyClass.new(...): MyClass -- . for constructors
return setmetatable({...}, MyClass)
end
function MyClass:method() -- : for methods (implicit self)
end
-- Inheritance: setmetatable(Child, { __index = Parent })Always set __index. Constructors use ., methods use :.
Module Services: Singleton pattern for managers. Service.init() wires events; clean up in PlayerRemoving.
Instance Creation: Configure ALL properties, set Parent LAST (prevents replication races).
Task Library: Always use task.*. wait()/spawn()/delay() are deprecated.
Error Handling:
local ok, result = pcall(fn, args...) -- one-shot fallible calls
local ok, result = xpcall(fn, handler) -- custom error handler + tracebackWrap ALL DataStore/HTTP calls. Use a Promise library for async chains when the project already has one; otherwise use task and explicit error handling.
Naming: PascalCase (classes/modules/types), camelCase (vars/functions), UPPER_CASE (constants). Prefix _ for private.
Anti-Patterns:
wait()/spawn()/delay()→task.*- Polling loops → events or Heartbeat
- String
..in loops →table.concat() - Missing
pcallon DataStore/HTTP → silent crash - Trusting client → validate types, ranges, ownership
- Parent before config → replication race
- Props on class table instead of
self→ shared across instances - No connection cleanup → use Trove or manual
:Disconnect()
Libraries: Promise · Trove · Signal · Comm · Component · Concur · TypedRemote (Sleitnick) · ProfileStore · t (runtime checks)
Checklist: __index set · ./: correct · pcall on fallible · cleanup · Parent last · no deprecated · clear API · player data cleaned on leave
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

