Skip to main content

​
Read the docs

  • Start with llms.txt for a page index.
  • Append .md to a page URL for Markdown. For example, read the documenting guide as Markdown.
  • Connect an MCP client to https://docs.tuturuuu.com/mcp and use search_tuturuuu_docs to search public documentation. The endpoint accepts MCP POST requests; a browser GET is not a connectivity test.

​
Repository map

The platform repository separates application entrypoints from shared libraries. Start with these public contribution areas. This is a selected map, excluding paused runtimes and operational tooling.

​
Follow repository conventions

Read the root AGENTS.md and the nearest applicable AGENTS.md before editing. Public contribution conventions include:
  • Use Bun, with the version pinned in the root package.json. Change dependencies through the package manager.
  • Use Conventional Commits and an accepted branch prefix such as docs/, feat/, or fix/.
  • Run focused non-build checks for changed code. Run bun check:changed before pushing; applicable CI checks must pass for the exact commit.
  • For docs, use the local Mintlify wrapper. Run node scripts/local-docs.js validate and node scripts/local-docs.js broken-links from the repository root.
  • Add new docs pages to apps/docs/docs.json and keep documentation aligned with behavior changes.
  • Add user-facing strings to both English and Vietnamese bundles. Update every affected shared UI bundle and run bun i18n:sort.
  • Keep new authored source files at or below 700 lines. Generated and vendored files are excluded.
  • Modify and commit only files intentionally changed for the task.

​
Find product decisions

Product behavior decisions live in the platform/ section of these docs. Start with the platform overview, then read the relevant feature page for defaults, scope, exceptions, and regression evidence.

​
Contribute documentation

Follow Documenting for page structure, navigation, preview, validation, and review.