菜单
Voice and drafting guide for all writing meant for other people: posts, articles, updates, messages. Use whenever drafting or editing for an audience. This file handles drafting; the voice itself lives in TASTE.md. If the two conflict, TASTE.md wins.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Apply WCAG 2 Level AA accessibility standards to design systems, UI components, and web pages — contrast math with a runnable validator, design-token patterns that make color accessible by construction, typography and focus-state rules, and a semantics checklist. Use when building or reviewing UI, choosing colors or type for a brand/design system, setting up design tokens, wiring accessibility checks into a build, or when the user mentions accessibility, a11y, WCAG, contrast, or screen readers.
Detect AI-sounding drift in written content and apply a surgical de-slop pass only where needed. Run on drafts before sending for review.
Engineering leadership principles and decision-making framework. Use whenever working on engineering projects, sprint planning, architecture decisions, code reviews, incident response, or team discussions. Apply these principles proactively.
Read raw notes in inbox/, classify and label each one, draft what should be drafted in the author's voice, and open the results for review. Never publishes on its own.
| name | writing-style |
| description | Voice and drafting guide for all writing meant for other people: posts, articles, updates, messages. Use whenever drafting or editing for an audience. This file handles drafting; the voice itself lives in TASTE.md. If the two conflict, TASTE.md wins. |
Template. This is a generic drafting guide. The personality lives in
TASTE.md— replace that with your own voice. Keep this file mostly as-is; it is just sane defaults for how to draft.
Before drafting anything, read TASTE.md in this directory. It defines the voice. This file only
defines how to draft and edit. If a rule here makes the writing feel less true or more performative,
ignore the rule and follow the taste.
Before drafting, name three things:
If you can't state the core idea in one sentence, the piece isn't ready.
Don't open with framing before the reader feels the problem.
When it helps, include the actual artifact — the config, the command, the number, the line someone said. Concrete detail is a trust signal. Don't decorate with it.
Default to a genuine question or something the reader can use. Don't force a call to action. Don't summarise what you just said.
