免费在 GitHub 公开

markdown

The rules for every Markdown file in the repository, inside docs/ or not: prose a reader understands on the first pass, MECE structure, headings rather than bold, checklists for TODOs. Read before writing or editing any Markdown (.md) file.

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

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

实测评分未实测

查看安装方法

包含的文件（1）

SKILL.md1.6 KB

SKILL.md（原文）

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

Markdown

The goal is prose a reader understands on the first pass. Everything below serves that.

Prose

Plain words. One idea per sentence. The plain statement first, the reason for it after.
Three habits make a reader decode instead of read: a second clause hung off a dash, an abstract noun standing where a verb would do, and the clever phrasing of a point arriving before the obvious one. Undo each where you find it.
Correct and fresh. Keep the facts.
Cutting narration and redundancy is one way to get there. It is not the point. A passage that came out shorter and harder to follow has failed.

Structure

Keep a document simple and MECE.
Do not use **...** (bold) for sub-sections. Use Markdown sections instead.
Use a Markdown checklist for TODOs (- [ ] ...) and what's done (- [x] ...).

Numbers

A measured figure belongs in the table that holds its measurement, not in prose beside it: the table gets refreshed and the prose does not.
A table whose refresh you cannot see is a reason to find how it was measured, not to delete it. Name the command beside the table; deleting a measurement loses a fact.
Name the shape to grep for, not how many sites there are. A count goes stale with the next site.

Finish

Run mise run format after editing.

评价

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

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

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

同一仓库的技能

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.

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