Publisher All Streamlined

Generate platform-optimized content for X/Twitter, LinkedIn, Medium, and Dev.to from a single source in one command, eliminating the need to manually adapt content across channels.

When to Use This Command

Run this command when you have content ready to distribute across multiple social and publishing platforms simultaneously.

• You published a new blog post and want to promote it across X, LinkedIn, Medium, and Dev.to
• You need platform-specific content variations without spending hours manually adapting tone and format
• You want to generate all social previews in one pass and review them in browser tabs
• You are running a content marketing workflow and need consistent cross-platform distribution

Use it also when:

• You want to save 2+ hours of manual content adaptation per article
• You need both English and Japanese versions of your cross-platform content

Quick Start

Copy
# .claude/commands/publisher-all-streamlined.md
name: publisher-all-streamlined
description: Generate content for all publishing platforms
arguments:
  input: Blog slug, file path, or URL

Copy
# Generate content for all platforms from a blog slug
claude publisher-all-streamlined "my-post-slug"

Expected output:
Publishing pipeline complete:
  - X/Twitter: x-thread-en.html (3 formats: thread, long, short)
  - LinkedIn: linkedin-draft-en.html (with media attachment)
  - Medium: medium-article-en.html (copy-paste ready)
  - Dev.to: rss-devto.xml (auto-import feed)

Opening 4 browser tabs for review...

Core Concepts

Concept	Description
Source Content	The original blog post, article, or URL used as input
Platform Adapter	Content transformation logic for each target platform
HTML Preview	Browser-viewable preview file with copy buttons
RSS Feed	XML feed for Dev.to automatic content import
Language Support	Content generation in English (default) or Japanese

Content Pipeline:
  Source ──> Parse ──┬──> X/Twitter (thread + long + short)
                    ├──> LinkedIn (post + media)
                    ├──> Medium (HTML article)
                    └──> Dev.to (RSS feed)

Configuration

Parameter	Default	Description
input	required	Blog slug, file path, or URL to source content
language	en	Target language: en or ja
platforms	all	Which platforms to generate for
open-browser	true	Auto-open preview tabs in browser
output-dir	current dir	Directory for generated preview files

Best Practices

1. Review each platform's output individually -- Each platform has unique formatting rules. Do not assume what works on X will work on LinkedIn without checking the preview.

2. Edit the source content first -- Polish your blog post before running the publisher. The generated content quality directly reflects the source material.

3. Use the HTML preview copy buttons -- Each preview file includes one-click copy buttons optimized for each platform's paste behavior.

4. Run Dev.to feed generation only once -- The RSS feed is cumulative. Run it once to generate the initial feed, then add new posts incrementally.

5. Set up Dev.to RSS import for automation -- After generating rss-devto.xml, configure Dev.to at dev.to/settings/extensions to auto-import from your deployed RSS URL.

Common Issues

1. Source content not found -- Verify the blog slug matches a file in your content directory, or provide a full file path or URL instead.

2. Browser tabs not opening -- On headless or remote systems, the open command may fail. Check generated files manually in the output directory.

3. LinkedIn API credentials missing -- Without API setup, LinkedIn content is generated for manual copy-paste. Add credentials to .env for direct posting.