Vibe Setup banner
is52hertz is52hertz

Vibe Setup

Testing community

Description

A small Bash CLI that bootstraps a project for AI-assisted development: seeds AGENTS.md/CLAUDE.md, a secrets-deny Claude Code settings file, and a manual test checklist, with optional git init and Trellis setup.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Vibe-Setup

A small Bash CLI that bootstraps a project for AI-assisted development. It seeds a shared set of AI-agent instruction files (`AGENTS.md`, `CLAUDE.md`), a secrets-deny Claude Code settings file, and a manual test checklist — and can optionally install and initialize [Trellis](https://www.npmjs.com/package/@mindfoldhq/trellis). The files under `templates/` are the source of truth the script copies from.

Why

Every new project needs the same baseline so AI coding assistants behave consistently: one source of truth for product rules and coding standards, a guardrail that keeps agents from reading secrets, and a place for handoff notes. `vibe-init` lays that down in one step, for a brand-new project or an existing one.

Requirements

  • Bash — works on the system Bash that ships with macOS (3.2+).
  • git — optional; only needed for the git init step.
  • Trellis (optional) — Node.js 18+, npm, and Python 3.9+.

Install

git clone https://github.com/is52hertz/Vibe-Setup.git
cd Vibe-Setup

# Run it directly,
./vibe-init.sh

# …or put it on your PATH:
ln -s "$PWD/vibe-init.sh" ~/.local/bin/vibe-init

The script resolves symlinks, so it always finds its sibling `templates/` directory even when invoked through a symlink on your `PATH`.

Usage

Scaffold a new project

Run inside an empty directory (it initializes in place) or a non-empty one (it creates a project subfolder):

vibe-init
# or, in a non-empty directory, name the project directly:
vibe-init my-project

You will be asked whether to `git init` the project (default **yes**) and whether to install/initialize Trellis (default **no**); then the template files are copied in.

Seed an existing project

vibe-init --apply

`--apply` lists the managed files with their status and lets you copy **all or a subset**. Existing files are never overwritten or merged — when a target already exists, the copy lands alongside it as `.template` instead.