What this prompt does
This prompt casts the model as a developer relations expert and builds a personal-brand strategy around technical blogging. You supply [expertise], [target_audience], [current_presence], [blogging_goal], and [frequency], and it returns niche positioning, content pillars, a 12-post calendar, developer-focused SEO, a distribution plan, a post template, and growth milestones.
The structure mirrors what actually grows a technical audience: a narrow niche, tutorials with real code, and pushing each post beyond its day-one spike. It positions you with a primary and secondary niche based on your [expertise] and names oversaturated areas to avoid. It defines four to five content pillars, then fills a 12-post calendar with titles, pillars, formats, target keywords, and difficulty, rotating tutorials, opinion pieces, case studies, and comparisons. Because you set [frequency], the calendar and milestones pace realistically, and [traction_metrics] defines what month-three success looks like for you.
When to use it
- When you want to build authority as a developer through writing but don't have a plan.
- To pick a narrow niche and content pillars instead of blogging about everything.
- When you need a concrete 12-post calendar with formats and target keywords.
- To get a distribution plan so posts don't die after their first day.
- When you want SEO title formulas and a repeatable post template for technical writing.
Example output
You get a positioning section (primary niche, secondary niche, areas to avoid, and a positioning statement), a content-pillar table with descriptions, example titles, and search intent, a 12-post content calendar with title, pillar, format, keywords, and difficulty per row, developer-blog SEO guidance with title formulas and a technical checklist, a day-by-day distribution plan across Twitter, LinkedIn, Dev.to, Hacker News, and newsletters, a reusable blog-post template (hook, context, solution, gotchas, conclusion, CTA), and a milestones table from foundation to monetization.
Pro tips
- Make
[expertise]and[target_audience]narrow and specific — "Laravel for mid-level PHP devs leveling up to senior" produces a far sharper niche than "web development." - Set
[frequency]to what you can truly sustain; the calendar and milestones pace off it, and consistency beats volume for building authority. - Write about problems you actually hit in real work — that's what makes tutorials rank and read as credible, and the calendar leans on tutorials for SEO value.
- Use
[blogging_goal]to bias the plan; aiming for consulting leads versus a future course changes which pillars and CTAs make sense. - Treat the distribution plan as the real work — publishing is half the job; pushing each post across channels over three days is what gets it read.
- Set realistic
[traction_metrics]so the milestones are motivating targets rather than vanity numbers you'll ignore.
