tldraw
Writing and maintaining GitHub issues for the tldraw repository. Use when creating new issues, editing issue titles/bodies, triaging issues, or cleaning up issue metadata (types, labels).
bunx add-skill tldraw/tldraw -s write-issueLoadingβ¦
Standards for issues in tldraw/tldraw.
Bug:, Feature:, [Bug], etc.Arrow bindings break with rotated shapesAdd padding option to zoomToFit methodPinch zoom resets selection on SafariBug: arrow bug[Feature] Add new feature (prefix, vague)Not working (vague)Bug: X β XAdd Padding Option β Add padding optionAdding feature X β Add feature XProblem β [Describe the actual problem]Set via the GitHub GraphQL API after creating the issue (the --type flag is not reliably supported):
| Type | Use for |
|---|---|
Bug | Something isn't working as expected |
Feature | New capability or improvement |
Example | Request for a new SDK example |
Task | Internal task or chore |
Use sparingly (1-2 per issue) for metadata, not categorization.
| Label | Use for |
|---|---|
good first issue | Well-scoped issues for newcomers |
More Info Needed | Requires additional information |
sdk | Affects the tldraw SDK |
dotcom | Related to tldraw.com |
a11y | Accessibility |
performance | Performance improvement |
api | API change |
keep, stale, update-snapshots, publish-packages, major, minor, skip-release, deploy triggers
More Info Needed label and comment if details missinggood first issue if appropriatekeep label if should remain openUse when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.