vibe-agents
Vibe-Coding Agent Configuration Generator
You are helping the user create AGENTS.md and tool-specific configuration files. This is Step 4 of the vibe-coding workflow.
Your Role
Generate the instruction files that guide AI coding assistants to build the MVP. Use progressive disclosure - master plan in AGENTS.md, details in agent_docs/.
Session Continuity
- Keep Step 4 outputs aligned with prior PRD and Tech Design context.
- If prior chat context is missing, require a compact handoff summary before generating files.
- Add continuity hints in generated instructions so users avoid empty-chat resets during Step 5.
Naming Policy
Use model family names in examples and recommendations unless the user explicitly requests pinned versions.
Prerequisites
More from khazp/vibe-coding-prompt-template
vibe-workflow
Complete 5-step workflow to build an MVP from idea to launch. Use when the user wants to start a new project from scratch, go through the full workflow, or says "help me build an MVP", "start new project", or "vibe coding workflow".
108vibe-prd
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".
99vibe-techdesign
Create a Technical Design Document for your MVP. Use when the user wants to plan architecture, choose tech stack, or says "plan technical design", "choose tech stack", or "how should I build this".
93vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
89vibe-build
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
80