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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Always use this skill to verify a change locally before committing or opening a pull request in the Topcoat repository
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Keep this file in sync with CI workflows.
Run these by default:
cargo +nightly fmt --all # nightly is required, CI checks formatting with it
cargo topcoat fmt # formats Topcoat macros inside source files (ignore Leptos errors)
cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
cargo test --workspace --all-features
RUSTDOCFLAGS="--cfg docsrs -Dwarnings" cargo +nightly doc --workspace --all-features --no-deps --locked
Only on user request:
# per-feature lint, catches feature combos that do not build (needs cargo-hack)
cargo hack clippy --workspace --each-feature --exclude-features stage-icons --no-dev-deps -- -D warnings
# unused dependencies, which CI fails on (needs cargo-udeps on nightly)
cargo +nightly udeps --workspace --all-targets --all-features --locked
For changes in crates/topcoat-runtime/browser or crates/topcoat-cli/browser, run these commands from the affected project's directory. For shared code in crates/topcoat-core/browser, run them in both projects. yarn lint checks formatting, imports, and lint rules, including the shared code.
yarn install --frozen-lockfile
yarn lint
yarn build
yarn test
The runtime and CLI embed their prebuilt dist/index.js; the runtime's coherence crate also embeds dist/coherence.js. CI rebuilds these files and rejects drift. Include regenerated bundles alongside source changes.
A new crate must be referenced in the toplevel Cargo.toml as well as release-plz.toml.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.