WR

Assists in writing and maintaining technical documentation for tldraw SDKs.

Install

mkdir -p .claude/skills/write-docs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/704" && unzip -o skill.zip -d .claude/skills/write-docs && rm skill.zip

Installs to .claude/skills/write-docs

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
196 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Create MDX documentation files with frontmatter
  • Format API references using tables
  • Highlight code blocks with FocusLines
  • Embed images with alt text and captions
  • Link to SDK classes and methods

How it works

It guides the creation of documentation by enforcing a specific file structure, frontmatter requirements, and the use of project-specific MDX components for code and API references.

Inputs & outputs

You give it
SDK feature or documentation topic
You get back
Formatted MDX documentation file

When to use write-docs

  • Writing documentation for a new SDK feature
  • Updating existing SDK reference docs
  • Formatting technical content for developer consumption
  • Creating API guides

About this skill

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:

DirectoryPurpose
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.

When not to use it

  • Writing documentation outside of apps/docs/content/
  • Using non-standard formatting for API references

Prerequisites

Target SDK feature detailsAccess to apps/docs/content/

Limitations

  • Restricted to tldraw SDK documentation scope
  • Requires specific MDX component usage

How it compares

It ensures technical content follows the specific style guide and component library of the tldraw SDK rather than generic markdown.

Compared to similar skills

write-docs side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
write-docs (this skill)63moNo flagsBeginner
docs-changelog44moNo flagsBeginner
docs-writer43moNo flagsBeginner
technical-docs22moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry