agentleFS
szlayszlay/roblox-base/.claude/skills/roblox-architecture/SKILL.md

roblox-architecture

Skill1 starsChanged 4 months agoMITView on GitHub

Use when starting or refactoring a Roblox project, choosing service or module structure, or making client-server architecture decisions.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    Put authoritative game rules in ServerScriptService.

    line 21
  2. Very specific:

    Put only genuinely shared modules, remotes, and public assets in ReplicatedStorage.

    line 22
  3. Very specific:

    Treat LocalScript code and replicated contents as observable and modifiable by the player.

    line 23
  4. Distinctive:

    Use one small bootstrap on each side, then initialize feature modules in an explicit order.

    line 25
  5. Distinctive:

    Keep UI and input controllers on the client.

    line 26

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

roblox architecture

When to Load

Load when deciding where code and assets belong, introducing service or controller modules, or changing the client/server boundary.

Quick Reference

  • Put authoritative game rules in ServerScriptService; keep server-only templates and secrets in ServerStorage.
  • Put only genuinely shared modules, remotes, and public assets in ReplicatedStorage.
  • Treat LocalScript code and replicated contents as observable and modifiable by the player.
  • Give each module one owner and one clear contract. Use signals or a coordinator for cross-system communication instead of circular require calls.
  • Use one small bootstrap on each side, then initialize feature modules in an explicit order.
  • Keep UI and input controllers on the client. Keep rewards, inventory, combat outcomes, and persistence on the server.

Need the details? Load references/full.md for layouts, lifecycle code, and boundary checks.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.