qbcore-framework
Develops resources for FiveM using the QBCore Framework. Covers resource creation, Core Object usage, Player management, Callbacks, Events, Items, Jobs, Gangs, Database (oxmysql), and best practices. Use when the user works with FiveM, QBCore, Lua scripts for QBCore servers, or mentions `QBCore.Functions`, `GetCoreObject`, `CitizenID`, or any system of the QBCore Framework.
What this skill does
# QBCore Framework Development
This skill provides guidelines and patterns for developing resources using the **QBCore Framework**.
## 1. Core Object Retrieval
To interact with QBCore, you must retrieve the Core Object. Always cache this in a local variable at the top of your scripts.
**Client & Server:**
```lua
local QBCore = exports['qb-core']:GetCoreObject()
```
## 2. Key Concepts
### Player Data (Server-side)
- Identify players by **Source** temporarily, but use **CitizenID** for database persistence.
- **QBCore.Functions.GetPlayer(source)**: Returns the Player object with all data.
- **Player.PlayerData**: Contains `job`, `gang`, `money`, `items`, `metadata`, etc.
### Callbacks (Server -> Client Data)
- Use **QBCore.Functions.CreateCallback** (Server) to send data to client.
- Use **QBCore.Functions.TriggerCallback** (Client) to request data from server.
- **Rule:** Never trust client data blindly in callbacks. Always validate on server.
### Items
- Use **QBCore.Functions.CreateUseableItem** (Server) to register items.
- Items are defined in `qb-core/shared/items.lua` (or `qb-inventory`).
### Database
- QBCore uses **oxmysql** by default.
- Use `MySQL.query`, `MySQL.insert`, `MySQL.update`, `MySQL.scalar`.
## 3. Standard Resource Structure
```
my-resource/
├── fxmanifest.lua
├── config.lua
├── client/
│ └── main.lua
└── server/
└── main.lua
```
## 4. Best Practices
1. **Cache Core Object:** Do not call `exports['qb-core']:GetCoreObject()` inside loops.
2. **Use Callbacks for Data:** Avoid `TriggerClientEvent` for data retrieval if a callback is cleaner.
3. **Validate Inputs:** Client can send any data. Verify job, money, and ownership on server.
4. **Optimized Loops:** Use dynamic sleep (Wait) based on distance.
5. **Localization:** Use `qb-core/shared/locale.lua` or standard `Lang` object if available.
## 5. Documentation
- Official Docs: https://docs.qbcore.org/
- Github: https://github.com/qbcore-framework/qb-core
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.