agentsclimarketplace
Sign in

Whitepaper

Skill prateek11rai/tldraw-canvas-kit/skills/whitepaper

Draft or update a structured whitepaper / design doc / architecture write-up directly on the open tldraw offline canvas — as titled section frames with prose, laid out as a readable long-form document that can embed the canvas's diagrams. Use when the user asks to write a whitepaper, a design doc, an RFC/ADR-style write-up, or an architecture explainer on the canvas (not slides). Produces the same section skeleton and layout every run. When the user wants a maintained, visual design doc, prefer the canvas over a plain markdown file — even if tldraw isn't mentioned.From its SKILL.md

Install
npx -y skills add prateek11rai/tldraw-canvas-kit --skill whitepaper

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 514 tokens by cl100k_base, as published. Nobody here has run it

whitepaper

A structured long-form document on the canvas: a vertical stack of titled section frames with prose, able to reference/embed the architecture and sequence diagrams alongside it. This is the canvas-native alternative to a doc file.

Before you start

  • Read references/shared/bridge.md (bundled with this skill), references/shared/style.md, references/shared/conventions.md.
  • Read ./reference.md — the default section outline + layout.

Target document

Convention: ~/canvas/whitepapers/<topic>.tldraw. Locate via api.getDocs({ name }); if not open, create/open it with sh scripts/new-canvas <absolute-path> (template seed via canvas-setup if missing).

What to build (consistent structure)

A titled section stack (default outline in reference.md): Context → Problem → Goals & Non-goals → Proposed Design → Data Flow → Trade-offs & Alternatives → Risks → Decision / Next steps. Each section = a frame (SECTION_W wide) with a heading (l) and prose body (m), tagged meta:{kckit:'section', order}.

The canvas is programmable — a whitepaper can carry animated or interactive elements (tick-loop animation, React shape widgets), e.g. a live data-flow illustration in the Design section. Pair with the canvas-widget skill when the user wants motion or interactivity.

Workflow

  1. Gather material: the user's input, and — for a doc "on the code" — the relevant source (read the repo; keep it factual, cite files by path). If a codebase-map / architecture-diagram exists on the canvas, plan to embed or reference it in the Design/Data Flow sections.
  2. Generate the section skeleton (idempotent: stable ids sec-<order>, match on meta.order); fill each section's prose. Keep prose tight and specific.
  3. Place/reference diagrams: put an existing architecture/sequence diagram beside or inside the relevant section, or link it by title.
  4. Verify (below).

Verify (once)

getShapes() shows the section frames in order with headings + body text; the stack reads top→bottom without overlap.

Report

Doc id/name, section count, and which sections embed a diagram.

What ships with it: 10 files

78.4 KB alongside SKILL.md, 2 of them executable

assets/

references/

scripts/

Keep looking

Skills are one crate of 326,422. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.