docs: README should tell a story, not list features

[DevanshuNEU]

Summary

Rewrites the README to tell a story instead of listing features.

What changed

Before: Technical description, feature list, "MCP server" identity

OpenCodeIntel gives AI coding assistants deep understanding of your codebase. 
It's an MCP server that provides semantic code search...

After: Pain point first, show don't tell

You know that mass of code you inherited? The one where you spend 20 minutes 
grep-ing just to find where authentication happens?

OpenCodeIntel fixes that.

Key improvements

1. Opens with the pain — Every developer knows the feeling of being lost in a codebase
2. Shows real examples — Table with actual search queries and what they find
3. Concise features — One-liner descriptions, not bullet point lists
4. De-emphasized MCP — It's in a collapsible section, not the identity
5. Collapsible setup — Manual setup and MCP config hidden by default (clean)
6. Shorter overall — ~120 lines vs ~145 lines (shadcn-style confidence)

Inspiration

• shadcn/ui: Brevity = confidence. 15-line README, 80k stars.
• Cal.com: Relatable opening, positions against known pain
• Supabase: Clean architecture diagrams, clear "what it does"

Comparison

Metric	Before	After
Lines	145	~120
Opens with	Technical description	Developer pain point
Features	Bullet list	Table with real examples
MCP mention	In tagline	In collapsible section
Tone	Corporate docs	Developer talking to developer

Screenshots

Will add after merging (need to see rendered markdown)

---

Closes #190

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
opencodeintel	Ignored		Jan 9, 2026 0:06am