npx skills add https://github.com/tldraw/tldraw --skill write-tbp此技能涵盖如何撰写关于 tldraw 实现细节的技术博客文章。
为此主题创建一个资源文件夹:
.claude/skills/write-tbp/assets/<主题>/
├── research.md # 收集的上下文和笔记
└── draft.md # 博客文章草稿
为主题使用简短、短横线分隔的名称(例如 scribbles、arrow-routing、dash-patterns)。
使用探索子代理收集所有相关信息:
Task (subagent_type: Explore, thoroughness: very thorough)
在 tldraw 代码库中查找与 [主题] 相关的所有代码、文档和上下文。
查找:
- packages/editor 和 packages/tldraw 中的实现文件
- packages/tlschema 中的类型定义
- apps/examples 中的相关示例
- apps/docs/content 中的任何现有文档
- 揭示行为的测试
- 解释事物为何如此工作的注释
对于每个相关文件,记录:
- 它的作用
- 关键函数/类
- 有趣的实现细节
- 任何解释"原因"的注释或不明显的决策
输出关于 [主题] 如何工作的全面总结。此文档将由另一个代理阅读。无需过度优化以追求人类可读性。
将研究输出保存到 。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
assets/<主题>/research.md在撰写之前,根据研究回答以下问题:
如果找不到有趣的角度,该主题可能不适合撰写技术博客文章。
按照博客指南结构创建 assets/<主题>/draft.md:
目标字数为 800-1500 字。
根据博客指南清单检查草稿:
修改草稿以解决任何不足之处。
将最终草稿呈现给用户审阅。草稿将保留在 assets/<主题>/draft.md 中,直到用户满意为止,届时用户可以将其移动到适当的位置。
../shared/blog-guide.md。../shared/writing-guide.md。每周安装量
95
代码仓库
GitHub 星标数
46.1K
首次出现
2026年2月1日
安全审计
安装于
opencode90
codex88
github-copilot86
kimi-cli85
gemini-cli85
amp85
This skill covers how to write technical blog posts about tldraw's implementation details.
Create an assets folder for this topic:
.claude/skills/write-tbp/assets/<topic>/
├── research.md # Gathered context and notes
└── draft.md # The blog post draft
Use a short, kebab-case name for the topic (e.g., scribbles, arrow-routing, dash-patterns).
Use an Explore subagent to gather all relevant information:
Task (subagent_type: Explore, thoroughness: very thorough)
Find all code, documentation, and context related to [TOPIC] in the tldraw codebase.
Look for:
- Implementation files in packages/editor and packages/tldraw
- Type definitions in packages/tlschema
- Related examples in apps/examples
- Any existing documentation in apps/docs/content
- Tests that reveal behavior
- Comments explaining why things work the way they do
For each relevant file, note:
- What it does
- Key functions/classes
- Interesting implementation details
- Any "why" comments or non-obvious decisions
Output a comprehensive summary of how [TOPIC] works. This document will be read by another agent. No need to over-optimize for human readability.
Save the research output to assets/<topic>/research.md.
Before writing, answer these questions from the research:
If you can't find an interesting angle, the topic may not be suitable for a technical blog post.
Create assets/<topic>/draft.md following the blog-guide structure:
Target 800-1500 words.
Check the draft against the blog-guide checklist:
Revise the draft to address any gaps.
Present the final draft to the user for review. The draft remains in assets/<topic>/draft.md until the user is satisfied, at which point they can move it to the appropriate location.
../shared/blog-guide.md for voice, tone, and structure.../shared/writing-guide.md for general writing conventions.Weekly Installs
95
Repository
GitHub Stars
46.1K
First Seen
Feb 1, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode90
codex88
github-copilot86
kimi-cli85
gemini-cli85
amp85
新闻稿撰写工具:使用 inference.sh CLI 进行事实核查与专业新闻稿创作
7,700 周安装