mcpField
V
vibe-agents

vibe-agents

github.com/khazpAgent workflows3.2k121 installsUpdated 3w ago
Repository

About vibe-agents

A project-agent skill for maintaining concise, stable repository guidance and setting up Vibe Workflow within authorized boundaries. It adapts instructions to known decisions and available files rather than requiring a full interview or setup process.

Key features

  1. 01Targeted AGENTS.md updates
  2. 02Vibe Workflow setup guidance
  3. 03Preservation of existing files
  4. 04Context-aware instruction drafting
  5. 05CLI setup checks with doctor

Use cases

  1. 01Updating repository instructions for a task
  2. 02Initializing Vibe Workflow files
  3. 03Preparing separated guidance when filesystem access is unavailable

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/khazp/vibe-coding-prompt-template --skill vibe-agents

After installing, type/vibe-agentsin Claude Code to confirm it loaded.

Details

From the project README

Project agent instructions

Use agreed requirements, technical decisions, and the existing repository to write only stable, non-obvious guidance. For a targeted AGENTS.md edit, update the affected instructions directly; do not require an installer, new PRD, or full interview. Keep progress in the project's memory/handoff file rather than the always-loaded rules.

For initial Vibe Workflow setup, use the configured manifest paths. If the vibeworkflow CLI is available, inspect npx vibeworkflow --dry-run --json and initialize within the user's authorization. Preserve existing files; replacement flags are for intentional replacements whose affected files have been reviewed. The CLI installs files directly, not into a new templates/ directory.

Fill relevant placeholders from known decisions. Keep task-specific procedures in skills or references and load them only when relevant. Distinguish local implementation from external sends, production changes, and new access. Do not enable broad tool permissions just to make setup convenient.

Use npx vibeworkflow doctor for CLI-generated setup when available; it checks configuration, not a working build or user journey. In a chat without filesystem access, use the repository's docs/context-pack.md and supplied product decisions to produce separated files to save. State absent template/context limitations instead of inventing them. Continue into implementation only when that is part of the user's request.

Comments

Markdown supported