菜单
Write an Architecture Decision Record (ADR) — lead with the decision, give neutral context, and state consequences both ways. Use when recording an architectural or technical decision, documenting why a choice was made, or capturing tradeoffs for future maintainers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Best practices when developing in Crystal codebases
Best practices when developing in Go codebases
Write essays, blog posts, newsletters, and opinion pieces in a personal first-person voice — concrete cold open, argument by historical analogy, deliberate sentence rhythm, aphoristic kicker. Use when drafting or editing personal essays, blog posts, op-eds, newsletter issues, or any first-person long-form meant to persuade or reflect.
Write an RFC or design doc — summary-first, with goals/non-goals, real alternatives, drawbacks, and open questions. Use when proposing a technical change for review, writing a design doc, or documenting a system or feature proposal before building it.
Write clear technical documents — design docs, PR descriptions, proposals, postmortems — that lead with the decision and ground every claim in specifics. Use when drafting or editing workplace technical writing where a reader must act or later understand why. For the specific RFC and ADR formats, use writing-rfc and writing-adr.
Python development guidelines and best practices. Use when working with Python code.
| name | writing-adr |
| description | Write an Architecture Decision Record (ADR) — lead with the decision, give neutral context, and state consequences both ways. Use when recording an architectural or technical decision, documenting why a choice was made, or capturing tradeoffs for future maintainers. |
An ADR captures a decision and the forces behind it, so a future maintainer doesn't
have to reverse-engineer "why is it like this?" from the code. It is a log entry, not
a monument. (For proposing a change still under debate, use writing-rfc.)
Lead with the decision. State it in the first lines, in active voice ("We will…"). Context and justification follow. Don't bury the conclusion under the analysis.
State consequences both ways. What becomes easier and what becomes harder, what you now owe. The honesty of the "harder" half is what makes the record trustworthy.
Append-only. A record is not edited away when it's overturned. Set the old ADR's
status to Superseded by ADR-NNN and link forward; preserve the original reasoning.
ADR-NNN: <the decision, as a short imperative>.Optionally add Alternatives considered (each with an honest why-not) when the rejected options carry real weight, and Non-goals to bound scope.