Skip to main content

create-a-content-style-guide

Create concise, testable writing rules from audience needs, brand decisions, and recurring content examples. Use when multiple people or agents need consistent editorial choices.

来源信息

仓库
protosphinx/sphinxstack
最近来源活动
2026年7月29日 13:55
检测到的 SKILL.md 语言
英语
星标
3
Forks
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
2 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
create-a-content-style-guide
category
write
description
Create concise, testable writing rules from audience needs, brand decisions, and recurring content examples. Use when multiple people or agents need consistent editorial choices.
# create-a-content-style-guide Record decisions writers repeatedly need. Prefer examples and decision rules over abstract brand adjectives. ## Procedure 1. Define audiences, channels, content types, languages, owners, and the inconsistency or risk the guide must reduce. 2. Audit representative published content, support issues, search behavior, legal requirements, and accessibility needs. 3. Identify recurring decisions about voice, tone, structure, terminology, grammar, numbers, dates, links, calls to action, and inclusive language. 4. Separate organization-specific rules from the external base style the team adopts. 5. Write each rule with rationale, preferred example, avoid example, and exception where needed. 6. Add channel and situation guidance for errors, urgency, sensitive topics, translation, and regulated claims. 7. Create an approved terminology list with definitions, capitalization, deprecated terms, and owner. 8. Test the guide on real editing tasks with multiple users and record disagreements or missing rules. 9. Revise for findability, assign governance, and set a version, feedback path, and review trigger. ## Failure plan - Do not encode stereotypes, exclusion, manipulative patterns, or unsupported marketing claims as voice. - Never copy another organization's proprietary guide without permission. - If a rule conflicts with law, accessibility, accuracy, or user safety, those constraints win. - Avoid rules that cannot be distinguished in real examples. ## Done - Core rules, terminology, examples, exceptions, and owners are written - Multiple users apply the guide to representative content with consistent results - Version, review trigger, feedback route, and superseded guidance are recorded
在 GitHub 查看