A collection of battle-tested initialization prompts for working with AI coding assistants. These prompts implement systematic methodologies to prevent AI eagerness and ensure high-quality, verified code development.
AI assistants have a fundamental tendency toward over-eagerness - rushing to implement solutions, adding unrequested features, and claiming completion without verification. This repository provides initialization prompts that channel this eagerness into productive, verified progress through systematic human-AI collaboration.
Read universal-principles.md
for a complete understanding of the methodology these prompts implement.
Core Principle: "Measure Twice, Cut Once"
ai-initialization-prompts/
├── README.md
├── universal-principles.md
├── browser-based/
│ ├── 01-initialization-comprehensive.md
│ ├── 01-initialization-condensed.md
│ ├── 02-new-project.md
│ ├── 02-analyze-codebase.md
│ ├── 02-refactor-existing.md
│ └── 02-debug-investigation.md
├── ide-based/
│ ├── 01-initialization.md
│ ├── 02-new-project.md
│ └── 02-analyze-codebase.md
└── specialized/
├── rapid-prototyping.md
└── documentation-writing.md
(some files are missing b/c this project is a wip
- Start a new conversation
- Copy and paste the entire
01-initialization
prompt (comprehensive or condensed based on preference) - Wait for the AI's acknowledgment
- Copy and paste the appropriate
02-
prompt for your specific task - Provide your project details where indicated in the Step 2 prompt
- Start a new session
- Copy and paste the appropriate initialization prompt
- Follow with your task-specific prompt
All prompts implement eight universal principles:
- Permission-Based Action
- Evidence Over Assertions
- Systematic Progression Through Living Documentation
- Transparent Limitations
- Critical Thinking Over Agreement
- Quality Through Review Layers
- No Time Estimates
- Collaboration Over Completion
- Step 1: Establishes working principles and prevents eagerness
- Step 2: Introduces specific task with appropriate constraints
Instead of "fixing" problems, the AI investigates systematically to understand issues before proposing changes.
Every project begins with a detailed game plan that serves as the single source of truth throughout development.
- Comprehensive: Full principles and detailed workflow (~1500 words)
- Condensed: Essential principles and workflow (~500 words)
- New Project: Starting from scratch with full planning
- Analyze Codebase: Understanding existing code before modifications
- Refactor Existing: Systematic improvement of working code
- Debug Investigation: Scientific approach to troubleshooting
- Always use Step 1 first - Never skip initialization
- One task at a time - Complete projects systematically
- Verify everything - The human verifies, the AI suggests
- Update game plans - Mark progress and learnings
- Investigate, don't fix - Understand problems before solving
- ❌ Jumping straight to task description without initialization
- ❌ Asking AI to "fix" problems (triggers eagerness)
- ❌ Proceeding without verification
- ❌ Accepting time estimates from AI
- ❌ Skipping the game plan phase
These prompts are battle-tested through real development work. Contributions should:
- Follow the established philosophical framework
- Include concrete examples from actual usage
- Maintain the focus on preventing AI eagerness
- Provide clear documentation
Copyright (c) 2025 Dennis Porter
This project is licensed under the MIT License - see the LICENSE file for details.
These prompts were developed through extensive real-world AI-assisted development, learning from both successes and failures in human-AI collaboration.
Created by Dennis Porter - dennismars.com