turjuman: Skill for Claude Code

Writing great Turjuman documentation

This skill is two things at once: a craft guide for building excellent Mintlify docs, wired to Turjuman's specific repo. The craft rules are distilled from Mintlify's own best-practices pages (cited in the reference files); the wiring tells you exactly which page to touch when code changes.

Turjuman keeps one documentation set in docs/, published with Mintlify. That single source serves four audiences, and good docs serve all four at once:

• Human readers — the rendered site.
• Search engines — page title/description become meta tags; Mintlify handles sitemaps, canonical URLs, and heading semantics automatically.
• AI answer engines — Mintlify auto-generates llms.txt / llms-full.txt and a per-page "copy as Markdown / open in Claude/ChatGPT" menu. Each page is also fetchable as clean Markdown by appending .md to its URL.
• The agents working in this repo — they read these MDX files (and the .md exports) directly.

For an MCP-first, agent-first product, the agent audience is first-class, not an afterthought — but there is still no separate "agent doc." Write each page once so it renders well on the site and flattens cleanly to Markdown. Docs change in the same PR as the code that changed.

The golden rules

1. Frontmatter on every page. title (short, sentence case) and description (a tight, front-loaded summary in active voice that says what the reader accomplishes). The description is the page's search-result snippet, social card, and its llms.txt/agent-facing line — aim for ~130–160 characters; never exceed ~300 and never put a line break in it (Mintlify truncates the llms.txt entry at the first newline or 300 chars). See pages-and-frontmatter.md and discoverability.md.

2. Pick the page's primary job. Diátaxis is the mental model — explanation (a Concept), how-to (a Guide), reference, or tutorial. Lead with one job per page; don't bury an exhaustive option table inside a narrative guide, and don't put a workflow narrative inside a reference. Mintlify (and we) allow blending when a page genuinely serves two needs — a quickstart legitimately mixes tutorial + how-to. Cross-link instead of duplicating whole tables. See doc-types.md.