A reference guide for GitHub issue standards in the tldraw repository. Use this when you need to know how to format issue titles (sentence case, no type prefixes, imperative mood for features), apply the right issue type via GraphQL, or follow their triage workflow. It covers the full lifecycle: writing clear bug reports with reproduction steps, structuring feature requests around problem statements, cleaning up messy titles, and knowing which labels to use sparingly versus which are automated. The standards are opinionated but practical, like insisting on "Arrow bindings break with rotated shapes" instead of "Bug: arrow bug". Helpful if you're maintaining a repo with similar quality standards or contributing to tldraw itself.
npx -y skills add tldraw/tldraw --skill write-issue --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
github/awesome-copilot
microsoft/win-dev-skills
github/awesome-copilot
github/awesome-copilot