AGENT SKILL

rfc

A request for comments: the problem, goals and non-goals, the proposal with the alternatives considered, risks, rollout and open questions, with a status banner, grounded in the code and docs it changes.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1.1k
Forks
104

01 前言 Front Matter

od
{ "mode": "prototype", "craft": { "requires": [ "typography", "typography-hierarchy", "color", "accessibility-baseline" ] }, "preview": { "type": "html", "entry": "index.html" }, "platform": "desktop", "scenario": "engineering", "design_system": { "requires": false }, "example_prompt": "Write an RFC for moving our image exports to a job queue: problem, goals and non-goals, the proposal with alternatives, risks, rollout plan and open questions. Read the current export code first." }
name
rfc
tags
[ "rfc", "design doc", "proposal", "engineering", "architecture", "技术方案" ]
emoji
📐
en_name
RFC
zh_name
技术方案 RFC
category
doc
scenario
engineering
triggers
[ "rfc", "design doc", "technical proposal", "request for comments", "engineering proposal", "技术方案" ]
description
A request for comments: the problem, goals and non-goals, the proposal with the alternatives considered, risks, rollout and open questions, with a status banner, grounded in the code and docs it changes.
en_description
A request for comments: the problem, goals and non-goals, the proposal with the alternatives considered, risks, rollout and open questions, with a status banner, grounded in the code and docs it changes.

02 资源文件 1

03 SKILL.md 正文

RFC

Intent. A proposal people can review and decide on. Readers skim the summary and the decision; reviewers read the alternatives and the risks.

Ground it

Write only what the sources say. Gather them yourself before writing a word:

  • the code and docs the proposal changes (read them; cite file paths);
  • related issues, earlier RFCs or ADRs the user points to;
  • if it comes from a spec or openspec change, its proposal and design files.

Keep the list of files, commits and refs you read: they go in a Sources section at the bottom of the page and in sources when you register (register_open_design_artifact with kind html). If something the document needs isn't in the sources, ask the user, or mark it plainly as an open question. Never invent numbers, dates, names or quotes.

Structure

  1. Header: title, RFC-<number> if the repo numbers them, author(s), date, and a status banner: <p class="status" data-od-status="draft|proposed|accepted|rejected|superseded">…</p>. Superseded RFCs link to their replacement.
  2. Summary: three to five sentences: what changes and why, in plain words.
  3. Problem: what's wrong today, with evidence from the sources (code paths, numbers, user reports).
  4. Goals and Non-goals: short bullet lists. Non-goals matter: they stop scope creep.
  5. Proposal: the design, at the level a reviewer needs. Diagrams as simple HTML boxes, or a diagram artifact exported as an image; code in <pre>.
  6. Alternatives considered: each with why it lost. At least one.
  7. Risks and mitigations: a two-column table.
  8. Rollout: steps, flags, migration and rollback.
  9. Open questions: numbered, each with an owner if known.
  10. Sources.

Design

  • One readable column (max-width 720–780px), body 16–17px with line-height 1.55–1.65, generous space between sections. It must read well on a phone: tables sit in an overflow-x: auto wrapper, nothing has a fixed width wider than the screen.
  • Style from the active design system (--bg, --surface, --fg, --muted, --border, --accent); status colours are the only extra colours (green for accepted/done, amber for proposed/in progress, red for rejected/high severity, grey for superseded).
  • Headings are short labels; the content does the talking. Code, paths and commands in a monospace face, with overflow-wrap: anywhere so long paths wrap on phones.
  • Finish with check_open_design_artifact and fix every error at desktop and mobile width.

04 同仓库更多 Skills

feimacode
feimacode/open-design-agent-kit

youtube-clipper

YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

writing-guidelines

Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

★ 1.1k
feimacode
feimacode/open-design-agent-kit

wpds

WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

weread-year-in-review-video-template

WeRead-inspired HyperFrames video template for vertical annual reading reports, personal reading dashboards, book-note recaps, and shareable year-in-review stories. Use when users want a 9:16 HTML-to-MP4 reading report with warm paper texture, editorial Chinese typography, book-page metaphors, data highlights, and deterministic motion.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

web-design-guidelines

Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

web-clone

网站复刻 / 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互/WebGL/Canvas/Three.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树,覆盖静态站 / React-Vue-Next 内容站 / WebGL-Canvas 重前端站三大分支,并强制核对任何 AI 二手分析里的可执行代码。

★ 1.1k