菜单
Use when writing something public-facing about this project's engineering. A release announcement, a how-we-built-X deep-dive, a retrospective. Not tied to a release event, and not the mechanical changelog (that's changeset-writing's job).
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/segunadebayo/design-eng-skills --skill engineering-writing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing or reviewing a component's public API. Naming, props, compound component structure, CSS custom properties, and data-attributes.
Use when a feature involves multiple states or transitions. Recognizes the shape, names states and events, designs guards, actions, and hierarchy, and visualizes or simulates the result.
Use when writing a changeset for a change to a published package. Picking the semver bump, writing the summary, flagging breaking changes, and making sure the entry still reads well once aggregated into CHANGELOG.md.
基于 SOC 职业分类
正在显示 SKILL.md
| name | engineering-writing |
| description | Use when writing something public-facing about this project's engineering. A release announcement, a how-we-built-X deep-dive, a retrospective. Not tied to a release event, and not the mechanical changelog (that's changeset-writing's job). |
Narrative, external-facing technical writing, built from reading real engineering blogs end to end and cross-checking against writing-craft, persuasion, and copywriting research, not from generic advice about "good writing." Every technique in the references below is attributed to where it actually came from.
An announcement, a how-we-built-X deep-dive, or a retrospective answer different reader questions and take different shapes. Decide this first. references/REGISTERS.md.
What does the reader already believe, and is there a genuinely surprising fact here, or is this the same generic post everyone already wrote? Don't draft until you have a real answer to both. references/PERSUASION-ETHICS.md and references/METHODOLOGY.md.
Write the one small section you understand completely, not the whole piece at once. Cutting happens later, as its own pass. references/METHODOLOGY.md.
Nine real patterns, cold scene, concrete problem, disarming confession, myth-then-dismantle, reframed word, credentials-then-claim, TL;DR, tension, two-sentence tradeoff, pick the one that fits what you actually have. references/OPENINGS-AND-MOMENTUM.md.
Every sentence's job is to get the next one read. Reveal iteratively, show the alternatives you rejected, end sections with a reason to keep going. references/OPENINGS-AND-MOMENTUM.md.
Second person, short sentences, a number or name behind every claim. No em dashes, no decorative emoji, no hype words, no AI-tell phrases. Run the checklist before you ship. references/VOICE-AND-SLOP.md.
A command to run, a link, the sentence you'd want quoted if nothing else gets read. Never a summary of what you already said.
The mechanical, per-change changelog entry is changeset-writing's job, not this one. This skill is for the narrative writing: why it matters, what was hard, what happened, not the record of what changed.
