qbcore-framework

Estrellas10

Forks1

Actualizado21 de febrero de 2026 a las 15:09

QBCore Framework for FiveM - Player management, jobs, gangs, economy, inventory. Use when creating QBCore resources or working with Player object, PlayerData, QBCore functions.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

germanfndez

germanfndez/fiveai-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

5 archivos

SKILL.md

readonly

name	qbcore-framework
description	QBCore Framework for FiveM - Player management, jobs, gangs, economy, inventory. Use when creating QBCore resources or working with Player object, PlayerData, QBCore functions.
author	germanfndez
version	1.0.0
mcp-server	projecthub

QBCore Framework Development

Complete guide for developing with QBCore Framework — a comprehensive FiveM roleplay framework providing core functionalities and modules.

When to use

Creating or editing QBCore resources/scripts
Working with player data (Player object, PlayerData)
Implementing jobs, gangs, economy, or inventory systems
Using QBCore client/server functions, callbacks, or events
Questions about QBCore best practices and optimization

How to use

Read individual rule files for detailed explanations and examples:

rules/core-concepts.md — QBCore architecture, PlayerData structure, Player object, framework initialization
rules/client-functions.md — Client-side QBCore functions, notifications, player state management
rules/server-functions.md — Server-side functions, player retrieval, callbacks, usable items
rules/player-methods.md — Player object methods: money, items, jobs, gangs, metadata, accounts
rules/jobs-gangs.md — Job system, gang system, payments, duty status
rules/inventory-items.md — Inventory management, item handling, usable items
rules/events-callbacks.md — QBCore events, server callbacks, client callbacks, event handling
rules/best-practices.md — QBCore coding standards, optimization, security, naming conventions
rules/reference-links.md — Official QBCore documentation links

Key principles

Always check for nil — if Player then ... end before using Player object
Use QBCore.Functions.GetPlayer — Standard player retrieval: local Player = QBCore.Functions.GetPlayer(source)
Wait for player load — Check player loaded state on client before accessing PlayerData
Never trust client — Validate all data server-side, secure your events
Follow QBCore patterns — Use QBCore functions instead of reinventing (callbacks, notifications, etc.)
Optimize loops — Cache player objects, use dynamic Wait times, avoid unnecessary calls
Use camelCase — Follow Lua naming: myVariable, local over global
Minimal globals — Keep variables local unless they need global scope
Use ox_lib for UI — Prefer ox_lib for menus, dialogs, notifications, progress bars

Más de este repositorio

mismo repositorio

fivem-security

germanfndez/fiveai-skills

Best practices and rules for securing FiveM resources against cheaters and exploits. Use this skill when writing or reviewing server-side and client-side code to ensure malicious events, unauthorized entity creations, and client trust issues are prevented. Focuses on strict server authority and safe event handling.

2026-02-2210

esx-framework

germanfndez/fiveai-skills

ESX Legacy Framework for FiveM - Player management, jobs, economy, inventory, weapons. Use when creating ESX resources or working with xPlayer, PlayerData, ESX functions.

2026-02-2110

fivem-basics

germanfndez/fiveai-skills

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.

2026-02-2110

fivem-nui

germanfndez/fiveai-skills

FiveM NUI (New User Interface) development for creating graphical elements and user interfaces. Use when creating or editing NUI interfaces, HTML/CSS/JS for FiveM, or handling NUI callbacks.

2026-02-2110

fivemanage

germanfndez/fiveai-skills

Fivemanage SDK for FiveM — installation, screenshots (takeImage, takeServerImage, uploadImage), and centralized logs (Log, Info/Warn/Error). Use when integrating Fivemanage, capturing player screenshots, uploading images, or sending logs to the Fivemanage dashboard.

2026-02-2110

lua-basics

germanfndez/fiveai-skills

Effective Lua programming for FiveM - functions, tables, variables, conditionals, error handling. Use when writing or reviewing Lua code for FiveM resources.

2026-02-2110

QBCore Framework Development

Complete guide for developing with QBCore Framework — a comprehensive FiveM roleplay framework providing core functionalities and modules.

When to use

Creating or editing QBCore resources/scripts

Working with player data (Player object, PlayerData)

Implementing jobs, gangs, economy, or inventory systems

Using QBCore client/server functions, callbacks, or events

Questions about QBCore best practices and optimization

How to use

Read individual rule files for detailed explanations and examples:

rules/core-concepts.md — QBCore architecture, PlayerData structure, Player object, framework initialization

rules/client-functions.md — Client-side QBCore functions, notifications, player state management

rules/server-functions.md — Server-side functions, player retrieval, callbacks, usable items

rules/player-methods.md — Player object methods: money, items, jobs, gangs, metadata, accounts

rules/jobs-gangs.md — Job system, gang system, payments, duty status

rules/inventory-items.md — Inventory management, item handling, usable items

rules/events-callbacks.md — QBCore events, server callbacks, client callbacks, event handling

rules/best-practices.md — QBCore coding standards, optimization, security, naming conventions

rules/reference-links.md — Official QBCore documentation links

Key principles

Always check for nil — if Player then ... end before using Player object

Use QBCore.Functions.GetPlayer — Standard player retrieval: local Player = QBCore.Functions.GetPlayer(source)

Wait for player load — Check player loaded state on client before accessing PlayerData

Never trust client — Validate all data server-side, secure your events

Follow QBCore patterns — Use QBCore functions instead of reinventing (callbacks, notifications, etc.)

Optimize loops — Cache player objects, use dynamic Wait times, avoid unnecessary calls

Use camelCase — Follow Lua naming: myVariable, local over global

Minimal globals — Keep variables local unless they need global scope

Use ox_lib for UI — Prefer ox_lib for menus, dialogs, notifications, progress bars