Agent Skills › KhazP/vibe-coding-prompt-template › vibe-agents

vibe-agents

GitHub

根据产品和技术决策生成项目代理指令与工具配置，初始化 Vibe Workflow 环境，编写稳定的 AGENTS.md 指导文件。

templates/.claude/skills/vibe-agents/SKILL.md KhazP/vibe-coding-prompt-template

Trigger Scenarios

需要创建或更新项目代理指令初始化 Vibe Workflow 配置基于现有决策生成 Agent 文档

Install

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents -g -y

More Options

Non-standard path

npx skills add https://github.com/KhazP/vibe-coding-prompt-template/tree/main/templates/.claude/skills/vibe-agents -g -y

Use without installing

npx skills use KhazP/vibe-coding-prompt-template@vibe-agents

指定 Agent (Claude Code)

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents -a claude-code -g -y

安装 repo 全部 skill

npx skills add KhazP/vibe-coding-prompt-template --all -g -y

预览 repo 内 skill

npx skills add KhazP/vibe-coding-prompt-template --list

SKILL.md

Frontmatter

{
    "name": "vibe-agents",
    "description": "Create project agent instructions and tool configuration from agreed product and technical decisions.",
    "allowed-tools": "Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion"
}

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.