一键导入
content-writing
Use when writing or reviewing website copy, articles, headlines, ledes, persuasive content, readability, or scannable structure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when writing or reviewing website copy, articles, headlines, ledes, persuasive content, readability, or scannable structure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Top-level router for the Chwezi Core Systems web-development and software-engineering skills engine. Use for AI systems, SaaS, architecture, APIs, databases, security, frontend engineering, mobile, DevOps, reliability, product engineering, SDLC documentation, catalog maintenance, delivery evidence packs, routing fixtures, and world-class engineering quality gates.
Use when specifying or implementing engine-neutral gameplay systems such as movement, combat, AI, quests, dialogue, inventory, progression, save/load, world state, spawning, cameras, or narrative state; engine skills own framework integration.
Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.
Use when discovering, designing, prioritizing, or auditing AI-powered products for measurable business value. Applies to AI opportunity mapping, ROI cases, product strategy, client workshops, and deciding whether an AI feature should be built.
Use when specifying one AI-powered feature end to end, including model choice, prompt and context contracts, output schema, fallbacks, human oversight, UX states, and evaluation.
Use when discovering and ranking AI use cases for a project or module and producing an opportunity register with impact, effort, cost, risk, and evidence gaps.
| name | content-writing |
| description | Use when writing or reviewing website copy, articles, headlines, ledes, persuasive content, readability, or scannable structure. |
| metadata | {"portable":true,"compatible_with":["Codex","codex"]} |
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
| Input | Required | Use |
|---|---|---|
| Decision, audience, and deliverable | yes | Bound the business outcome |
| Source evidence, constraints, and owner | yes | Ground recommendations and accountability |
| Approved budget, customer data, or production artefacts | conditional | Support high-impact execution |
Default to read-only analysis and drafting. Do not publish, send, price, promise, alter customer records, commit budget, or modify production artefacts without explicit authority and a named approver. Minimise confidential data, preserve provenance, and keep reversible copies.
If evidence, stakeholder decisions, specialist tooling, or authoritative commercial data are unavailable, deliver a labelled draft, checklist, or decision memo. State what was not verified and do not claim approval, publication, financial accuracy, or customer acceptance.
| Condition | Action | Stop condition |
|---|---|---|
| Output creates a commercial, customer, or delivery commitment | Obtain named approval before release | Authority or terms are unclear |
| Evidence supports a reversible draft | Produce it with assumptions and owner | Required evidence conflicts |
| Tooling or data is incomplete | Specify validation | A final executable artefact is expected |
| Category | Artifact | Format | Example |
|---|---|---|---|
| UX quality | Page copy review | Markdown doc covering headline, lede, body, and CTA per page against the content-writing standard | docs/content/page-copy-review-checkout.md |
references/ directory for deep detail after reading the core workflow below.premium-software-product-execution when copy must support premium pricing, buyer trust, service packaging, sales follow-up, or website-as-marketing-asset requirements.Professional copywriting standards for website copy, blog posts, articles, and all written content. This is a cross-cutting skill — apply these principles whenever creating or editing text for any page.
Every word exists for the reader, not the writer. Before writing anything, answer:
Write for the reader all the time. That is what separates content that converts from content that gets ignored.
The headline is the most important element. Five times as many people read the headline as read the body. If the headline fails, everything below it is wasted.
Extended guidance for content-writing was moved to references/skill-deep-dive.md to keep this entrypoint compact and fast to load.
Use that deep dive for:
The Lede (Opening)ReadabilityNiche Vocabulary (Thematic Depth)Scannable FormattingThe "So What?" TestAttribution as AuthorityUnique Value PropositionFeatures vs BenefitsStructure TemplatesKeeping Eyes MovingWriting StylesTakeawaysCopy must be accurate, audience-specific, readable aloud, supported by named proof, and free of claims the source material cannot substantiate.
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Reader-ready copy or copy review | Page owner, editor, or campaign team | The headline names a credible benefit, the body supplies proof, and the CTA states the next action without inventing claims |