The problem

The first screen of a README determines if developers star, fork, or bounce. Writing a clean, professional header that captures project value is time-consuming for new or messy repositories.

What it does

• Generates a professional project title and a concise one-line description.
• Distills project utility into 3-6 outcome-oriented feature bullets.
• Scaffolds a high-level quick start skeleton for immediate clarity.
• Creates a logical table of contents based on existing or planned sections.
• Outputs clean, portable Markdown ready for immediate pasting.

Why this beats prompting it yourself

General prompts often produce wordy paragraphs or technical implementation details. This skill enforces strict formatting rules to ensure features focus on user outcomes and the layout fits the "first screen" mental model without manual editing.

Use cases

• Initialize a new repository with a polished, professional landing page.
• Standardize the header structure across multiple internal company repos.
• Convert a messy, informal project description into a structured README.
• Draft a scannable summary for a project before writing full documentation.

Known limitations

Focuses only on the header section; you must write the detailed body content. It cannot scan your local files and relies entirely on your provided project description.