Tokio

Use this skill to write long-form Markdown guides for Topcoat. It covers where documentation sources belong, how to structure explanations from basic to advanced, and how to keep prose plain, concise, and easier to maintain as implementations change.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning where a guide and its links should live
• Structuring a guide from basic to advanced use
• Editing Markdown for clear, maintainable prose

Use this skill when building procedural macros for Topcoat in Rust. It explains how to preserve parsed syntax in AST nodes, separate parsing from meaning, and keep macro entry points focused on parsing input, expanding valid code, and reporting errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing AST nodes for a procedural macro
• Parsing custom syntax while preserving tokens
• Organizing a macro entry point and code generation

Use this skill to write concise commit messages in the Topcoat project’s Conventional Commits format. It helps choose a change type and scope, describe the update clearly, and mark breaking changes so release notes and version bumps can be based on commit history.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a commit message for a code change
• Choosing a commit type and scope
• Marking a breaking change and migration note

Use this skill to prepare a Topcoat pull request from the full branch diff. It guides you to write a Conventional Commits title and a concise body covering the change, verification performed, and an AI-use disclaimer when an agent creates the PR.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a pull request title from the net branch change
• Summarizing a diff and the checks performed
• Adding the required AI-use disclosure to a PR

Use this skill to check Topcoat changes locally before committing or opening a pull request. It runs the project’s Rust formatting, lint, test, and documentation commands, plus browser project checks when relevant, so problems can be caught before review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a Rust change before committing
• Validating browser project changes
• Building project documentation locally

Apply the project’s Rust conventions when editing code or documentation. The guidance covers module and type organization, workspace dependency declarations, plain English documentation, and tests that check meaningful behavior rather than fixed text.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organizing Rust modules and implementations
• Writing or revising Rust documentation
• Reviewing whether a test protects real behavior

Prepare Toasty design documents under `docs/dev/design/` using the required template, audience, and concise writing conventions. The skill guides document structure and illustrative Rust examples, and outlines the proposal and roadmap steps for non-trivial features.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a Toasty feature design document
• Editing an existing design proposal
• Explaining a feature to users and driver implementors

Prepare concise Git commit messages for the Toasty project by first checking its authoritative commit guide. The skill focuses on describing what changed and why, using the project's required format, types, scopes, and breaking-change notation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a commit subject and body
• Checking allowed commit types and scopes
• Marking a breaking change correctly

Write or edit Toasty documentation, design notes, READMEs, pull request descriptions, issues, and commit bodies using the project's prose conventions. It favors direct, factual language, concrete examples, active voice, and descriptions of current behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Editing a README or project documentation
• Writing an issue or pull request description
• Making design notes more direct and concrete

Write clear Toasty issues by choosing the right template for a bug report or feature proposal and filling in its required fields. It helps describe observed behavior, reproduction steps, proposed APIs, and alternatives in concise, factual language.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reporting a bug with steps and a reproducer
• Proposing a feature or public API change
• Choosing and completing an issue template

Prepare a Toasty pull request by reviewing the full change against its base branch and drafting a concise title and body from the net diff. It also covers the required template, rendered links for major Markdown changes, and label handling.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a pull request title and body
• Summarizing changes across several commits
• Preparing a pull request for a Markdown document