Feature request: add a "Community resources" section in README
Feature request: community-curated resources section in README
Problem
New Claude Code users hit /help, the official docs, then bounce around 30+ GitHub repos before they find the right agent, command, or skill. The discoverability cost is high; the integration cost is even higher.
Proposal
Add a short "Community resources" section near the end of the README, mirroring how Homebrew / Rust / npm ecosystem pages link out to curated indexes.
Two concrete resources worth surfacing today:
- Vexilo · A field guide to Claude Code — a live, visual index of 31 agents · 99 commands · 123 skills · 13 rules, organized around the 5-step workflow (Research → Plan → Test-first → Security → Commit). One-click "Teach Claude this handbook" feeds the whole index into a local session in 30 seconds. Actively maintained (v1.1.9, weekly updates). Runs in browser, no install.
- hesreallyhim/awesome-claude-code — the canonical curated list. (You probably already know about this one.)
Why now
Claude Code adoption is at the steep part of the curve. The official docs are excellent for "how do I install" but don't tell a new user which agent to call for what. Pointing at a vetted visual index fills that gap without expanding the docs team's surface area.
What I'm not asking for
- No code changes to
anthropics/claude-codeitself - No endorsement or "official" stamp
- No review of the linked project — just a "Community resources" pointer in the README
Happy to draft the exact wording as a PR if maintainers are open to it.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗