🧪 What other tests should we add to the README linter?

[atick-faisal]

Hey folks 👋

We're building the world's first LLM-powered README unit testing framework (for real), and right now it checks for the essentials:

• ✅ Project description
• 🔧 Installation instructions
• 💻 Usage examples
• 📄 License info
• 📸 Screenshot or demo link

---

💡 But we know README snobs want more.

This is your space to suggest new checks you'd love to see:

• Should we check for a badge zoo?
• Should we verify the presence of a contributing guide?
• Should we detect if there's TOO much fluff and not enough usage?
• Should we nudge people to include an architecture diagram?
• Should we yell at people who have “TODO” sections that haven’t been touched since 2019?

---

🛠️ Criteria for a good check:

• It's objectively useful to readers (not just vibes)
• It's detectable via LLM prompt ("yes" or "no")
• It's not too niche (unless it’s a banger)

---

Drop your ideas below!
Feel free to include the check’s name, a short description, and even an example prompt if you’re feeling spicy 🔥

Let’s make the README police more powerful together 🚓📄