a4e667de10
Single-commit clean baseline after security scrub of niche-tells, project codenames, internal jargon, and contributor-email leaks. Contents: - 100 Rust crates (_primitives/_rust/) - 37 agent manifests (_manifests/) + generated specs (_generated/) - 67 user-invocable skills (skills/) - 33 hooks (hooks/) - Composition blocks (_blocks/) - Documentation (docs/, README.md) - TS adapter packages (_ts_packages/) - Assembler (_assembler/) - Roles (_roles/) - Templates (_templates/) - Forgejo CI (.forgejo/) Author: Denis Parfionovich <info@greendragon.info> License: see LICENSE.
1.5 KiB
1.5 KiB
| name | description | arguments | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| social-post | Use when creating platform-optimized social posts — Twitter threads, LinkedIn, Instagram, Telegram |
|
Social Post Workflow
Step 1: Core Message
- Identify the ONE key message / takeaway
- Who is the audience?
- What action should they take? (click, share, reply, sign up)
Step 2: Platform Adaptation
Twitter/X Thread
- Hook tweet: provocative statement or question (<280 chars)
- Body: 3-7 tweets, each standalone-valuable
- Last tweet: CTA + link
- Use line breaks for readability
- Numbers and lists perform well
- Hook: first 2 lines visible before "see more"
- Professional tone, personal experience angle
- 1300-1700 chars optimal
- End with question to drive engagement
- Relevant hashtags (3-5)
Instagram Caption
- Hook in first line
- Story format works best
- CTAs: "save this", "share with someone who..."
- 20-30 relevant hashtags (separate from caption)
- Emoji-friendly format
Telegram
- Direct, informative tone
- Markdown formatting (bold, links)
- Can be longer than other platforms
- Include media if relevant
Step 3: Output
- Generate post(s) for requested platform(s)
- If "all" — adapt same message to each platform's format
- Include suggested posting time (based on platform best practices)