VBW integrates with skills.sh — an open-source skill registry for AI agents with 20+ supported platforms and thousands of community-contributed skills. Skills teach your agents framework conventions, project patterns, and best practices for your specific tech stack.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/swt-labs/vibe-better-with-claude-code-vbw/llms.txt
Use this file to discover all available pages before exploring further.
How VBW integrates with skills.sh
Skills enter your project at three points:- Automatic detection on init —
/vbw:initscans your project, identifies your tech stack, and recommends relevant skills from a curated mapping. You get targeted suggestions based on what’s actually in your codebase. - On-demand discovery —
/vbw:skillslets you browse installed skills, view curated suggestions, and search the full registry at any time. - Agent injection — installed skills are automatically injected into every agent’s context via the SubagentStart hook. Agents use them without any extra prompting.
Using /vbw:skills
/vbw:skills with no arguments, it:
- Displays your currently installed skills (global and project-scoped)
- Shows your detected stack
- Presents curated suggestions for skills you haven’t installed yet
- Searches the live registry for additional matches
- Prompts you to select and install skills in one step
~/.agents/skills/) or scoped to the current project (./.claude/skills/). VBW asks which scope to use before installing.
Configuration options
| Setting | Default | Description |
|---|---|---|
skill_suggestions | true | Show skill suggestions during /vbw:init |
auto_install_skills | false | Install detected skills without prompting |
discovery_questions | true | Ask discovery questions to refine suggestions |
/vbw:config:
Supported stacks
VBW ships with curated skill mappings for the following stacks. When your project matches one of these, VBW recommends the right skills automatically. Languages| Stack | Detected from |
|---|---|
| Python | pyproject.toml, requirements.txt, setup.py |
| Rust | Cargo.toml |
| Go | go.mod |
| Elixir | mix.exs |
| Java | pom.xml, build.gradle |
| .NET | *.csproj, *.sln |
| Ruby | Gemfile, *.gemspec |
| PHP | composer.json |
| Kotlin | build.gradle.kts |
| Deno | deno.json, deno.lock |
| Bun | bun.lockb, bunfig.toml |
| Stack | Detected from |
|---|---|
| Next.js | next.config.js, next.config.mjs |
| React | package.json (react dependency) |
| Vue.js | vue.config.js, package.json (vue) |
| Svelte / SvelteKit | svelte.config.js |
| Angular | angular.json, @angular/core |
| Astro | astro.config.mjs |
| Remix | remix.config.js |
| Nuxt.js | nuxt.config.ts |
| NestJS | nest-cli.json, @nestjs/core |
| SolidJS | package.json (solid-js) |
| Express | package.json (express) |
| Django / FastAPI / Flask | requirements.txt or pyproject.toml |
| Ruby on Rails | config/routes.rb, Gemfile |
| Laravel | artisan, composer.json |
| Spring Boot | pom.xml or build.gradle (spring-boot) |
| Phoenix | mix.exs (phoenix) |
| Prisma | prisma/schema.prisma |
| Tailwind CSS | tailwind.config.js |
| TypeScript | tsconfig.json |
Adding skills manually
Skills are Markdown files stored in your skills directory. To add a skill outside the registry:- Create a
.mdfile in.claude/skills/(project scope) or~/.agents/skills/(global) - Write your skill as instructions an agent would follow
- Skills take effect immediately — no restart needed
Teaching project-specific conventions
For conventions that aren’t in the public registry, use/vbw:teach:
- Injected into every agent’s context via
CLAUDE.md - Verified by QA against completed work
- Auto-detected from your codebase patterns during
/vbw:init
/vbw:teach with no arguments opens an interactive prompt that scans your codebase and surfaces conventions worth capturing.
Working with existing codebases
How brownfield init, codebase mapping, and session resumption work.
Supporting commands
Full reference for /vbw:skills, /vbw:teach, /vbw:doctor, and more.