Part 4 — Generate AGENTS.md and AI Agent Configuration Files

Part 4 — Generate AGENTS.md and AI Agent Configuration Files

I'll help you create the instruction files that will guide your AI coding assistant to build your MVP. These files are what make the magic happen!

Required Documents — Please Attach

Required:

1. PRD Document (from Part 2) — Defines WHAT to build
2. Technical Design Document (from Part 3) — Defines HOW to build

Optional but Helpful:

• Research Findings (from Part 1) — Additional context

Attach these in any format (.txt, .pdf, .docx, .md) or paste if short.

After attaching your files, confirm your setup:

**A) Technical Level:**

• A) Vibe-coder — AI does everything, I guide and test
• B) Developer — I code with AI assistance
• C) Somewhere in between — Learning while building

**B) Which AI Tool(s) Will You Use?** (Can select multiple)

1. Claude Code — Terminal-based agent with session memory
2. Gemini CLI — Free terminal agent
3. Google Antigravity / equivalent — Agent-first IDE (availability may vary)
4. Cursor — AI-powered IDE
5. VS Code + GitHub Copilot — IDE with AI extension
6. Lovable / v0 — No-code platforms

Please attach files and type: A/B/C and tool numbers (e.g., "A, 1,4"):

---

Instructions for AI Assistant

Generation Rules & Logic

Your Goal

You are an expert Tech Lead setting up a **Progressive Disclosure** documentation system for an AI Agent. Your output must be **modular** to prevent context window overload.

1. Master Plan (AGENTS.md): High-level context, roadmap, and active state.
2. Detailed Docs (agent_docs/): Specific implementation details.
3. Tool Configs: Concise pointers to the above.

Content Extraction Guidelines

• From PRD: Extract exact feature names, user stories, success metrics, and constraints.
• From Tech Design: Extract exact tech stack, architecture decisions, and implementation approaches.
• Language Level: Adjust explanations in agent_docs/ based on user's technical level (A/B/C).
  • Level A (Vibe-coder): Explain concepts simply, focus on "what to do next".
  • Level B (Developer): Focus on architecture, patterns, and best practices.
• Be Specific: Replace all bracketed placeholders with actual project details.
• Keep Examples: Include code examples with comments explaining the "why".

High-Order Prompts (Meta-Cognition)

Include these behavioral instructions in AGENTS.md to improve agent reasoning:

## How I Should Think
1. **Understand Intent First**: Before answering, identify what the user actually needs
2. **Ask If Unsure**: If critical information is missing, ask before proceeding
3. **Plan Before Coding**: Propose a plan, ask for approval, then implement
4. **Verify After Changes**: Run tests/linters or manual checks after each change
5. **Explain Trade-offs**: When recommending something, mention alternatives