> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slashvibe.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Contributing

> What is public now and where help is useful.

## Public now

The documentation source is public at
[`VibeCodingInc/docs`](https://github.com/VibeCodingInc/docs). Corrections that make setup,
limits, or first use clearer are welcome as pull requests.

Vibe Buddy's signed binaries and release notes are public at
[`VibeCodingInc/vibe-buddy-releases`](https://github.com/VibeCodingInc/vibe-buddy-releases).

## Terminal client source

`slashvibe-mcp` is open source. Its public **source-of-record** is
[`VibeCodingInc/vibe-mcp`](https://github.com/VibeCodingInc/vibe-mcp): the npm package
(0.8.17) is built and published from there, and that is where client changes are proposed
and reviewed. Contribute there directly — file issues and open pull requests against
`vibe-mcp`.

## Platform source

The production platform repository remains private today. It mixes product code for the
hosted identity and messaging service with migrations, deployment configuration, internal
operations, and unrelated company history. Production data, credentials, certificates,
legal records, and fleet state belong to the separate private operating estate.
Opening the terminal client does not expose that estate.

## Good first contributions

* reproduce first-time setup on a clean machine and report the exact step that was unclear
* improve an instruction only when the product actually behaves that way
* add a regression test for a user-visible failure
* remove a second definition rather than updating two copies

Please do not propose a new transport, social feed, directory, or delivery claim as an
onboarding fix. `/vibe` is currently testing one loop: message someone from your terminal,
then receive a useful reply.