vibe-agents
Skill1 starsChanged 8 months agoMITView on GitHub
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".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- KhazP/vibe-coding-prompt-templatetheir own version, first seen Sep 10, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- KhazP/vibe-coding-prompt-template★ 3.1ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- vibe-buildSkill
- vibe-prdSkill
- vibe-researchSkill
- vibe-techdesignSkill
- vibe-workflowSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Keep Step 4 outputs aligned with prior PRD and Tech Design context.
- Distinctive: line 18
If prior chat context is missing, require a compact handoff summary before generating files.
- Distinctive: line 19
Add continuity hints in generated instructions so users avoid empty-chat resets during Step 5.
- Distinctive: line 23
Use model family names in examples and recommendations unless the user explicitly requests pinned versions.
- Very specific: line 27
Look for docs/PRD-*.md - REQUIRED
- Distinctive: line 29
If either is missing, suggest running the appropriate skill first
- Distinctive: line 73
Create the following structure:
- Very specific: line 185
Prefer .cursor/rules/ for modern Cursor setups.
- Distinctive: line 231
testing.md: Test strategy, tools, verification loop, pre-commit hooks
- Distinctive: line 235
Write all files to the project, then tell the user:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Look for
docs/PRD-*.md- REQUIRED - Look for
docs/TechDesign-*.md- REQUIRED - If either is missing, suggest running the appropriate skill first
Step 1: Load Context
Extract from documents:
From PRD:
- Product name and description
- Primary user story
- All must-have features
- Nice-to-have and excluded features
- Success metrics
- UI/UX requirements
- Timeline and constraints
From Tech Design:
- Complete tech stack
- Project structure
- Database schema
- Implementation approach
- Deployment platform
- AI tool recommendations
Step 2: Ask Configuration Questions
Ask the user:
Which AI tools will you use? (Select all that apply)
- Claude Code (terminal-based)
- Gemini CLI (free terminal agent)
- Google Antigravity / equivalent (agent-first IDE)
- Cursor (AI-powered IDE)
- VS Code + GitHub Copilot
- Lovable / v0 (no-code)
Then ask:
What's your technical level?
- A) Vibe-coder
- B) Developer
- C) In-between
Step 3: Generate Files
Create the following structure:
project/
├── AGENTS.md # Master plan
├── agent_docs/
│ ├── tech_stack.md # Tech details
│ ├── code_patterns.md # Code style
│ ├── project_brief.md # Persistent rules
│ ├── product_requirements.md # PRD summary
│ └── testing.md # Test strategy
├── CLAUDE.md # If Claude Code selected
├── GEMINI.md # If Gemini/agent-first IDE selected
├── .cursor/rules/ # If Cursor selected (preferred)
├── .cursorrules # Cursor legacy fallback
└── .github/copilot-instructions.md # If Copilot selectedAGENTS.md Template
# AGENTS.md - Master Plan for [App Name]
## Project Overview
**App:** [Name]
**Goal:** [One-liner]
**Stack:** [Tech stack]
**Current Phase:** Phase 1 - Foundation
## How I Should Think
1. **Understand Intent First**: Identify what the user actually needs
2. **Ask If Unsure**: If critical info is missing, ask before proceeding
3. **Plan Before Coding**: Propose a plan, get approval, then implement
4. **Verify After Changes**: Run tests/checks after each change
5. **Explain Trade-offs**: When recommending, mention alternatives
## Plan -> Execute -> Verify
1. **Plan:** Outline approach, ask for approval
2. **Execute:** One feature at a time
3. **Verify:** Run tests/checks, fix before moving on
## Context Files
Load only when needed:
- `agent_docs/tech_stack.md` - Tech details
- `agent_docs/code_patterns.md` - Code style
- `agent_docs/project_brief.md` - Project rules
- `agent_docs/product_requirements.md` - Requirements
- `agent_docs/testing.md` - Test strategy
## Current State
**Last Updated:** [Date]
**Working On:** [Task]
**Recently Completed:** None yet
**Blocked By:** None
## Roadmap
### Phase 1: Foundation
- [ ] Initialize project
- [ ] Setup database
- [ ] Configure auth
### Phase 2: Core Features
- [ ] [Feature 1 from PRD]
- [ ] [Feature 2 from PRD]
- [ ] [Feature 3 from PRD]
### Phase 3: Polish
- [ ] Error handling
- [ ] Mobile responsiveness
- [ ] Performance optimization
### Phase 4: Launch
- [ ] Deploy to production
- [ ] Setup monitoring
- [ ] Launch checklist
## What NOT To Do
- Do NOT delete files without confirmation
- Do NOT modify database schemas without backup plan
- Do NOT add features not in current phase
- Do NOT skip tests for "simple" changes
- Do NOT use deprecated librariesTool Config Templates
CLAUDE.md (Claude Code)
# CLAUDE.md - Claude Code Configuration
## Project Context
**App:** [Name]
**Stack:** [Stack]
**Stage:** MVP Development
## Directives
1. **Master Plan:** Read `AGENTS.md` first for current phase and tasks
2. **Documentation:** Refer to `agent_docs/` for details
3. **Plan-First:** Propose plan, wait for approval
4. **Incremental:** One feature at a time, test frequently
5. **Concise:** Be brief, ask clarifying questions when needed
## Commands
- `npm run dev` - Start server
- `npm test` - Run tests
- `npm run lint` - Check code styleCursor Rules (Cursor)
Prefer .cursor/rules/ for modern Cursor setups. Use .cursorrules only as a fallback.
# Cursor Rules for [App Name]
## Project Context
**App:** [Name]
**Stack:** [Stack]
**Stage:** MVP Development
## Directives
1. Read `AGENTS.md` first
2. Refer to `agent_docs/` for details
3. Plan before coding
4. Build incrementally
5. Test frequently
## Commands
- `npm run dev` - Start server
- `npm test` - Run testsGEMINI.md (Gemini CLI / Agent-First IDE)
# GEMINI.md - Gemini Configuration
## Project Context
**App:** [Name]
**Stack:** [Stack]
## Directives
1. Read `AGENTS.md` first
2. Use `agent_docs/` for details
3. Plan, then execute
4. Build incrementallyagent_docs/ Files
Generate each file with content from PRD and Tech Design:
- tech_stack.md: List every library, version, setup commands, code examples
- code_patterns.md: Naming conventions, file structure, error handling patterns
- project_brief.md: Product vision, coding conventions, quality gates, key commands
- product_requirements.md: Core requirements, user stories, success metrics
- testing.md: Test strategy, tools, verification loop, pre-commit hooks
After Completion
Write all files to the project, then tell the user:
Files Created:
AGENTS.md- Master planagent_docs/- Detailed documentation- [Tool-specific configs based on selection]
Project Structure:
your-app/ ├── docs/ │ ├── research-[App].txt │ ├── PRD-[App]-MVP.md │ └── TechDesign-[App]-MVP.md ├── AGENTS.md ├── agent_docs/ │ ├── tech_stack.md │ ├── code_patterns.md │ ├── project_brief.md │ ├── product_requirements.md │ └── testing.md └── [tool configs]Next Step: Run
/vibe-buildto start building your MVP, or say "Build my MVP following AGENTS.md"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

