Content
Social Content OS
Turn scattered notes, shipping updates, and product opinions into a coherent publishing system.
Non-negotiables
- Optimize for earned signal. Every idea maps to: claim, proof, implication, reply target
- Prefer artifact-backed content: screenshots, code, diagrams, benchmarks, launch notes
- Keep the mix weighted toward technical and product depth
- Treat non-public information as off-limits unless explicitly marked public
- Prefer recurring series over disconnected one-offs — repetition creates recognition
Workflow
1. Identify the narrative
- What identity to reinforce: engineer, builder, product thinker, operator
- Which audience matters most
- Which pillar the idea belongs to
- What evidence exists now vs. what needs gathering
2. Convert raw notes into post briefs
- Working title, pillar, one-sentence claim
- Specific proof, why it matters now
- Best platform and format
- Asset to attach, confidentiality check
3. Shape the publishing mix
Balance across pillars — don't let one topic dominate the feed.
4. Prioritize
Favor ideas with at least two of: sharp contrarian angle, real build artifact, named event/result, stealable lesson, conversation starter.
5. Deliver actionably
Default output: ranked backlog with platform assignments, draft briefs for the top 3, and a cadence recommendation.