跳到正文
cccskills
免费在 GitHub 公开

rust

Workspace-specific Rust rules that override common habits: panic instead of dummy or no-op fallbacks, never catch a panic outside tests, enums over unclear bool parameters, no wildcard match arms, dependencies managed in the workspace Cargo.toml, 2024 edition, zero warnings and clippy lints. Read before writing or editing Rust (.rs) code.

中文简介正在准备中。当前显示原文说明。

wado-lang/wado星标 119(GitHub 119 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md1.6 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

  • Manage dependencies in the workspace Cargo.toml.
  • Use the panic! macro instead of falling back to meaningless dummy values or no-op implementations.
  • Never catch a panic in production code. A panic is a bug, and it ends the run. So there is no catch_unwind, a task is joined through wado_host::sync::joined rather than its JoinError turned into an error value, and a thread's panic is resumed where it is joined. Tests may catch one.
  • Take an enum rather than a bool where the call site would not say what the flag means. f(x, true) makes the reader open f, and f(x, Mode::Strict) does not.
  • Use the 2024 edition.
  • Keep the code free of compiler warnings and Clippy lints. mise run clippy runs -D warnings, so any warning or lint fails it.
  • Import every item you name. A crate:: or super:: path goes in a use item at the top of the module; where the item is read, write its name. use crate::elaborator::sem::Ty; then Ty, never crate::elaborator::sem::Ty inline. Alias a collision (use crate::ast::Ty as AstTy;) rather than spelling the path out. A hook refuses an edit that writes one inline, and mise run check-rust-paths gates the rest.
  • Avoid wildcard match arms (_ => ...) unless absolutely necessary.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

benchmark

免费

Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.

中文简介正在准备中。当前显示原文说明。

wado-lang/wado1192026年10月26日 更新

ci-timing

免费

Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.

中文简介正在准备中。当前显示原文说明。

wado-lang/wado1192026年10月26日 更新

How to answer code review feedback — a human reviewer, CodeRabbit, or any review bot. Verify the findings, report the classes they are instances of to the user before fixing, then fix the class rather than the sites named. Put design decisions to the user, then run /distill. Invoke when responding to review comments on a pull request, or to the findings of a /code-review run.

中文简介正在准备中。当前显示原文说明。

wado-lang/wado1192026年10月26日 更新

Investigate and improve code coverage for the wado-compiler crate. Use for any question about what the tests do and do not reach, dead code included.

中文简介正在准备中。当前显示原文说明。

wado-lang/wado1192026年10月26日 更新

cr

免费

Review the branch with /code-review at high, then answer the findings with /code-review-response.

中文简介正在准备中。当前显示原文说明。

wado-lang/wado1192026年10月26日 更新

debugger

免费

Use rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any investigation into what the compiler is actually doing (lldb is unavailable on Claude Code Web).

中文简介正在准备中。当前显示原文说明。

wado-lang/wado1192026年10月26日 更新

查看 wado-lang 的全部技能

报告此技能的问题