Create platform-native content that resonates with each community's culture. Use when adapting technical content for WeChat, Hacker News, Reddit, Medium, Twitter/X, Dev.to, or LinkedIn. Transforms generic writing into content that feels written BY that community, not AT them.
Adapts technical content for specific platforms like WeChat, Hacker News, Reddit, Medium, Twitter/X, Dev.to, or LinkedIn. Use when you need to transform generic writing into culturally resonant posts that feel native to each community.
/plugin marketplace add shareAI-lab/shareAI-skills/plugin install shareai-lab-shareai-skills@shareAI-lab/shareAI-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/devto.mdreferences/hackernews.mdreferences/linkedin.mdreferences/medium.mdreferences/reddit.mdreferences/twitter.mdreferences/wechat.mdTransform technical content into platform-native writing that feels like it belongs.
Every platform is a culture, not a format.
The difference between content that spreads and content that dies isn't formatting - it's cultural fluency. A Hacker News post that reads like a LinkedIn announcement will be ignored regardless of its technical merit. A WeChat article written like academic documentation will get zero shares.
Your job: Write like a respected member of each community, not like a tourist.
Before writing for any platform, understand:
CRITICAL: The same insight packaged differently can get 0 engagement or 10,000. The insight doesn't change. The cultural packaging does.
Identify target platform from user input, then load ONLY that guide:
| User says... | Platform | Load | Do NOT Load |
|---|---|---|---|
| "公众号", "微信", "WeChat" | references/wechat.md | All others | |
| "HN", "Hacker News" | Hacker News | references/hackernews.md | All others |
| "Reddit", "r/", "subreddit" | references/reddit.md | All others | |
| "Medium" | Medium | references/medium.md | All others |
| "Twitter", "X", "thread" | Twitter/X | references/twitter.md | All others |
| "Dev.to", "dev.to" | Dev.to | references/devto.md | All others |
| "LinkedIn", "LI" | references/linkedin.md | All others |
MANDATORY: Read the corresponding platform guide completely before writing. Each guide contains the cultural context and anti-patterns specific to that platform.
These kill content on ANY platform:
Expert content writers understand:
When creating platform-specific content:
Remember: The goal isn't to "post content on Platform X." The goal is to become a valuable voice in that community.