tangzhan-runse-master_skill

Overview

This skill is a focused text polishing engine built to collaborate with a persona named Tang Zhan. It applies a light-touch "30% effort" editing rule to technical drafts, preserving the author's voice as a 13-year backend veteran and AI-native thinker. The output is ready-to-use Markdown plus short distribution hooks for social sharing.

How this skill works

The skill reads the original draft and applies minimal edits: adjust rhythm, fix typos, tighten copy, and improve Markdown structure without rewriting core voice or arguments. It enforces terminology standardization (for example, always convert "Cloud Code" to "Claude Code") and outputs polished Markdown plus 1–2 concise promotion hooks. Edits focus on readability, accuracy, and preserving the persona's direct, no-nonsense tone.

When to use it

• Polish technical blog posts while keeping the original author's voice intact.
• Prepare internal design notes or post-mortems for clear, senior-engineer readership.
• Convert rough draft into publication-ready Markdown without heavy rewriting.
• Standardize terminology across developer-facing content.
• Create short, punchy hooks for social distribution alongside the polished piece.

Best practices

• Use the skill for editorial light-touch only—avoid drafts that need full rewrites.
• Provide context about target audience (senior backend engineers) so tone stays aligned.
• Keep original metaphors and core phrasing; allow only rhythm and formatting tweaks.
• Flag any domain-specific terms that must not be changed besides enforced mappings.
• Request explicit output length or heading structure when formatting constraints matter.

Example use cases

• Turn an internal RFC into a concise Markdown article for the company blog while retaining the author’s blunt, experienced voice.
• Polish a technical newsletter entry about distributed systems, ensuring terminology like "Claude Code" is correct.
• Refine a talk abstract or README excerpt to improve rhythm and skimmability for senior engineers.
• Prepare a post-mortem summary for management and engineering teams, emphasizing actionable takeaways.
• Create a short, punchy social post and a corresponding Markdown article for wider technical audiences.