FiveM development. Step by step.
Your project context. Ready for the next task.
Frameworks, naming conventions and project decisions do not change with every question. Personal knowledge, a project prefix and custom instructions help retain that context. Notes and work boards support organisation when enabled for your account.
What you can do
Useful context is brief, specific and current. It describes your actual project rather than a general wish list.
Open notes and project contextRecord recurring requirements
Document your framework version, inventory and database resources, and rules for file and event names. A project prefix and custom instructions can bring recurring requirements together. Make clear which rules apply to every task and which belong to one resource.
Separate knowledge from open tasks
Stable information belongs in project context. An unresolved idea, bug report or planned test belongs in a note or work board. This stops assumptions from quietly becoming fixed requirements. Record when a decision was last checked as well.
Refresh context before major changes
When switching framework or inventory, review saved instructions and knowledge for obsolete names and interfaces. Still provide relevant files and exceptions in the individual request. Saved context helps the workflow; it does not replace the current resource version.
For your next task
Useful project context
Our server uses the QBCore version documented in the project. New events use the vl_garage prefix. Money and ownership checks belong on the server. Existing database columns change only when explicitly requested. Open UI ideas are tracked separately on the work board.
Check before moving on
- Keep versions and dependencies current
- Separate facts, ideas and tasks
- Do not store passwords or private player data
- Mention relevant exceptions in each request
Scope and limitations
Features and permissions vary by account and plan. Personal knowledge and additional organisation features are available according to the current plan comparison. Check which content others can access before sharing it.
Current plans and conditions →Common questions
Does saved knowledge replace uploading files?
No. Knowledge records rules and context. Analysing a specific resource still requires its current code and a relevant task description.
Does every plan include all organisation features?
No. Check the plan comparison and your account for enabled knowledge, notes and team features.
Your project. Your next step.
Describe your idea or upload an existing resource. Continue working on the source code and test the result on your server.
Open AI chat →