write-example

Create tldraw SDK example files with standardized folder structure and frontmatter metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/arusinova/annarusinova-platform --skill write-example-arusinova
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-example
Source: https://github.com/arusinova/annarusinova-platform/tree/main/.claude/skills/write-example
Command: npx skills add https://github.com/arusinova/annarusinova-platform --skill write-example-arusinova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, scalable SDK examples for the tldraw docs and apps/examples, ensuring consistency and learnability for developers.

Core Features & Use Cases

  • Standardized example structure under apps/examples/src/examples/<example-folder>/ with a README.md containing required metadata and a main example file.
  • Enforced frontmatter metadata format to align with documentation standards, including title, component, category, and keywords.
  • Clear naming, layout, and styling conventions to facilitate quick understanding and reuse of examples.

Quick Start

Follow the described example structure to create a new SDK example in apps/examples.

Frequently Asked Questions about write-example

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a tldraw SDK example for the apps/examples directory?

A tldraw SDK example requires a README.md with frontmatter metadata and a main example file, placed under apps/examples/src/examples/. You can also include optional CSS to support a consistent component layout for your SDK demonstration.

What frontmatter fields are required for tldraw documentation examples?

Required frontmatter fields for tldraw documentation examples include title, component, category, and keywords. This metadata aligns your example with documentation standards to ensure learnability and consistency across the SDK.

What is the best way to ensure consistency across tldraw SDK example files?

The best way to ensure consistency across tldraw SDK example files is to follow a standardized folder layout with a README, a main example file, and optional CSS. Enforcing coding conventions and frontmatter metadata standardizes the structure for developer reuse.

Does my tldraw app example need a separate CSS file?

Your tldraw app example supports an optional CSS file alongside the main example file and README. While not strictly required, including CSS follows the standard component layout conventions for examples in apps/examples.

When do I need to use a standardized layout for tldraw SDK demonstrations?

You need a standardized layout for tldraw SDK demonstrations when creating new examples or app examples in apps/examples. Using a README with metadata and a consistent component layout ensures the examples are clear, scalable, and learnable for developers.