Viktor.comAn AI coworker that actually does the work
Vexilo
Claude Code planner w/ 31 agents, 92 commands, + 121 skills
73 followers
Claude Code planner w/ 31 agents, 92 commands, + 121 skills
73 followers
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.
Free Options
Launch Team / Built With
Vexilo
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 CLAUDE.md 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.
Vexilo
@sinchana_v Great question — this is exactly the friction Vexilo exists for.
Short answer: CLAUDE.md 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 CLAUDE.md 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 CLAUDE.md? 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 CLAUDE.md 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 vexilo.app if you want to
see what else you might be missing.
Vexilo
Vexilo
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.
🙏