What this prompt does
This prompt builds a concrete 90-day developer content plan you can execute, not a list of motivational tips. It casts the AI as a developer-advocate and content strategist. You supply your [niche], your [audience], the [weekly_hours] you can spend, and your [platforms] in priority order. It returns three evergreen content pillars, a twelve-week table mapping weekly themes to LinkedIn, GitHub, and blog ideas, a rule for how each week compounds on the last, nine search-aligned topics, a per-platform time budget, and three success metrics with thresholds.
The plan is designed to be sustainable by reusing work you already do. Pillars drawn from your [niche] mean you write about problems you solve weekly rather than inventing content. The compounding rule keeps each week building authority instead of posting randomly, and the [weekly_hours] budget keeps the plan realistic. Ranking [platforms] decides where your limited time goes first.
When to use it
- Starting to build authority in a
[niche]and you want a structured runway - Turning real engineering work into LinkedIn, GitHub, and blog content
- Fitting content into a fixed
[weekly_hours]budget without burning out - Prioritizing effort across
[platforms]when you cannot do all of them well - Mapping topics to what your
[audience]actually searches for - Replacing random posting with a plan where each week compounds
Example output
You get the three pillars and three metrics stated up front, then a twelve-week Markdown table with columns for week, theme, a LinkedIn idea, a GitHub repo or gist idea, a blog idea, and a learning topic. Below or within it sit the compounding rule that ties each week to the last, the nine search-mapped topics aligned to what your audience queries, and a weekly time budget per platform that fits your stated hours. There are no filler weeks — every row is concrete and actionable.
Pro tips
- Pick a
[niche]narrow enough that pillars come from problems you solve weekly — broad niches produce generic, hard-to-sustain content - Be honest about
[weekly_hours]; an overstated budget produces a plan you will abandon by week three - Order
[platforms]by where your[audience]actually is, since the time budget front-loads the top platform - Use the nine search-mapped topics as your highest-leverage pieces — they are tied to what people query
- Lean on the compounding rule: let each week reference or extend the last so authority accumulates instead of resetting
- Treat the three metrics as kill criteria — if a pillar never crosses its threshold, swap it rather than forcing it
- Reuse a single GitHub repo or gist across several weeks so the content amplifies work you would build anyway instead of inventing throwaway demos
