Use AI to generate a GitHub profile README that converts

Status: Outline — full guide coming soon. Get notified when it ships →

What this covers

• The structured input format (positioning + 3 projects + contact) the AI needs to write a good README
• The 3-iteration loop: draft → critique → tighten — each one removes filler
• Why fully-AI-written READMEs fail and how the human-in-the-loop pass fixes them
• A copy-paste prompt set you can use in 15 minutes total

Why this matters for Indian devs going remote

A blank or default GitHub profile README is the single most common gap on Indian-dev GitHub profiles. AI can close that gap in 15 minutes — but only if you give it structured input and run the critique pass. The lazy version produces obvious AI-slop READMEs that hurt more than they help.

Outline

The structured input format

TODO — positioning sentence, 3 project pitches, role-targeting, contact info; the input template.

The 3-iteration loop

TODO — iteration 1: draft; iteration 2: critique for AI-slop; iteration 3: tighten and human-voice; what each pass removes.

Why pure AI fails

TODO — generic phrasing, list-padding, "passionate developer" tropes, missing specificity; how the critique pass catches them.

The 15-minute prompt set

TODO — 3 prompts, one per iteration; expected output shape per step.

Common mistakes to avoid

• Giving the AI no structured input ("write me a README") — generic output
• Skipping the critique pass — AI-slop tells
• Copy-pasting the first draft without removing the obvious AI phrases

Templates / examples

TODO — the structured-input form (fill-in-blanks), the 3-prompt chain, and 3 example before/afters.

Related guides

• Your GitHub profile README: what recruiters actually see
• Use AI to build a developer portfolio site fast

---

Have a question about this? DM me on LinkedIn or drop your email to get the full guide as soon as it's published.