build-in-public
Generate social media posts for building in public, coding in public, or dev content creation. Activate when user mentions Twitter, X, BlueSky, LinkedIn, Instagram posts about coding, sharing progress, social media content for developers, or wants to share what they built.
What this skill does
# Build in Public - Social Media Post Generator
This skill helps developers create engaging social media content from their Claude Code sessions for the #BuildingInPublic and #CodingInPublic communities.
## Capabilities
- Parse Claude Code session transcripts to extract highlights
- Generate platform-appropriate posts for:
- **Twitter/X**: Short posts (280 chars) and threads
- **BlueSky**: Short posts (300 chars)
- **LinkedIn**: Medium-length professional updates
- **Instagram**: Long-form captions with hashtags
- **Mastodon**: Medium posts with hashtags
- Track session metrics (files created, commits, bugs fixed, etc.)
- Output both markdown (human-readable) and JSON (for automation)
## When to Activate
Activate this skill when the user:
- Asks to create social media posts about their coding
- Mentions "building in public" or "coding in public"
- Wants to share their progress on Twitter, X, BlueSky, LinkedIn, or Instagram
- Asks for a session summary to share
- Mentions #BuildingInPublic or similar hashtags
- Says things like "I want to tweet about this" or "post this to social media"
## Commands Available
- `/build-in-public:generate` - Generate posts from the current session
- `/build-in-public:preview` - Preview session activity before generating
## How to Generate Posts
When the user wants to create social media content:
1. **Preview first** (optional): Run `/build-in-public:preview` to show them what happened in the session
2. **Generate posts**: Run the generation script:
```bash
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/generate_posts.py" --output . --json
```
3. **Present the best options**: Show the user 1-2 ready-to-post short posts and mention the full file has more options
4. **Offer customization**: Ask if they want to emphasize certain aspects or add custom context
## Post Formats
### Short Posts (Twitter/X, BlueSky)
- Max 280 characters
- Include 1-2 relevant hashtags
- Focus on one key accomplishment
- Use emojis sparingly but effectively
### Threads (Twitter/X)
- 4-6 tweets
- Start with a hook
- End with engagement question
- Each tweet under 280 chars
### Medium Posts (LinkedIn)
- 500-700 characters
- Professional tone
- Bullet points for accomplishments
- Include relevant hashtags at the end
### Long Form (Instagram)
- 1000+ characters
- Storytelling format
- Multiple hashtags (up to 30)
- Include call-to-action
## Output Files
The generator creates:
- `build-in-public_[timestamp].md` - Human-readable posts with all options
- `build-in-public_[timestamp].json` - Structured data for automation tools
## Integration with Publishing Tools
The JSON output can be consumed by automation tools to publish posts. The structure:
```json
{
"summary": {
"session_id": "...",
"project_name": "...",
"files_created": [...],
"git_commits": [...],
...
},
"posts": {
"short": ["post1", "post2"],
"thread": ["tweet1", "tweet2", ...],
"medium": ["linkedin post"],
"long": ["instagram caption"],
"hashtags": ["#BuildingInPublic", ...]
}
}
```
## Tips for Great #BuildingInPublic Content
1. **Be specific**: "Added user authentication" beats "worked on the app"
2. **Show numbers**: "Fixed 3 bugs, created 5 files" is more engaging
3. **Include the struggle**: Bugs fixed = relatable content
4. **End with engagement**: "What are you building?" invites responses
5. **Use relevant hashtags**: Match the tech stack (#Python, #React, etc.)
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.