README to Landing Page

Transform a project's README.md into a concise, visual, developer-friendly landing page.

Core Principle: Show, Don't Tell

Developers skim — they don't read walls of text. The output README must:

• Prefer visuals over prose — use mermaid diagrams for architecture, workflows, data flow
• Be concise — every sentence must earn its place; cut ruthlessly
• Be scannable — badges, tables, code blocks, diagrams; minimize paragraphs
• Be direct — lead with what matters, skip the preamble
• No emoji — never use emoji in headings, body text, badges, or section labels

If something can be a diagram, make it a diagram. If something can be a table, make it a table. If something can be a one-liner, don't write three sentences.

Anti-Slop Rules

AI-generated READMEs have predictable tells. Slop signals "nobody reviewed this" and kills credibility. See references/anti-slop-rules.md for the full banned-phrase list and structural patterns to avoid.