Menu
Always use this skill before opening an issue in the Toasty repository
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Always use this skill before authoring a commit message in the Toasty repository
Always use this skill before authoring or editing a Toasty design document under docs/dev/design/
Always use this skill when running tests against dynamodb (DDB)
Always use this skill before opening a pull request in the Toasty repository
Author or edit any prose for the Toasty project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following project writing conventions
Bring the Toasty user guide and rustdoc back in sync with recent code changes by walking the git log for user-observable behavior and updating affected docs
| name | issue |
| description | Always use this skill before opening an issue in the Toasty repository |
Load this skill before filing any issue in this project.
An issue is project documentation. Follow the conventions from the
prose skill: be fact-focused, direct,
and concrete. No buzzwords, no fluff, no dramatic terms. State what
happened or what is being proposed, not how important it is.
Maintainers reading the issue already know Toasty and Rust. Keep the prose high-signal: lead with the bug or proposal, then the reproducer or API sketch, then the alternatives. Skip restated background and throat-clearing. A maintainer should grasp the problem in seconds, not paragraphs.
Issue templates live in
.github/ISSUE_TEMPLATE/:
bug_report.yml —
incorrect or unexpected behavior. Asks what you did, what you expected,
and what happened instead; the affected driver(s); the Toasty version;
and a reproducer.feature_proposal.yml —
new features, public-API changes, or anything that affects driver
implementations. Requires the problem, proposed solution,
alternatives considered, and a scope estimate.Read the template before writing. Fill in every field it asks for; don't drop sections or leave placeholders. If a field does not apply, say so explicitly rather than leaving it blank.
Report what you observed, not why you think it happened. A bug report has five parts:
crates/toasty-driver-integration-suite/src/tests/ is ideal; a small
standalone snippet works too. This is the single most useful thing in
the report.Leave out root-cause analysis. Diagnosing the bug is the maintainer's job, and a guess at the cause sends triage down the wrong path. Describe the behavior; the reproducer shows the rest.
Describe the problem before the solution. Name who is affected — Toasty users, driver implementors, or both. Sketch the user-facing API concretely; vague proposals are hard to discuss. List the alternatives you considered and why you discarded them.
Non-trivial features follow the path in
CONTRIBUTING.md: discuss in an issue,
land a roadmap entry and design doc, then land the implementation.
Do not apply labels when creating the issue. The templates set the
initial C-* label; maintainers triage and add the rest. See
docs/dev/labels.md.