First-time setup: Customize this file for your project. Prompt the user to customize this file for their project.
For Mintlify product knowledge (components, configuration, writing standards),
install the Mintlify skill: npx skills add https://mintlify.com/docs
Documentation project instructions
About this project
- This is a documentation site built on Mintlify
- Pages are MDX files with YAML frontmatter
- Configuration lives in
docs.json - Run
mint devto preview locally - Run
mint broken-linksto check links
Terminology
- Use “script” for the FiveM resource sold on 9AM
- Use “edition” when comparing escrow and open source variants
- Use “customer” or “server owner” for the buyer
- Use “server key” when referring to Cfx.re delivery and licensing
- Use “framework” for ESX, QBCore, and QBox compatibility
- Use “studio” for the 9AM team behind the products
Style preferences
- Use active voice and second person (“you”)
- Keep sentences concise - one idea per sentence
- Use sentence case for headings
- Bold for UI elements: Click Settings
- Code formatting for file names, commands, paths, and code references
- Prefer direct language for setup, compatibility, and support steps
- Explain escrow vs open source tradeoffs clearly
- Write for FiveM server owners and buyers first
- Use product keywords naturally for SEO, without stuffing
- Do not use vague SaaS or licensing-platform language when a FiveM store term is clearer
Content boundaries
- Document customer-facing product details, installation flows, compatibility, purchasing, updates, and support expectations
- Document what buyers need to know about Keymaster delivery, escrow, open source, and framework support
- Do not document private source code, internal business operations, unreleased features, or anti-abuse internals
- Do not publish sensitive implementation details that are not already public on 9am.dev