VI

vibe-agents

Generates instruction files from project documentation to standardize AI coding agent configurations.

Install

mkdir -p .claude/skills/vibe-agents && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2350" && unzip -o skill.zip -d .claude/skills/vibe-agents && rm skill.zip

Installs to .claude/skills/vibe-agents

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Generate AGENTS.md and AI configuration files for your project. Use when the user wants to create agent instructions, set up AI configs, or says "create AGENTS.md", "configure my AI assistant", or "generate agent files".
220 chars✓ has a “when” trigger
Beginner

Key capabilities

  • →Generate AGENTS.md instruction files
  • →Extract context from PRDs and design docs
  • →Configure AI-specific behavior settings
  • →Maintain AI session continuity

How it works

It parses architectural and requirement documents to programmatically assemble instruction sets for secondary AI agents.

Inputs & outputs

You give it
Project documentation (PRD/TechDesign)
You get back
AGENT.md and configuration files

When to use vibe-agents

  • →Initialize project-specific AI instructions
  • →Create AGENTS.md from existing design docs
  • →Configure AI assistant behaviors for new features
  • →Sync AI instructions with project structure

About this skill

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.

When not to use it

  • →Writing feature implementation code
  • →Drafting marketing copy for the project

Prerequisites

PRD fileTech Design document

Limitations

  • →Highly dependent on the presence of PRDs and Tech Designs
  • →Requires user to provide technical level for output calibration

How it compares

It automates the creation of 'system prompts' based on documented project context, reducing manual setup time for new features.

Compared to similar skills

vibe-agents side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
vibe-agents (this skill)35moNo flagsBeginner
skill-name09moReviewAdvanced
skill-creator1285moReviewAdvanced
skill-development1710moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry