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

vibe-agents

GitHub

基于PRD和技术设计生成Agent指令文件，通过CLI验证环境并填充占位符，支持无文件访问模式及上下文打包。

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

Trigger Scenarios

需要生成AI编程助手配置指令初始化Vibe工作流环境

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/.agents/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": "Generate project agent instructions from agreed requirements and technical decisions. Not for ordinary incremental feature changes.",
    "allowed-tools": "Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion"
}

Vibe Agents

Read the agreed PRD and Tech Design using vibe.project.json paths when available; otherwise inspect docs/PRD--MVP.md and docs/TechDesign--MVP.md. Reconcile conflicts and reuse Handoff Context before asking anything.

Run npx vibeworkflow --dry-run --json to inspect setup changes, then initialize within existing authorization. Existing files are preserved by default. Use --force only for explicitly intended replacement after showing affected files. The CLI installs selected files directly; it does not create a templates/ directory.

Fill required placeholders from decisions. AGENTS.md contains stable rules; MEMORY.md contains current progress; agent_docs contains concise build context. Run npx vibeworkflow doctor and resolve required setup errors. Build and behavior remain Not checked.

For a chat without filesystem access, use the repository's downloadable docs/context-pack.md plus the user's product documents; output clearly separated files to save. Do not invent absent template content. Tool configurations follow the installed client's supported settings; do not enable broad permissions automatically.