agentleFS
Sign inStart free
EL4CTEOEL4CTEO/roblox-skills/AGENTS.md

roblox-skills

AGENTS.md92 starsChanged 47 days agoMITView on GitHub

This repository is a skills collection. It is not a Roblox game. - Skills live in skills/<name>/SKILL.md, with optional references/*.md. Follow CONTRIBUTING.md. - Before you finish any change, run python3 scripts/validate.py. It must report 0 errors. If .tools/ is missing, run ./scripts/setup-tools.sh first. - Treat the Roblox engine API reference (Roblox/creator-docs, content/en-us/reference/engine) as the source of truth for API names, deprecations, and limits. Never add an API you haven't verified. - Keep every SKILL.md concise: defaults, decision tables, and short…

The file

We split this AGENTS.md 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:

    Before you finish any change, run python3 scripts/validate.py.

    line 6
  2. Very specific:

    Treat the Roblox engine API reference (Roblox/creator-docs, content/en-us/reference/engine) as the source of truth for API names, …

    line 8
  3. Very specific:

    Keep every SKILL.md concise: defaults, decision tables, and short verified examples.

    line 10
  4. Very specific:

    Don't commit .tools/, .check/, or dist/.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

Instructions for AI agents working in this repository

This repository is a skills collection. It is not a Roblox game.

  • Skills live in skills/<name>/SKILL.md, with optional references/*.md. Follow CONTRIBUTING.md.
  • Before you finish any change, run python3 scripts/validate.py. It must report 0 errors. If .tools/ is missing, run ./scripts/setup-tools.sh first.
  • Treat the Roblox engine API reference (Roblox/creator-docs, content/en-us/reference/engine) as the source of truth for API names, deprecations, and limits. Never add an API you haven't verified.
  • Keep every SKILL.md concise: defaults, decision tables, and short verified examples. Move long material into references/.
  • Luau style: tabs, double quotes, --!strict, services via game:GetService, task.*, and current *Async APIs. StyLua config is in stylua.toml.
  • Don't commit .tools/, .check/, or dist/.

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