Part IV AI Agent Instructions

Part IV: AI Agent Instructions

Purpose

Part IV converts your PRD and Technical Design into actionable instructions that AI coding agents can use to build your MVP. It generates a universal NOTES.md file and tool-specific configuration files for various AI coding platforms.

Prerequisites

Required Files

• PRD Document (from Part II) - Required
• Technical Design Document (from Part III) - Required

Optional Files

• Research Findings (from Part I) - Provides additional context

Setup Configuration

Users must specify:

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) AI Tool Selection (Multiple Options Supported)

1. Claude Code - Terminal-based agent
2. Gemini CLI - Free terminal agent
3. Jules - Async Google agent
4. Cursor - AI-powered IDE
5. Windsurf - Beginner-friendly IDE
6. Cline - Open source VS Code extension
7. GitHub Copilot - In VS Code
8. Bolt.new / Lovable - No-code platforms

Generated Files

Universal File (Always Generated)

• NOTES.md - Universal instructions readable by all AI agents

Tool-Specific Configuration Files (Generated Based on Selection)

For Claude Code Users

• CLAUDE.md - Claude Code specific configuration
  • Behavioral directives
  • Command shortcuts
  • File operation priorities
  • Code generation preferences
  • Working modes for complex features
  • Progress tracking methods

For Cursor Users

• .cursorrules - Cursor IDE configuration
  • Code style rules
  • AI behavior rules
  • Component patterns
  • Performance guidelines
  • Security practices
  • Git commit conventions

For Windsurf Users

• .windsurfrules - Windsurf IDE configuration
  • Cascade AI behavior settings
  • Code generation rules
  • Communication style adaptation
  • Supercomplete usage guidelines
  • Chat command shortcuts

For Jules Users

• AGENTS.md - Jules async agent configuration
  • Autonomous work guidelines
  • Decision frameworks
  • PR creation guidelines
  • Audio summary formats
  • Integration points

For Gemini CLI Users

• GEMINI.md - Gemini CLI configuration
  • Project configuration YAML
  • MCP server configuration
  • Command patterns
  • Development workflow
  • Cost optimization strategies

For Cline Users

• .clinerules/config.md - Cline configuration structure
  • Multiple configuration files:
    • instructions.md - Primary directives
    • patterns.md - Code patterns
    • workflow.md - Development workflow
    • commands.md - Cline commands
    • safety.md - Safety rules
    • learning.md - Educational approach
    • project.md - Project-specific rules

NOTES.md Structure

The universal instruction file follows a strict template:

Core Sections

1. Project Overview - Context and learning goals
2. What We're Building - App purpose and tech stack
3. Setup Instructions - Prerequisites and initialization
4. Implementation Phases - Step-by-step development plan
5. Learning Resources - Technology-specific guides
6. Common Issues & Solutions - Troubleshooting
7. Code Patterns - Standard implementations
8. Testing Approach - Manual and automated testing
9. Architecture Understanding - Data flow and concepts
10. Deployment Guide - Production preparation
11. Definition of Done - MVP completion criteria

Content Adaptation by User Level

For Vibe-coders

• Simple explanations with analogies
• Step-by-step instructions
• Clear examples with comments
• Troubleshooting guides
• Celebration of progress

For Developers

• Technical specifications
• Best practices focus
• Architecture details
• Performance considerations
• Security implementations

For In-between Users

• Balanced explanations
• Learning opportunities highlighted
• Progressive complexity
• Resource recommendations
• Skill development path

Tool-Specific Features

Terminal Agents (Claude Code, Gemini CLI)

• Command shortcuts and aliases
• File operation priorities
• Error handling protocols
• Progress tracking methods
• Resource management

IDE Tools (Cursor, Windsurf)

• Code style enforcement
• Component templates
• Testing patterns
• Performance guidelines
• Security practices

Async Agents (Jules)

• Autonomous decision making
• PR creation guidelines
• Communication protocols
• Progress reporting formats

No-code Platforms (Bolt.new, Lovable)

• Simplified instructions
• Platform-specific features
• Deployment automation

Implementation Phases

All generated instructions follow a phased approach:

Phase 1: Foundation

• Project setup and environment configuration
• Basic structure creation
• Core dependencies installation
• Initial testing

Phase 2: Core Features

• Feature-by-feature implementation
• Testing after each addition
• Error handling integration
• User feedback loops

Phase 3: Polish & Deploy

• UI/UX improvements
• Performance optimization
• Production preparation
• Deployment execution

Code Patterns and Templates

Generated files include:

• Component structures for frontend frameworks
• API endpoint patterns for backend services
• Database query templates with error handling
• Testing approaches for different scenarios
• Error handling patterns for user experience

Best Practices Integration

Development Workflow

• Incremental development approach
• Regular testing and validation
• Version control practices
• Documentation maintenance

Quality Assurance

• Code review guidelines
• Testing requirements
• Performance benchmarks
• Security standards

Communication Guidelines

• Progress reporting methods
• Issue escalation procedures
• Documentation updates
• Stakeholder communication

Time Investment

• File upload and configuration: 2-3 minutes
• Instruction generation: 3-5 minutes
• Total time: 5-8 minutes

Output Structure

project-root/
├── NOTES.md                    # Universal instructions
├── [tool-specific configs]     # Based on selection
└── docs/
    ├── research-[app].txt
    ├── PRD-[app]-MVP.md
    └── TechDesign-[app]-MVP.md

Validation Checklist

Before starting development:

• All required files generated
• Tool-specific configurations match selected platforms
• Instructions align with PRD requirements
• Technical approach matches design document
• Budget and timeline constraints incorporated

Next Steps

After completing Part IV:

1. Save all generated files in project directory
2. Set up chosen AI coding agent/IDE
3. Begin development with first prompt:
   • "Read NOTES.md and begin implementing the MVP step by step"
4. Follow incremental development approach
5. Test after each feature implementation

Common Starting Prompts by Tool

Claude Code

cd your-project
claude "Read CLAUDE.md and NOTES.md, then start building the MVP"

Cursor/Windsurf

"Read NOTES.md and begin implementing the MVP step by step"

Gemini CLI

gemini "Set up the project following NOTES.md specifications"

No-code Platforms

"Build this MVP following the PRD specifications"