fivem-basics
FiveM resource structure, fxmanifest, client/server scripting, events. Use when creating or editing FiveM resources or Lua scripts, or when the user asks how FiveM works.
Don’t want to manage skills yourself? Get the full app.
Skill contents (includes SKILL.md and any other files)
# FiveM basics
Best practices for FiveM — resources, manifest, client/server, events. Use this skill whenever you are dealing with FiveM code to obtain domain-specific knowledge.
## When to use
- User asks how FiveM resources or scripts work.
- Editing or creating `fxmanifest.lua`, `client_*.lua`, or `server.lua`.
- Questions about client/server, events, or exports.
- Need to look up natives or detailed docs → point to https://docs.fivem.net/natives/ and https://docs.fivem.net/docs/.
## How to use
Read individual rule files for detailed explanations and examples:
- **rules/structure.md** — Resource structure and organization: scope, client/server separation, logical grouping, naming conventions.
- **rules/fxmanifest.md** — Resource manifest (fxmanifest.lua): fx_version, game, client_scripts, server_script, files, dependencies.
- **rules/client-server.md** — Client vs server scripts, shared code, communication patterns.
- **rules/events.md** — Events in Lua: RegisterNetEvent, TriggerServerEvent, TriggerClientEvent, naming conventions, security.
- **rules/exports.md** — Defining and consuming exports between resources.
- **rules/debugging.md** — Server vs client (F8) logs; when to ask the user for F8 logs if there's no server-side error.
- **rules/optimization.md** — Lua/FiveM optimization: locals, loops, natives (PlayerPedId, vector distance), state bags, security, readability, folder structure.
- **rules/reference-links.md** — Official docs and natives reference.