Back to Details

marketing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Marketing Skill for Theme & Plugin Agency

主题与插件机构营销Skill

Writing Style Guidelines

写作风格指南

Tone & Voice (Non-Negotiable)

语气与语态（硬性要求）

Be Human, Not AI:
  • Write like a helpful colleague, not a marketing robot
  • Use natural language that sounds like a real person wrote it
  • Avoid buzzwords: "revolutionary", "game-changing", "seamless", "leverage", "synergy"
  • Skip filler words: "basically", "essentially", "simply", "just"
  • No excessive punctuation (!!!) or ALL CAPS for emphasis
Emoji Policy:
  • Maximum ONE emoji per piece of content (or none)
  • Use only when it adds clarity, not decoration
  • Prefer text over emoji for important information
What to Avoid:
❌ "🚀 This REVOLUTIONARY plugin will TRANSFORM your workflow!! 💥"
✅ "This plugin handles form submissions automatically, so you can focus on your actual work."

❌ "Simply leverage our seamless integration to unlock game-changing results!"
✅ "Connect it to your email list in two clicks. New subscribers sync automatically."
像人一样写作，而非AI：
  • 像乐于助人的同事那样写作，不要像营销机器人
  • 使用听起来像真人撰写的自然语言
  • 避免使用流行空话："revolutionary"、"game-changing"、"seamless"、"leverage"、"synergy"
  • 省略冗余词："basically"、"essentially"、"simply"、"just"
  • 不要使用过多标点（如!!!）或全大写字母来强调内容
表情符号规则：
  • 每条内容最多使用1个表情符号（或完全不使用）
  • 仅在能提升内容清晰度时使用，而非为了装饰
  • 重要信息优先使用文字，而非表情符号
需避免的内容：
❌ "🚀 This REVOLUTIONARY plugin will TRANSFORM your workflow!! 💥"
✅ "This plugin handles form submissions automatically, so you can focus on your actual work."

❌ "Simply leverage our seamless integration to unlock game-changing results!"
✅ "Connect it to your email list in two clicks. New subscribers sync automatically."

Folder Structure

文件夹结构

When creating marketing content for a product, create this folder structure:
marketing/
├── 01-slides/                    # Visual presentation content
│   ├── product-overview-slides.md
│   ├── feature-breakdown-slides.md
│   ├── use-case-slides.md
│   └── free-vs-pro-comparison.md
├── 02-video-scripts/             # Video content
│   ├── 01-product-overview.md    # 2-3 min explainer
│   ├── 02-installation-setup.md  # Tutorial
│   ├── 03-feature-demos.md       # Feature walkthroughs
│   ├── short-ads.md              # 15s, 30s, 60s scripts
│   └── shot-list-template.md     # Production notes
├── 03-website-copy/              # Website content
│   ├── landing-page.md           # Full landing page
│   ├── features.md               # Feature highlights
│   ├── product-description.md    # Marketplace descriptions
│   ├── faq-content.md            # FAQ section
│   └── feature-pages/            # Individual feature pages
│       └── [feature-name].md
├── 04-email-sequences/           # Email campaigns
│   ├── welcome-sequence.md       # Onboarding emails
│   ├── feature-announcement.md   # New feature emails
│   ├── free-to-pro-upgrade.md    # Upgrade campaigns
│   └── re-engagement.md          # Win-back emails
├── 05-social-media/              # Social content (separate files per platform)
│   ├── twitter-posts.md          # Twitter/X content
│   ├── linkedin-posts.md         # LinkedIn content
│   ├── facebook-posts.md         # Facebook content
│   └── instagram-captions.md     # Instagram content
├── 06-sales-materials/           # Sales enablement
│   ├── one-pager.md              # Quick sales sheet
│   ├── objection-handling.md     # Sales FAQ responses
│   ├── feature-comparison-chart.md # Competitive comparison
│   ├── roi-calculator-content.md # Value justification
│   └── testimonials.md           # Customer quotes
├── 07-brand-assets/              # Brand guidelines
│   ├── persona-profiles.md       # Target customer profiles
│   ├── messaging-guide.md        # Voice and messaging
│   └── seo-keywords.md           # Keywords and meta content
└── README.md                     # Index and quick reference
为产品创建营销内容时，请使用以下文件夹结构：
marketing/
├── 01-slides/                    # Visual presentation content
│   ├── product-overview-slides.md
│   ├── feature-breakdown-slides.md
│   ├── use-case-slides.md
│   └── free-vs-pro-comparison.md
├── 02-video-scripts/             # Video content
│   ├── 01-product-overview.md    # 2-3 min explainer
│   ├── 02-installation-setup.md  # Tutorial
│   ├── 03-feature-demos.md       # Feature walkthroughs
│   ├── short-ads.md              # 15s, 30s, 60s scripts
│   └── shot-list-template.md     # Production notes
├── 03-website-copy/              # Website content
│   ├── landing-page.md           # Full landing page
│   ├── features.md               # Feature highlights
│   ├── product-description.md    # Marketplace descriptions
│   ├── faq-content.md            # FAQ section
│   └── feature-pages/            # Individual feature pages
│       └── [feature-name].md
├── 04-email-sequences/           # Email campaigns
│   ├── welcome-sequence.md       # Onboarding emails
│   ├── feature-announcement.md   # New feature emails
│   ├── free-to-pro-upgrade.md    # Upgrade campaigns
│   └── re-engagement.md          # Win-back emails
├── 05-social-media/              # Social content (separate files per platform)
│   ├── twitter-posts.md          # Twitter/X content
│   ├── linkedin-posts.md         # LinkedIn content
│   ├── facebook-posts.md         # Facebook content
│   └── instagram-captions.md     # Instagram content
├── 06-sales-materials/           # Sales enablement
│   ├── one-pager.md              # Quick sales sheet
│   ├── objection-handling.md     # Sales FAQ responses
│   ├── feature-comparison-chart.md # Competitive comparison
│   ├── roi-calculator-content.md # Value justification
│   └── testimonials.md           # Customer quotes
├── 07-brand-assets/              # Brand guidelines
│   ├── persona-profiles.md       # Target customer profiles
│   ├── messaging-guide.md        # Voice and messaging
│   └── seo-keywords.md           # Keywords and meta content
└── README.md                     # Index and quick reference

Instructions

操作说明

1. Always Start with Personas

1. 始终从Personas（用户画像）开始

Before creating content, define 3-5 target personas in 
07-brand-assets/persona-profiles.md
:
markdown
undefined
在创建内容前，请在
07-brand-assets/persona-profiles.md
中定义3-5个目标用户画像：
markdown
undefined

Persona: [Name]

Persona: [Name]

Demographics

Demographics

  • Role, Age, Team Size, Industry, Technical Level
  • Role, Age, Team Size, Industry, Technical Level

Goals

Goals

  • What they want to achieve
  • What they want to achieve

Pain Points

Pain Points

  • Problems they face (be specific, not generic)
  • Problems they face (be specific, not generic)

Why Product Appeals

Why Product Appeals

  • Feature-to-benefit mapping
  • Feature-to-benefit mapping

Key Message

Key Message

"One sentence that resonates with this persona"
"One sentence that resonates with this persona"

Content They Respond To

Content They Respond To

  • Types of content that work
undefined
  • Types of content that work
undefined

2. Product Descriptions

2. 产品描述

Lead with benefits, not features:
❌ "Includes auto-moderation feature"
✅ "Stop spam automatically — so you can focus on growing your community"
Power words to use wisely: effortless, powerful, stunning, instant, automatic Words to avoid: revolutionary, game-changing, seamless, leverage, synergy, cutting-edge
以用户收益为切入点，而非功能：
❌ "Includes auto-moderation feature"
✅ "Stop spam automatically — so you can focus on growing your community"
谨慎使用的有力词汇： effortless、powerful、stunning、instant、automatic 需避免的词汇： revolutionary、game-changing、seamless、leverage、synergy、cutting-edge

3. Feature Highlights

3. 功能亮点

Transform every feature into a benefit using:
  • "so you can..."
  • "which means..."
markdown
**What It Does:**
[Feature description - plain language]

**The Benefit:**
[Outcome] — so you can [user benefit].

**Why It Matters:**
- [Feature detail], which means [benefit]
- [Feature detail], so you can [benefit]
使用以下句式将每个功能转化为用户收益：
  • "so you can..."（让你能够……）
  • "which means..."（这意味着……）
markdown
**功能说明：**
[用平实语言描述功能]

**用户收益：**
[成果] —— 让你能够[用户收益]。

**重要性：**
- [功能细节]，这意味着[收益]
- [功能细节]，让你能够[收益]

4. Screenshots & Visuals

4. 截图与视觉内容

Requirements:
  • Use real screenshots from local development environment
  • Show actual product UI, not mockups
  • Annotate with arrows or highlights for clarity
  • Crop to relevant area (no full-screen captures)
  • Ensure no sensitive data visible
  • Use consistent browser/window size
Before creating visual content, ask:
"Do you have a local development setup where we can capture real screenshots? I'll need access to take authentic product images."
要求：
  • 使用本地开发环境的真实截图
  • 展示产品实际UI，而非原型图
  • 使用箭头或高亮标注以提升清晰度
  • 裁剪至相关区域（不要全屏截图）
  • 确保无敏感信息显示
  • 使用统一的浏览器/窗口尺寸
在创建视觉内容前，请确认：
"你是否有可用于截取真实截图的本地开发环境？我需要获取权限来拍摄真实的产品图片。"

5. Video Scripts

5. 视频脚本

Structure for each video:
markdown
undefined
每个视频的结构如下：
markdown
undefined

Video Details

视频详情

  • Title, Duration, Purpose, Tone, Target
  • Title, Duration, Purpose, Tone, Target

Script

脚本

INTRO (0:00 - 0:XX)

开场（0:00 - 0:XX）

VISUAL: [Description] NARRATOR: "[Script - conversational, not salesy]" ON-SCREEN TEXT: "[Text overlay]"
视觉： [描述] 旁白： "[脚本内容——口语化，而非推销式]" 屏幕文字： "[叠加文字]"

[SECTION NAME] (X:XX - X:XX)

[章节名称]（X:XX - X:XX）

...
...

Production Notes

制作说明

  • Visual style
  • Music suggestions (upbeat but not overwhelming)
  • Screenshots needed (from local dev environment)
undefined
  • 视觉风格
  • 音乐建议（轻快但不过于喧闹）
  • 需要的截图（来自本地开发环境）
undefined

6. Social Media (Separate Files Per Platform)

6. 社交媒体内容（按平台分文件存储）

Twitter/X: (
twitter-posts.md
)
  • Hook in first line
  • 1-2 key benefits
  • One emoji maximum (or none)
  • Thread format for longer content
LinkedIn: (
linkedin-posts.md
)
  • Professional tone
  • Problem → Solution format
  • Statistics and proof points
  • No emoji or one maximum
Facebook: (
facebook-posts.md
)
  • Community-focused
  • Storytelling approach
  • Engagement questions
Instagram: (
instagram-captions.md
)
  • Visual-first (describe image needed)
  • Short, punchy captions
  • Carousel/Reel ideas included
Twitter/X： (
twitter-posts.md
)
  • 首句设置钩子
  • 1-2个核心收益
  • 最多使用1个表情符号（或完全不使用）
  • 长内容使用推文串格式
LinkedIn： (
linkedin-posts.md
)
  • 专业语气
  • 问题→解决方案格式
  • 数据与实证
  • 不使用表情符号或最多使用1个
Facebook： (
facebook-posts.md
)
  • 以社区为核心
  • 故事化叙述方式
  • 设置互动问题
Instagram： (
instagram-captions.md
)
  • 视觉优先（描述所需图片）
  • 简短有力的文案
  • 包含轮播/Reel创意

7. Email Campaigns

7. 电子邮件营销

Structure each email file with multiple templates:
  • Subject line variations (A/B test)
  • Full email body (human tone, not salesy)
  • CTA options (clear, action-oriented)
每个邮件文件需包含多个模板：
  • 多种主题行（用于A/B测试）
  • 完整邮件正文（口语化，而非推销式）
  • 多种CTA选项（清晰、行动导向）

8. Sales Materials

8. 销售物料

One-Pager: Print-ready summary with:
  • Problem/Solution (lead with the problem they feel)
  • Key features (3-5 max)
  • Results/Stats (real numbers when possible)
  • Pricing
  • CTA
Objection Handling: For each objection:
  • Understand (clarifying questions)
  • Acknowledge (validate concern genuinely)
  • Address (provide information)
  • Confirm (check if resolved)
单页销售资料： 可打印的摘要，包含：
  • 问题/解决方案（从用户感受到的问题切入）
  • 核心功能（最多3-5个）
  • 成果/数据（尽可能使用真实数字）
  • 定价
  • CTA
异议处理： 针对每个异议，需包含：
  • 理解（澄清问题）
  • 认同（真诚地认可用户顾虑）
  • 解答（提供信息）
  • 确认（检查是否已解决用户疑问）

9. Pricing Messaging

9. 定价话术

Always include accurate pricing from product page:
markdown
| License | Price | Sites |
|---------|-------|-------|
| Single | $XX/yr | 1 site |
| 5 License | $XX/yr | 5 sites |
| Developer | $XX/yr | Unlimited |
务必包含产品页面上的准确定价：
markdown
| License | Price | Sites |
|---------|-------|-------|
| Single | $XX/yr | 1 site |
| 5 License | $XX/yr | 5 sites |
| Developer | $XX/yr | Unlimited |

Quality Checklist

质量检查清单

Before completing, verify:
完成前，请验证以下内容：

Content Quality

内容质量

  • Personas defined
  • All folders created
  • Pricing accurate
  • Benefits (not just features)
  • "so you can..." language used
  • Social media split by platform
  • Objection handling complete
  • README index updated
  • 已定义Personas（用户画像）
  • 已创建所有文件夹
  • 定价准确
  • 内容以收益为核心（而非仅功能）
  • 使用了"so you can..."类句式
  • 社交媒体内容按平台拆分
  • 异议处理内容完整
  • 已更新README索引

Tone Check

语气检查

  • Human tone (not robotic/AI-sounding)
  • No excessive emojis (max 1 per piece)
  • No buzzwords (revolutionary, seamless, etc.)
  • No filler words (basically, simply, etc.)
  • Reads like a helpful colleague wrote it
  • Direct and respectful of reader's time
  • 语气拟人（而非机器人/AI腔）
  • 无过多表情符号（每条内容最多1个）
  • 无流行空话（如revolutionary、seamless等）
  • 无冗余词（如basically、simply等）
  • 读起来像是乐于助人的同事撰写的
  • 直接明了，尊重读者时间

Visual Content

视觉内容

  • Screenshots requested from local dev environment
  • No stock photos where real product images should be
  • All visuals annotated clearly
  • No sensitive data visible
  • 已向本地开发环境索要截图
  • 需使用真实产品图片的场景未使用库存照片
  • 所有视觉内容标注清晰
  • 无敏感信息显示