メニュー
Use this skill when the user needs a content strategy, wants to build in public, grow an audience, choose content platforms, or create a distribution plan. Covers platform selection, build-in-public frameworks, content distribution, and audience building for solo founders.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | content |
| description | Use this skill when the user needs a content strategy, wants to build in public, grow an audience, choose content platforms, or create a distribution plan. Covers platform selection, build-in-public frameworks, content distribution, and audience building for solo founders. |
For a solo founder, content IS the marketing department. This skill helps you pick a platform, build an audience through authentic sharing, and convert followers into customers — without a marketing team or ad budget.
Choose ONE based on where your ICP actually spends time:
| Platform | Best For | Content Style | ICP Signal |
|---|---|---|---|
| Twitter/X | Developers, SaaS founders, tech professionals | Short-form threads, hot takes, metrics sharing | Your ICP tweets about work, follows industry leaders |
| B2B professionals, enterprise buyers, consultants | Professional stories, industry insights, career content | Your ICP has detailed LinkedIn profiles, posts about industry | |
| Technical audiences, niche communities | Helpful answers, deep-dive posts, genuine participation | Active subreddits exist for your problem space | |
| Indie Hackers | Solo founders, bootstrappers | Revenue updates, strategy deep-dives, lessons learned | Your buyers are themselves builders/founders |
| Hacker News | Developers, technical decision-makers | Technical articles, Show HN launches, Ask HN questions | Your ICP reads HN, comments on technical topics |
| Discord/Slack | Community-first audiences, developer tools | Ongoing helpful presence, quick answers | Active communities exist in your niche |
How to decide: Go where your ICP already has conversations about the problem you solve. Search for your problem keywords on each platform. The one with the most active discussion is your platform.
1. Progress Updates (weekly) What you built, what moved, what the numbers say.
This week:
- Shipped [feature]. Here's why it matters: [user problem it solves].
- MRR: $X → $Y (+Z%)
- Biggest surprise: [insight]
- Next week: [what you're tackling]
2. Decision Stories (2-3x/month) The reasoning behind a product, pricing, or strategy choice.
A user asked for [feature]. I said no. Here's why:
[Explain the reasoning — what you considered, what tradeoffs exist,
what you decided and why.]
The harder question isn't "should we build it?" It's "what should
we NOT build so we can focus on what matters?"
3. Lessons & Failures (2-3x/month) What went wrong and what you learned. This is the highest-engagement content type.
I lost 12% of my users last month. Here's what happened:
[Honest explanation of what went wrong.]
[What you learned.]
[What you're changing.]
Sharing because I wish someone had told me this 6 months ago.
4. How-We-Built-It (2-4x/month) Technical or tactical deep-dives that showcase your expertise.
How I built [feature] in [timeframe]:
[Step-by-step breakdown of the approach]
[Tools/tech used]
[Result for users]
Full breakdown: [link to blog post or thread]
5. Problem Exploration (1-2x/month) Content about the problem space that's useful even without your product.
The 3 things every [ICP role] gets wrong about [problem]:
1. [Misconception] — Actually, [truth]. Here's why...
2. [Misconception] — The data says [counter-evidence]...
3. [Misconception] — I learned this the hard way when...
Monday: Progress update or metrics share
Tuesday: Problem exploration or industry insight
Wednesday: How-we-built-it or tactical tip
Thursday: Decision story or lesson learned
Friday: Community engagement (reply to others, ask questions)
Minimum viable cadence: 3 posts per week. You can always scale up, but consistency at 3/week beats burnout at 7/week.
Thread format (highest engagement):
Tweet 1 (hook): [Surprising claim or specific result]
Tweet 2-6: [The substance — one idea per tweet, each stands alone]
Tweet 7 (close): [Takeaway + soft CTA]
Example hook tweets:
- "I went from 0 to $5K MRR in 90 days. Here's the exact playbook:"
- "A user asked me to build [feature]. I said no. Here's why:"
- "I tracked every hour I spent for 30 days. The results surprised me:"
- "The biggest mistake I made building [Product] (and how I fixed it):"
Single tweet format:
[Insight or observation]
[Supporting detail or data point]
[Implication or takeaway]
Keep under 240 characters for maximum reach. Or go long (up to 4,000 chars)
for nuanced takes.
Post format:
[Strong opening line — pattern interrupt or bold claim]
[blank line]
[3-5 short paragraphs, each 1-2 sentences]
[Use line breaks aggressively — LinkedIn rewards readability]
[Personal anecdote or specific data point]
[Takeaway or question to drive comments]
[Optional: 3-5 relevant hashtags]
What works on LinkedIn:
Post format:
Title: [Specific, descriptive, not clickbait]
Body:
- Lead with the value or question
- Be genuinely helpful first
- Share your experience, not your pitch
- Mention your product only if directly relevant AND you disclose it's yours
- Respond to every comment
Rules:
Post format:
Title: [Specific milestone, lesson, or question]
Body:
- Detailed breakdown of what happened
- Actual numbers (revenue, users, conversion rates)
- What you tried, what worked, what didn't
- Specific advice for others in similar situations
The IH community values transparency and specificity above all else.
Every piece of content should have a path to your product, but it should never feel like an ad.
Soft CTAs (use these):
Hard CTAs (use sparingly, only on high-value posts):
Link strategy:
One piece of content becomes many:
Blog post (1,500 words)
→ Twitter thread (extract 7-10 key points)
→ LinkedIn post (extract personal angle)
→ Reddit comment (answer a related question, link to post)
→ Newsletter edition (add personal context)
→ Indie Hackers post (add revenue/metrics context)
Write once, distribute everywhere. But adapt the format and tone for each platform.
Track monthly:
| Metric | This Month | Last Month | Trend |
|-------------------------------|------------|------------|-------|
| Posts published | | | |
| Total impressions/views | | | |
| Engagement rate (%) | | | |
| Profile/bio link clicks | | | |
| Signups attributed to content | | | |
| Followers gained | | | |
| DMs/replies about product | | | |
The only metric that truly matters: signups (or revenue) attributed to content. Everything else is a leading indicator.
Tell AI:
Help me plan my build-in-public content strategy:
- Product: [what it does]
- Audience: [who it's for]
- Platform I want to focus on: [Twitter/LinkedIn/Reddit/etc.]
- Current metrics: [MRR, users, or "pre-launch"]
- What I'm working on this week: [current project or feature]
Create:
1. A week's worth of posts (5 posts) using the 5 content pillars
2. Each post ready to copy-paste, formatted for [platform]
3. A mix: 1 progress update, 1 decision story, 1 lesson, 1 how-we-built-it, 1 problem exploration
Tell AI (for individual posts):
Write a [Twitter thread / LinkedIn post / Reddit post] about:
- Topic: [what happened, what you learned, what you decided]
- Key insight: [the one thing you want people to take away]
- Product mention: [include naturally / don't mention product]
- Tone: [casual and honest / professional / technical]
Make it sound like a real person sharing their experience, not a brand posting content.
Use the humanize skill patterns — no AI-sounding language.
| Mistake | Fix |
|---|---|
| Posting on 5 platforms at once | Pick ONE. Go deep. Expand after 3 months of consistency. |
| "Excited to announce..." openings | Lead with the value, insight, or result — not your feelings |
| Only posting about your product | 80% valuable content, 20% product mentions |
| AI-generated posts without editing | Audiences detect AI instantly. Write authentically or use humanize skill. |
| Giving up after 2 weeks | Content compounds. Give it 3 months of 3x/week before judging. |
| No call-to-action anywhere | Every post should have a soft path to your product |
Use this skill when the user wants to write long-form prose — blog posts, founder essays, build-in-public posts, About pages, newsletter intros, or origin stories. Also use when the user mentions 'blog post,' 'essay,' 'long-form,' 'founder voice,' 'build in public,' 'BIP post,' 'About page,' 'origin story,' or 'newsletter copy.' For microcopy and CTAs, see copywriting. For removing AI patterns from existing text, see humanize. For SEO articles, see seo-content. For content strategy and distribution, see content.
Use this skill when the user doesn't know what to work on next, asks 'what should I do?', wants to find high-value opportunities, or needs help deciding where to spend their time. Also use when the user mentions 'what should I do next,' 'what should I work on,' 'where should I focus,' 'find low-hanging fruit,' 'what's the most valuable thing I could do,' or 'I don't know what to do.' Scans the full project — code, infrastructure, marketing, growth, business — and surfaces 3-5 high-impact, low-effort opportunities ranked by value. Routes each recommendation to the right skill.
Use this skill to find and eliminate duplication across your codebase — UI components, database schema, and workflow logic. Also use when the codebase feels bloated, features take longer to build, changes break in unexpected places, or after significant AI-assisted development. Covers code deduplication, component reuse, database normalization, and modular architecture.
Use this skill when the user's app feels slow, the codebase feels bloated, or after significant development work. Also use when the user says 'my app is slow,' 'clean up my code,' 'reduce bundle size,' 'my hosting bill is too high,' or 'everything feels sluggish.' Optimizes across four dimensions: Speed (page load, API response), Code (unused files, dead code), Database (orphaned data, schema hygiene), and Dependencies (package bloat, bundle size).
Use this skill when the user is building software for a regulated industry and needs to understand compliance requirements. Also use when the user mentions 'HIPAA,' 'FERPA,' 'SOC 2,' 'PCI,' 'GDPR,' 'compliance,' 'regulated industry,' 'healthcare app,' 'fintech,' 'edtech,' or asks 'do I need to worry about [regulation]?' Covers what regulations mean for your tech stack — not legal theory, but concrete technical requirements.
Use this skill when the user needs to hire a developer, find a technical contractor, vet engineering talent, manage freelancers, write a job brief, decide between hiring and contracting, or bring on their first technical team member. Also use when the user says 'I need a developer,' 'should I hire someone,' 'how do I find a contractor,' 'I need technical help I can't do myself,' or 'AI keeps getting this wrong, I need a human.' Covers contractor sourcing, vetting, management, and the founder-developer working relationship for non-technical founders.