$ man content-wiki/content-os-full-stack
Content Workflowsintermediate
the content OS tool stack (what we actually use and why)
Every tool in the stack creates, distributes, or measures content. if it doesn't do one of those, it doesn't belong.
by Shawn Tenam
the AI layer
Claude is the primary AI for long-form writing, code generation, system design, and anything requiring sustained reasoning. The context window and instruction-following make it reliable for complex workflows that can't afford hallucinations.
ChatGPT handles project organization, API integration brainstorming, and quick iterative tasks. The project memory feature is useful for storing persistent context that doesn't need to be rebuilt each session.
Grok is the social scout. It has real-time X access and a personality that's calibrated for understanding what's actually trending versus what just looks like it's trending. Use it to monitor what conversations are happening before writing takes on a topic.
Midjourney handles character art and brand visuals. The Nio character and brand visual system were built in Midjourney. ElevenLabs handles voice generation when audio content is in the pipeline. The quality gap between ElevenLabs and other TTS tools is still significant.
the creation layer
Cursor IDE is an AI-native code editor with inline completions, codebase-aware chat, and debugging. It's where interactive building happens ... when you want to write code alongside AI explanation and iteration.
Claude Code CLI is the automated layer. It runs as an agent in your terminal, reads your entire repo, writes code, runs tests, and commits. The nightly cron pipeline uses Claude Code to run automated content builds and repo management while you sleep. It's the difference between AI as a tool you use and AI as a system that runs.
Super Whisper is voice-to-text drafting. Talking through a post idea and editing the transcript is 3-4x faster than writing from scratch for most people. The quality of modern voice recognition means transcript cleanup takes under a minute for a 500-word post.
Canva handles quick graphics and social templates. VEED does video editing and auto-subtitles for longer content. CapCut is TikTok and Reels specific ... the built-in template library and trending audio integration are worth the context switch from a more general editor.
the distribution layer
LinkedIn is the primary platform. 6.7K+ followers, long-form tactical content, 3-5x per week cadence. The audience skews B2B decision-makers and practitioners which makes it the highest-value distribution channel for any business-adjacent content.
X is an expanding channel for short-form takes and real-time commentary. The strategy is complementary to LinkedIn, not competitive ... LinkedIn for depth, X for speed and conversation.
TikTok is video-first builder content. The platform's algorithm doesn't punish low follower count the way LinkedIn does, so it's a viable growth channel even at 0 followers if the content quality is there.
Reddit is the authentic community participation channel. Not self-promotion, not link dropping ... genuine participation in subreddits where the content is useful. r/entrepreneur, r/SaaS, r/marketing for the primary audience. The karma and account age requirements mean this is a long-term build, but the trust signals from Reddit traffic are high quality.
the analytics and infrastructure layer
Favikon is the cross-platform creator analytics layer. Weekly check-in on influence score, category ranking, and engagement rate trends. It's the feedback loop that tells you whether the algorithm is rewarding what you're building.
The infrastructure is a Next.js 15 monorepo running three sites from one codebase. Shared components and utilities mean a component built once works across all three sites. Vercel handles deployment ... push to main, site is live. The CI/CD pipeline runs automatically.
SQLite runs locally for data that doesn't need to be in the cloud. The nightly cron pipeline queries it for content ops data, logs results back, and produces automated reports. The database grows more useful over time as patterns accumulate.
on notetakers and second brain tools
Obsidian handles personal knowledge management. Local-first, markdown files, graph view that shows connections between notes. The bidirectional linking is the feature ... connect a note about content strategy to a note about a specific tool and the graph surfaces those relationships visually. Your data lives on your machine, no cloud dependency.
Notion with MCP handles team collaboration and structured databases. The MCP integration means Claude can read and write to your Notion workspace directly, turning a passive wiki into an active workflow component. Ask Claude to check your content ideas database before suggesting topics for the week and it will.
The key rule for notetakers: one primary system you actually use beats two half-used systems. Pick Obsidian if you think in freeform and want a knowledge graph. Pick Notion if you think in structured tables and need team access. Use Apple Notes for quick mobile captures that get processed into the primary system later.
building your own OS vs. third-party tools
Tools like Typefully, Later, and Taplio exist and have their place when you're starting. Scheduling tools abstract away distribution mechanics that are worth understanding before you automate them. Use them until you understand what they're doing, then decide whether to keep them or replace with something custom.
The more you build your own operating system, the less you need external tools. The shift is from AI as a drafting assistant to AI as a version control system for your thinking. Hundreds of drafts exist in the pipeline but content comes naturally once you've internalized the patterns at a system level ... the AI stops generating ideas and starts executing them.
The test for any new tool: does it create, distribute, or measure content? If yes, evaluate it. If no, don't add it. Tool sprawl is a real productivity cost. The OS is the system connecting the tools, and complexity in the system creates maintenance overhead that eventually exceeds the value of the tool that created it.
frequently asked questions
Q: Is this stack too expensive for someone starting out?
A: The free tier of most tools here is functional for at least 6 months of building. Claude (free tier), Cursor (free tier), Canva (free), Favikon (free profile). The paid tools that matter first: Claude Pro for longer context, Cursor Pro for codebase chat. Everything else scales when revenue justifies it.
Q: Do I need all of these tools?
A: No. Start with one AI tool, one creation tool, one platform. Add tools when you hit a specific constraint, not because the stack sounds impressive.
Q: What's the most underrated tool in this stack?
A: Super Whisper. The combination of voice drafting and Claude editing removes the blank page problem entirely. Talking is faster than typing and the transcript gives Claude something concrete to work from.
Q: How long did it take to build this OS?
A: About 18 months of iterative addition and subtraction. Some tools looked essential and got cut. The current stack is stable because every remaining tool has a clear function that nothing else in the stack handles.
related entries
Recursive Content FlowBuilding a Content RepoAgent Skills for Content Automationwhich AI to use on which platform (the honest breakdown)elevenlabs for content buildersfavikon is how you see what the algorithm seesthe repos and skills you actually need to build AI-powered appsvideo editing for builders who are not video editorsnotetaker tools and second brain systems for builders