tuzi-copy-polish

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Social Copy Polish

社交媒体文案润色

Optimizes social media copy for different platforms. Adjusts tone, length, hashtags, and formatting based on platform best practices.
针对不同平台优化社交媒体文案,根据平台最佳实践调整文风、长度、话题标签和排版。

Step 0: Load Preferences ⛔ BLOCKING

步骤0:加载偏好设置 ⛔ 阻塞步骤

0.1 Check EXTEND.md

0.1 检查EXTEND.md

bash
test -f .tuzi-skills/tuzi-copy-polish/EXTEND.md && echo "project"
test -f "$HOME/.tuzi-skills/tuzi-copy-polish/EXTEND.md" && echo "user"
ResultAction
FoundLoad, parse, apply settings
Not foundContinue with defaults (ask platform in Step 2)
PathLocation
.tuzi-skills/tuzi-copy-polish/EXTEND.md
Project directory
$HOME/.tuzi-skills/tuzi-copy-polish/EXTEND.md
User home
EXTEND.md Supports: Default platform | Default language | Custom brand voice
Schema:
references/config/preferences-schema.md
bash
test -f .tuzi-skills/tuzi-copy-polish/EXTEND.md && echo "project"
test -f "$HOME/.tuzi-skills/tuzi-copy-polish/EXTEND.md" && echo "user"
结果操作
找到加载、解析并应用设置
未找到使用默认配置继续(在步骤2中询问平台)
路径位置
.tuzi-skills/tuzi-copy-polish/EXTEND.md
项目目录
$HOME/.tuzi-skills/tuzi-copy-polish/EXTEND.md
用户主目录
EXTEND.md支持配置:默认平台 | 默认语言 | 自定义品牌语气
配置Schema:
references/config/preferences-schema.md

Step 1: Analyze Input

步骤1:分析输入内容

Determine input source:
  • File path: Read file content as draft copy. Record the file path for Step 3 output.
  • Inline text: Use the text directly as draft copy.
Identify:
  • Content type (product promotion, knowledge sharing, personal story, news, opinion)
  • Current language and tone
  • Key message and selling points
  • Target audience (if mentioned)
确定输入来源:
  • 文件路径:读取文件内容作为文案草稿,记录文件路径供步骤3输出使用。
  • 行内文本:直接将该文本作为文案草稿。
识别以下信息:
  • 内容类型(产品推广、知识分享、个人故事、新闻、观点)
  • 当前使用的语言和语气
  • 核心信息和卖点
  • 目标受众(如有提及)

Step 2: Confirm Platform

步骤2:确认目标平台

If platform not specified by user or EXTEND.md, use AskUserQuestion:
yaml
header: "Target Platform"
question: "优化目标平台?"
options:
  - label: "小红书"
    description: "种草风、emoji、标签、口语化"
  - label: "X/Twitter"
    description: "简洁有力、英文友好、话题标签"
  - label: "抖音"
    description: "口语化、悬念开头、引导互动"
  - label: "微信公众号"
    description: "深度内容、段落清晰、引导关注"
  - label: "通用"
    description: "不针对特定平台,仅优化表达"
如果用户或EXTEND.md中未指定平台,则使用AskUserQuestion询问:
yaml
header: "Target Platform"
question: "优化目标平台?"
options:
  - label: "小红书"
    description: "种草风、emoji、标签、口语化"
  - label: "X/Twitter"
    description: "简洁有力、英文友好、话题标签"
  - label: "抖音"
    description: "口语化、悬念开头、引导互动"
  - label: "微信公众号"
    description: "深度内容、段落清晰、引导关注"
  - label: "通用"
    description: "不针对特定平台,仅优化表达"

Step 3: Polish Copy

步骤3:润色文案

Load platform rules from references/platforms/, then rewrite:
references/platforms/加载平台规则,然后进行改写:

Optimization Dimensions

优化维度

DimensionDescription
HookOpening line that grabs attention
ToneMatch platform culture (e.g., 小红书 casual, 公众号 professional)
LengthTrim or expand to platform sweet spot
StructurePlatform-specific formatting (line breaks, paragraphs, lists)
HashtagsAdd relevant tags per platform convention
CTACall-to-action matching platform interaction patterns
EmojiPlatform-appropriate emoji usage
维度说明
钩子吸引注意力的开篇句
语气匹配平台文化(例如:小红书偏随性,公众号偏专业)
长度删减或扩展内容至平台最优长度范围
结构平台专属排版(换行、段落、列表)
话题标签按照平台惯例添加相关标签
CTA匹配平台互动模式的行动号召
Emoji符合平台风格的表情使用

Output Format

输出格式

If input is a file path: Append the polished copy to the end of the original file, separated by a clear divider:
markdown
---
如果输入是文件路径:将润色后的文案追加到原文件末尾,用清晰的分隔线隔开:
markdown
---

Polished Copy ({platform})

润色后文案({platform})

{polished content}

Then inform the user: "已将优化后的文案追加到文件末尾: `{file_path}`"

**If input is inline text**: Present the polished copy in a code block for easy copying.

In both cases, include a brief changelog (what was changed and why, 2-3 bullet points).
{polished content}

随后告知用户:"已将优化后的文案追加到文件末尾: `{file_path}`"

**如果输入是行内文本**:将润色后的文案放在代码块中方便复制。

两种情况都需要附上简短的修改日志(2-3条要点说明修改内容和原因)。

Multiple Variants

多版本输出

When the user asks for options, generate 2-3 variants with different angles:
  • Variant A: Focus on emotion/story
  • Variant B: Focus on value/benefit
  • Variant C: Focus on curiosity/hook
当用户要求提供多个选项时,生成2-3个不同角度的版本:
  • 版本A:侧重情感/故事
  • 版本B:侧重价值/收益
  • 版本C:侧重好奇心/钩子

Step 4: Iterate

步骤4:迭代优化

After presenting the polished copy, ask if the user wants to:
  • Adjust tone (more casual / more professional)
  • Try a different angle
  • Optimize for another platform
  • Fine-tune specific parts
展示润色后的文案后,询问用户是否需要:
  • 调整语气(更随性 / 更专业)
  • 尝试不同角度
  • 适配其他平台优化
  • 微调特定部分

Extension Support

扩展支持

Custom configurations via EXTEND.md. See Step 0 for paths and supported options.
可通过EXTEND.md进行自定义配置,路径和支持的选项见步骤0