Vexilo
Claude Code planner w/ 31 agents, 92 commands, + 121 skills
Start new thread

Vexilo - Claude Code planner w/ 31 agents, 92 commands, + 121 skills

by•
Most Claude Code users discover 10% of the ecosystem — by accident. You burn tokens because nobody told you /context exists. Vexilo fixes that. → 92 commands organized by use case → 31 specialist agents (code-reviewer, tdd-guide, planner...) → 121 skills by domain (frontend, backend, AI, devops) → ECC Superpowers workflow (160K+ ⭐ GitHub) → Auto-generates CLAUDE.md instantly Bilingual EN/中文 · PWA · One-time, no subscription.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt! 👋 I built Vexilo after a painful realization: I'd been using Claude Code for 2 months and burning 3x more tokens than necessary — because nobody told me /context existed. Then I found /aside. Then /model haiku. Then 31 specialist agents I never knew about. Each discovery felt like "wait, this existed the whole time?" The Claude Code ecosystem is genuinely incredible — but the discoverability is brutal, especially for non-English speakers. There's no central index. You find things by accident, through Discord comments and GitHub READMEs. So I built one. Vexilo maps the entire ecosystem — including Everything Claude Code (160K+ ⭐), gstack, and UI/UX Pro Max — into one bilingual interactive index, organized by what you're actually building. The CLAUDE.md export is the part I'm most proud of: drop it in your project root, tell Claude to read it, and it automatically knows every tool available and when to use each one. Free preview at vexilo.app — happy to answer any questions!

It took me weeks to discover /context or /model existed as well. There’s no canonical map of what exists or when to fire each one. Does update dynamically as new gstack commands ship, or is it a one-time snapshot at generation? Curious how you’re handling version drift between the ecosystem and the exported map.

Maker

 Great question — this is exactly the friction Vexilo exists for.

Short answer: is a one-time snapshot at export time, not a

live document. The web app itself stays current — I shipped v1.0.6 about

an hour ago when Anthropic released /goal in Claude Code v2.1.139,

bumping the count from 92 → 93 commands.

How drift is handled in practice:

1. The app polls a version manifest every hour. When a new release lands,

the topbar shows a "v1.0.x → v1.0.y" pill with the changelog.

2. Re-exporting is one click. Each export embeds the version

at the top of the file, so Claude itself can tell when it's reading

a stale snapshot.

3. New commands and agents land in the index within hours of upstream

release — that's the whole point of this being curated, not

auto-scraped.

Why not auto-refreshing ? Two reasons:

- It's a project artifact. Silent updates would diff in every PR and

destroy the audit trail.

- Local determinism matters. If Claude reads a that mutates

under it, you can't reproduce its output. That's a debugging hell.

So: snapshot + explicit re-export + always-visible update banner = no

drift in practice, with full reproducibility.

On the "weeks to discover /context existed" part — yeah, that's the

itch I built this for. The whole map's at if you want to

see what else you might be missing.

Maker

Hey Product Hunt! 👋

I'm Alex, the maker behind Vexilo.

Two months ago I started using Claude Code seriously and hit a wall immediately — not with the AI, but with discoverability. I kept finding powerful features by accident, months after I should have known they existed.

/context alone would have saved me hundreds of dollars in wasted tokens. I found it on week 6.

So I spent 3 weeks mapping the entire ecosystem. What started as a personal doc became Vexilo — an interactive, bilingual index of everything Claude Code can actually do.

What makes it different:

  • Organized by what you're building, not alphabetically

  • Auto-generates a you drop into any project

  • Works offline (PWA)

  • One-time purchase, no subscription

Use code PRODUCTHUNT for $5 off today.

Happy to answer any questions about Claude Code or how I built this. What's the most useful Claude Code feature you discovered way too late? 👇

Maker

Just woke up to this — the Reddit post hit 8K views overnight. Didn't expect this kind of response.

Thank you to everyone who checked out Vexilo and left feedback. Every comment has been genuinely useful. Still a long way to go but this feels like a real signal.

🙏