write-docs

tldraw/tldraw · updated Apr 8, 2026

$npx skills add https://github.com/tldraw/tldraw --skill write-docs
0 commentsdiscussion
summary

This skill covers how to write and update tldraw SDK documentation.

skill.md

Write documentation

This skill covers how to write and update tldraw SDK documentation.

Location

All documentation lives in apps/docs/content/. The main categories are:

Directory Purpose
docs/ SDK documentation articles
releases/ Release notes (see write-release-notes skill)
examples/ Example documentation
getting-started/ Quickstart and setup guides

Process

1. Understand the scope

Before writing:

  • Identify the target audience (new users, experienced developers, API reference)
  • Check existing docs that cover related topics
  • Look at relevant examples in apps/examples/
  • Read the API types and comments in the source code

2. Create the file

Create a new .mdx file in the appropriate directory with frontmatter:

---
title: Feature name
status: published
author: steveruizok
date: 3/22/2023
order: 1
keywords:
  - keyword1
  - keyword2
---

3. Write the content

Follow the structure:

  1. Overview — 1-2 paragraphs on what and why
  2. Basic usage — The simplest working example
  3. Details — Deeper explanation with more examples
  4. Edge cases — Advanced patterns, gotchas
  5. Links — Related docs and examples

4. Use MDX components

API links

Use [ClassName](?) or [ClassName#methodName](?) for API references:

The [Editor](?) class has many methods. Use [Editor#createShapes](?) to create shapes.

Code highlighting

Use <FocusLines> to highlight specific lines:

<FocusLines lines={[2,6,10]}>

\`\`\`tsx
import { Tldraw } from 'tldraw'
import { useSyncDemo } from '@tldraw/sync'
\`\`\`

</FocusLines>

Images

<Image
	src="/images/api/events.png"
	alt="A diagram showing an event being sent to the editor."
	title="Caption text here."
/>

Tables for API documentation

Use tables for listing methods, options, or properties:

| Method                   | Description                                    |
| ------------------------ | ---------------------------------------------- |
| [Editor#screenToPage](?) | Convert a point in screen space to page space. |
| [Editor#pageToScreen](?) | Convert a point in page space to screen space. |
| Value     | Description                                          |
| --------- | ---------------------------------------------------- |
| `default` | Sets the initial zoom to 100%.                       |
| `fit-x`   | The x axis will completely fill the viewport bounds. |

5. Verify

Check that:

  • Code examples actually work
  • API links resolve correctly
  • Images have alt text
  • Headings use sentence case
  • No AI tells (see style guide)

References

  • Style guide: See ../shared/docs-guide.md for voice, tone, and formatting conventions.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.564 reviews
  • Kaira Rahman· Dec 28, 2024

    Useful defaults in write-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Sofia Shah· Dec 24, 2024

    Registry listing for write-docs matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noah Abebe· Dec 16, 2024

    I recommend write-docs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Charlotte Sanchez· Nov 19, 2024

    Registry listing for write-docs matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noah Nasser· Nov 15, 2024

    Useful defaults in write-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Sofia Flores· Nov 7, 2024

    write-docs reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Noah Johnson· Oct 26, 2024

    Registry listing for write-docs matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ava Lopez· Oct 10, 2024

    write-docs reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Noah Sanchez· Oct 6, 2024

    I recommend write-docs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Min Huang· Sep 25, 2024

    write-docs has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 64

1 / 7