content-forge/.claude/commands/repurpose.md

131 lines
3.8 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Transform published content into formats suitable for other platforms (X threads, LinkedIn, newsletter, video script, etc.)
## Philosophy
> "If you can repurpose, don't rewrite. One piece of content should spawn many children."
Based on [[glue-coding]] principles: reuse mature content, adapt for new contexts, minimize original creation.
## Step 1: Load Source Content
```bash
cd /home/kang/apps/content-forge/content-forge
obsidian files folder="04-published"
```
Or target specific content:
```bash
obsidian read path="04-published/YYYY-MM-DD-slug.md"
```
## Step 2: Analyze Source Structure
Identify:
- **Core insight**: What's the main value proposition?
- **Key points**: 3-5 extractable ideas
- **Format elements**: Code blocks, lists, quotes, examples
- **Tone**: Technical/Casual/Educational
- **Length**: Word count and reading time
## Step 3: Select Target Platforms
| Platform | Best For | Typical Length |
|----------|---------|-----------------|
| **X/Twitter** | Hot takes, thread series | 280 char × N tweets |
| **LinkedIn** | Professional insights | 500-1000 words |
| **Newsletter** | Deep dives, tutorials | 1000-2000 words |
| **Xiaohongshu** | Visual + text, lifestyle | 500-800 words + images |
| **Video Script** | Tutorials, stories | 1000-1500 words (3-5 min) |
| **Infographic** | Data, processes | Visual summary |
| **Podcast** | Conversations, stories | 1500-2500 words (10-15 min) |
## Step 4: Generate Repurpose Plan
For each target platform, specify:
1. **Angle**: What aspect of the original content fits this platform?
2. **Cut**: What to remove? (too technical, too long, wrong tone)
3. **Add**: What's needed? (hooks, examples, visuals)
4. **Format**: Structure for this platform
## Output Format
```
=== Repurpose Plan ===
Source: [original title]
Path: 04-published/YYYY-MM-DD-slug.md
Core Insight: [one sentence summary]
## Repurpose Targets
### 1. X Thread Series
Angle: [specific angle for X audience]
Thread Structure:
Tweet 1 (Hook): [hook statement]
Tweet 2-4 (Core): [key points]
Tweet 5 (CTA): [call to action]
Effort: Low
Estimated Reach: [X impressions]
### 2. LinkedIn Post
Angle: [professional angle]
Format: [listicle/carousel/text post]
Hook: [opening line]
Key Takeaway: [main insight]
Effort: Medium
Estimated Reach: [LinkedIn impressions]
### 3. Newsletter Section
Angle: [subscriber value]
Section Type: [main feature/tutorial/case study]
Headline: [newsletter headline]
Effort: Low (reuse existing)
### 4. Video Script (Optional)
Angle: [visual storytelling angle]
Duration: [X minutes]
Key Scenes: [list 3-5 visual moments]
Effort: High
---
## Recommended Execution Order
1. [lowest effort, highest reach item]
2. [next priority item]
3. [high effort items - schedule separately]
## Assets to Create
- [ ] X thread graphics (use baoyu-xhs-images)
- [ ] LinkedIn carousel (use baoyu-infographic)
- [ ] Newsletter header image (use baoyu-cover-image)
## Next Actions
1. [immediate action]
2. [scheduled action]
3. [future consideration]
```
## Integration with Other Commands
- Use `/promote` first to identify promotion opportunities
- Use `/repurpose` to plan the actual content transformation
- Use `write-article` skill to generate new drafts from repurposed content
- Use `baoyu-*` skills to generate platform-specific assets
## Frontmatter Updates
After repurposing, update source file:
```yaml
repurposed_to:
- slug: x-thread-YYYY-MM-DD
- slug: newsletter-issue-XX
evergreen: true # Mark as reusable for future repurposing
```
## Tips
- **One-to-Many**: One article should spawn at least 3 derivative pieces
- **Platform-Native**: Adapt tone and length for each platform, don't just copy-paste
- **Asset Reuse**: Generate images once, use across all platforms
- **Link Back**: Always reference the original article
- **Schedule Gap**: Don't release all formats same day - stagger for maximum impact