qbcore-framework
QBCore Framework for FiveM - Player management, jobs, gangs, economy, inventory. Use when creating QBCore resources or working with Player object, PlayerData, QBCore functions.
What this skill does
# 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 1. **Always check for nil** — `if Player then ... end` before using Player object 2. **Use QBCore.Functions.GetPlayer** — Standard player retrieval: `local Player = QBCore.Functions.GetPlayer(source)` 3. **Wait for player load** — Check player loaded state on client before accessing PlayerData 4. **Never trust client** — Validate all data server-side, secure your events 5. **Follow QBCore patterns** — Use QBCore functions instead of reinventing (callbacks, notifications, etc.) 6. **Optimize loops** — Cache player objects, use dynamic Wait times, avoid unnecessary calls 7. **Use camelCase** — Follow Lua naming: `myVariable`, local over global 8. **Minimal globals** — Keep variables local unless they need global scope 9. **Use ox_lib for UI** — Prefer ox_lib for menus, dialogs, notifications, progress bars
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.