Practical AI Coding Strategies from 1000 Hours of Experience

AI Prompting Levels and Workflow Strategies

A Reddit post from r/ClaudeAI shares practical strategies for using AI coding agents based on 1000 hours of experience. The core recommendation is to stop treating AI like an architect and instead treat it like a junior developer—discuss what you want to build and let the AI find edge cases before implementation starts.

Three Prompting Levels

The source defines three distinct prompting approaches:

• Level 1 (Noob): Asking the AI to build the entire app in one go (e.g., "Build me a competitor pricing tracker"). The AI makes all design and tech stack decisions, resulting in completely unusable output.
• Level 2 (Intermediate): Providing features and capabilities but leaving out technical architecture. The AI has to guess edge cases, resulting in somewhat usable but not production-ready output.
• Level 3 (Pro): Figuring out the entire Product Requirement Document (PRD) with the AI agent first. Define core logic, user personas, step-by-step flows, and rigid technical architecture (e.g., Supabase with Postgres and Prisma). Ask the AI to poke holes in the logic before writing any code.

Implementation Strategies

The post recommends several concrete workflow practices:

• Phase the implementation: Never ask the AI to code the whole app at once. Ask it to create a phased plan with clear deadlines and deliverables for each step.
• Break down complex tasks: If the AI has too much to do, it will skip crucial decision-making steps and guess incorrectly. You need to make core product decisions, not the AI.
• Control your own design: Never let the AI decide your design language. Build out user flows and wireframes yourself, otherwise the AI will generate generic dashboards that don't fit your product.
• Use a strict instruction file: Create an agent.md (or cloud.md) file to define product structure, coding style, error handling, and restricted commands (e.g., explicitly telling it never to run database migrations) so you don't have to repeat yourself in every prompt.

These strategies emphasize that developers should maintain control over architecture and design decisions while leveraging AI for implementation and edge case discovery.