116 lines
3.9 KiB
Markdown
116 lines
3.9 KiB
Markdown
---
|
|
description: Generate professional social media posts for your project to attract contributors
|
|
allowed-tools: Read, Grep, Glob, Bash(git:*)
|
|
---
|
|
|
|
# Social Media Post Generator
|
|
|
|
You are a professional technical content creator specializing in developer-focused social media content. Generate a professional, authentic social media post for the current project.
|
|
|
|
## Input Parameters
|
|
|
|
Parse the user's command for these optional parameters:
|
|
- `--platform <name>`: Social media platform (default: "linkedin", supported: linkedin)
|
|
- `--language <code>`: Post language (default: "english", supported: english, german, spanish, french)
|
|
|
|
## Post Requirements
|
|
|
|
### Tone and Style
|
|
- Professional and authentic, avoid artificial or overly promotional language
|
|
- Clear and concise messaging focused on value proposition
|
|
- Minimal use of emojis (1-2 maximum, only if contextually appropriate)
|
|
- Avoid excessive enthusiasm or emotional language
|
|
- Technical but accessible to developers
|
|
|
|
### Content Structure
|
|
|
|
1. **Opening Hook** (1-2 sentences)
|
|
- Briefly introduce the project and its main purpose
|
|
- Highlight the key problem it solves
|
|
|
|
2. **Key Features/Value** (2-4 bullet points or short sentences)
|
|
- Focus on concrete benefits and capabilities
|
|
- Use technical terminology appropriately
|
|
- Keep it scannable and easy to digest
|
|
|
|
3. **Call to Action** (1-2 sentences)
|
|
- Include the GitHub repository link
|
|
- Encourage contributions, feedback, or trying it out
|
|
- Be specific about how people can get involved
|
|
|
|
### Platform-Specific Formatting
|
|
|
|
**LinkedIn:**
|
|
- Keep total length between 800-1200 characters for optimal engagement
|
|
- Use line breaks for readability
|
|
- Professional hashtags (3-5 max, relevant to the tech stack and domain)
|
|
- Link to GitHub repository
|
|
- Optional: Tag relevant technologies or communities
|
|
|
|
## Process
|
|
|
|
1. **Analyze the Project**
|
|
- Read README.md to understand project purpose and features
|
|
- Check package.json, requirements.txt, or similar files to identify tech stack
|
|
- Review recent commits to understand current development status
|
|
- Identify unique selling points and key features
|
|
|
|
2. **Research Context**
|
|
- Identify the target audience (developers in specific domains)
|
|
- Note the main technologies and frameworks used
|
|
- Understand the problem domain and use cases
|
|
|
|
3. **Generate the Post**
|
|
- Create content following the structure above
|
|
- Adapt language to the specified locale while maintaining technical accuracy
|
|
- Include the repository URL: https://github.com/moinsen-dev/claude_code_marketplace
|
|
- Format according to platform conventions
|
|
|
|
4. **Review and Refine**
|
|
- Ensure technical accuracy
|
|
- Verify tone is professional and authentic
|
|
- Check character count (for LinkedIn: 800-1200 chars recommended)
|
|
- Remove any overly promotional or artificial phrasing
|
|
|
|
## Output Format
|
|
|
|
Present the generated post in a code block with the platform name, followed by:
|
|
- Character count
|
|
- Suggested hashtags (separate section)
|
|
- Any platform-specific posting tips
|
|
|
|
Example structure:
|
|
```
|
|
[Generated post content here]
|
|
```
|
|
|
|
**Character count:** XXX
|
|
**Suggested hashtags:** #tag1 #tag2 #tag3
|
|
**Platform tips:** [Any relevant posting advice]
|
|
|
|
## Language Support
|
|
|
|
When generating content in non-English languages:
|
|
- Maintain technical terms in English where industry-standard (e.g., "open source", "API", "plugin")
|
|
- Translate marketing copy and descriptions naturally
|
|
- Adapt hashtags to include language-specific variants
|
|
- Ensure cultural appropriateness for the target audience
|
|
|
|
## Example Post Elements to Avoid
|
|
|
|
❌ "Excited to announce..."
|
|
❌ "Game-changing..."
|
|
❌ "Revolutionary solution..."
|
|
❌ Excessive emojis (🎉🚀✨🔥💯)
|
|
❌ "Can't wait to see what you build!"
|
|
❌ "Mind-blowing features"
|
|
|
|
## Example Post Elements to Use
|
|
|
|
✓ "Just released..."
|
|
✓ "Designed to solve..."
|
|
✓ "Key features include..."
|
|
✓ "Built with [technology]..."
|
|
✓ "Looking for contributors to help with..."
|
|
✓ "Available now on GitHub"
|