blog

Write bilingual Chorus release blog posts with Chinese-first drafts and English versions.

1.1k|99|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill blog-chorus-aidlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill blog-chorus-aidlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release notes and product updates often read like feature lists or marketing copy, which fail to connect with readers' real pain points and lead to low engagement; this Skill ensures Chorus release posts open from the reader's problem and present the solution clearly in both Chinese and English.

Core Features & Use Cases

  • Chinese-first drafting: Produce a primary Chinese draft written natively, not as a translation from English, preserving natural rhythm and idioms.
  • Editorial-compliant frontmatter: Generate frontmatter with title, description, date, lang, and matching postSlug for both zh and en versions using the project's naming conventions.
  • Iterative review workflow: Present the Chinese draft for user review, incorporate feedback, then craft a distinct English version that adapts metaphors and phrasing for an English-speaking audience.
  • Use Case: Prepare zh-chorus-v0.6.2-release and chorus-v0.6.2-release posts that open from a user's pain point, explain the solution in layered sections, and conclude by tying back to the original problem.

Quick Start

Draft a Chinese release blog post for Chorus v0.6.2 that opens from a reader's pain point, follows the project's editorial style, and includes frontmatter with title, description, date, lang: zh, and postSlug: zh-chorus-v0.6.2-release.

Frequently Asked Questions about blog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write bilingual release blog posts that focus on user pain points?

Bilingual release blog posts that focus on user pain points require a problem-first narrative structure, drafting natively in Chinese first, then adapting the English version iteratively to ensure both versions share the same postSlug and frontmatter.

Can I generate a non-literal English translation from a Chinese release draft?

Yes, you can generate a non-literal English version from a Chinese draft by adapting metaphors and phrasing for an English-speaking audience, ensuring the English text stands independently rather than serving as a direct translation.

What frontmatter do I need for a bilingual release announcement?

Bilingual release announcements require frontmatter that includes title, description, date, lang, and postSlug fields, following project naming conventions to ensure both Chinese and English versions are properly linked and published.

How does the iterative review workflow work for bilingual blog posts?

The iterative review workflow for bilingual blog posts involves presenting the primary Chinese draft for user review, incorporating feedback, and then crafting the distinct English version only after the initial draft is approved.

Why do feature list release notes fail to engage readers?

Feature list release notes fail to engage readers because they read like marketing copy and do not connect with real pain points, whereas problem-first narratives open from the reader's issue and present the solution clearly.

Does the blog writing workflow support Chinese-first drafting?

Yes, the blog writing workflow supports Chinese-first drafting by producing a primary Chinese version written natively to preserve natural rhythm and idioms, avoiding the stiffness of translated text.