agentleFS
Sign inStart free
szlayszlay/roblox-base/.claude/skills/roblox-data/SKILL.md

roblox-data

Skill1 starsChanged 4 months agoMITView on GitHub

Use when implementing player data persistence with DataStore, session ownership, schemas, migrations, or save and load flows.

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use UpdateAsync for read-modify-write operations and handle throttling or transient errors.

    line 26
  2. Very specific:

    If using ProfileStore, use StartSessionAsync, Profile.OnSessionEnd, and EndSession as documented.

    line 28
  3. Very specific:

    Use ProfileStore.Mock for Studio tests that must not write live DataStore keys.

    line 29
  4. Very specific:

    Use BindToClose to finish pending work within Roblox's shutdown window.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 data persistence

When to Load

Load when designing player saves, schema migrations, retries, shutdown handling, session ownership, or cross-server state. Use roblox-server-data for ordered leaderboards, messaging, and global world data.

Quick Reference

  • Define a serializable template and a version field before storing player state.
  • Use UpdateAsync for read-modify-write operations and handle throttling or transient errors.
  • Prevent two servers from mutating the same player's profile at once, either with a well-understood wrapper or an equivalent session protocol.
  • If using ProfileStore, use StartSessionAsync, Profile.OnSessionEnd, and EndSession as documented. Do not use its Steal option for normal player loading.
  • Use ProfileStore.Mock for Studio tests that must not write live DataStore keys.
  • Save on meaningful changes and on lifecycle boundaries, but do not assume PlayerRemoving alone is sufficient.
  • Use BindToClose to finish pending work within Roblox's shutdown window.
  • Store primitives, arrays, and dictionaries. Convert Instances, userdata, functions, and cyclic tables first.

Need the details? Load references/full.md for a framework-neutral persistence design.

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.

Check your setup, free