> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sportix.vn/llms.txt
> Use this file to discover all available pages before exploring further.

# CLAUDE

# Mintlify documentation

## Sportix defaults (quan trọng)

* Ngôn ngữ mặc định cho toàn bộ tài liệu: **Tiếng Việt**.
* Đối tượng đọc chính: người dùng cơ bản (player, coach), không phải developer.
* Ưu tiên hướng dẫn thao tác theo từng bước, ít thuật ngữ kỹ thuật.
* Không đưa API endpoint/JSON contract vào docs người dùng cơ bản trừ khi có yêu cầu riêng.
* Luôn bắt đầu bằng bối cảnh sản phẩm Sportix trước khi vào thao tác chi tiết.

## Global settings baseline

* Luôn kiểm tra `docs.json` trước khi viết nội dung mới.
* Duy trì nhận diện thương hiệu Sportix nhất quán: logo, font, màu, ngôn ngữ.
* Các thông tin chung cần xuất hiện rõ trong docs:
  * Giới thiệu ngắn về Sportix
  * Kênh liên hệ
  * Email hỗ trợ
  * Liên kết chính (website, blog)

## Working relationship

* You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
* ALWAYS ask for clarification rather than making assumptions
* NEVER lie, guess, or make up anything

## Project context

* Format: MDX files with YAML frontmatter
* Config: docs.json for navigation, theme, settings
* Components: Mintlify components

## Content strategy

* Document just enough for user success - not too much, not too little
* Prioritize accuracy and usability
* Make content evergreen when possible
* Search for existing content before adding anything new. Avoid duplication unless it is done for a strategic reason
* Check existing patterns for consistency
* Start by making the smallest reasonable changes

## docs.json

* Refer to the [docs.json schema](https://mintlify.com/docs.json) when building the docs.json file and site navigation

## Frontmatter requirements for pages

* title: Clear, descriptive page title
* description: Concise summary for SEO/navigation

## Writing standards

* Second-person voice ("you")
* Prerequisites at start of procedural content
* Test all code examples before publishing
* Match style and formatting of existing pages
* Include both basic and advanced use cases
* Language tags on all code blocks
* Alt text on all images
* Relative paths for internal links

## Git workflow

* NEVER use --no-verify when committing
* Ask how to handle uncommitted changes before starting
* Create a new branch when no clear branch exists for changes
* Commit frequently throughout development
* NEVER skip or disable pre-commit hooks

## Do not

* Skip frontmatter on any MDX file
* Use absolute URLs for internal links
* Include untested code examples
* Make assumptions - always ask for clarification


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.