Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

write-docs — Claude Code skill: tldraw SDK documentation

Skill for writing and updating tldraw SDK documentation. Guides you through creating articles, updating existing docs, and following the project's style.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add tldraw/tldraw --skill write-docs -a claude-code
Open on GitHub

What write-docs does

write-docs structures the documentation workflow in apps/docs/content/. The skill outlines a process: start with an overview, add a basic example, expand with details, cover edge cases, then link related docs. It shows how to use MDX components for API references, code highlighting with <FocusLines>, images, and tables.

You begin by understanding your audience and checking related documentation. The skill then guides frontmatter setup for .mdx files and when to reach for components like <Image> or API link syntax. Code examples must work, and all links must resolve correctly.

Available on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.

What it helps with

  • create a new SDK documentation article
  • update existing docs with new code examples and tables
  • format frontmatter and MDX components correctly
  • verify code examples run and API links resolve

Example prompts for the agent

  • Write a guide on creating shapes in tldraw with code samples and a methods table
  • Update the Editor documentation, adding line highlighting to code examples
  • Create a quickstart for new developers following the write-docs structure

How to install write-docs

1Skills CLI (Vercel)

npx skills add tldraw/tldraw --skill write-docs -a claude-code

2Manually: put the files in place

~/.claude/skills/write-docs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/write-docs/

From the same set7

The whole set →

Similar

dart-use-doc-examples flutter Teaches agents to inject external code examples into Dartdoc using the {@example} directive instead of inline blocks. Claude Code CX Codex Cursor +1 6,300installs concept-workflow leonardomso Orchestrates end-to-end JavaScript concept documentation from research and drafting to testing and SEO checks. Useful when writing new guides or rebuilding existing pages. Claude Code CX Codex Cursor +1 322installs resource-curator leonardomso Audits, discovers, and organizes external learning resources for JavaScript concept documentation. It weeds out broken links and obsolete syntax. Claude Code CX Codex Cursor +1 319installs improve-claude-md humanlayer Rewrites your CLAUDE.md file using <important if="condition"> XML blocks. It keeps Claude Code focused on relevant rules without dropping project guidelines. Claude Code CX Codex Cursor +1 2,500installs intended-vs-implemented phuryn Audits the gap between documented architecture and actual code boundaries. Catches missed permission checks and untrusted data exposure in AI-built codebases. Claude Code CX Codex Cursor +1 1,800installs write-concept leonardomso Creates and reviews JavaScript concept pages for 33 JavaScript Concepts. Use it when adding, rewriting, or checking material in /docs/concepts/. Claude Code CX Codex Cursor +1 305installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. Claude Code Claude.ai 414,180installs

Questions about write-docs

How do I install write-docs in Claude Code?

Run npx skills add tldraw/tldraw --skill write-docs -a claude-code. The skill will be available at ~/.claude/skills/write-docs/SKILL.md.

What does the write-docs skill do?

It guides you through writing and updating tldraw SDK documentation. The skill provides a structure for articles, frontmatter rules, examples of MDX components, and a checklist to verify your documentation before publishing.

Where should I write tldraw documentation?

All documentation lives in apps/docs/content/. Main directories are docs/ for SDK articles, getting-started/ for setup guides, examples/ for example docs, and releases/ for release notes.

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor