Skip to main content
If you are stuck, there are several ways to get help.

​
GitHub

The primary support channel is GitHub. The repository is at github.com/a7ul/vibes.

Open an Issue

Report a bug or unexpected behaviour. Include a minimal reproducible example and the Vibes version you are using.

Start a Discussion

Ask a question, share a pattern, or propose a feature. Discussions are the right place for open-ended topics.

​
Reporting a bug

Good bug reports get fixed faster. Include:
  1. Vibes version — run deno eval "import pkg from 'jsr:@vibesjs/sdk/package.json' assert { type: 'json' }; console.log(pkg.version)" or check deno.json.
  2. Minimal reproduction — the smallest piece of code that triggers the issue.
  3. Expected vs actual behaviour — what you expected to happen and what actually happened.
  4. Environment — Deno or Node.js, OS, TypeScript version.

​
Agent skill for Claude Code

If you use Claude Code, the @vibesjs/sdk agent skill gives your coding assistant complete, up-to-date knowledge of the framework API. Install it once and Claude Code will write idiomatic Vibes code without needing to look things up. 
# Project-level (recommended)
mkdir -p .claude/agents && curl -fsSL \
  https://raw.githubusercontent.com/a7ul/vibes/main/packages/sdk/skills/vibes-sdk.md \
  -o .claude/agents/vibes-sdk.md
See the Agent Skill page for global install, manual setup, and details.

​
Common issues

Before opening an issue, check the Troubleshooting page — it covers the most frequent setup problems, error classes, and Zod schema mistakes.