AI-Assisted Development Workflow

In the previous chapters, we learned how to use AI IDEs to write code, how to manage code versions with Git, and how to design and implement API interfaces. But when you face a real development task, you may run into questions like these:

• "This project has thousands of files. Where should I start?"
• "My boss asked me to add a new feature, but I'm not familiar with this part of the codebase."
• "I have no idea where this bug is. There is just too much code."
• "I need to refactor this pile of code, but I'm afraid of breaking something."

The essence of these questions is: how do you use AI tools efficiently in real development scenarios to get work done?

In this lesson, we will learn how to build a systematic AI-assisted development workflow so that you can use AI efficiently across different development scenarios. Through concrete examples, we will show how to use AI in new feature development, bug fixing, code refactoring, and more.

💡 Prerequisites

Before studying this section, it is recommended that you first understand:

• AI IDE Basics - master the basic use of AI IDEs
• Git and GitHub Workflow - understand code version management
• Using Large Models to Help Write API Code - understand the basic concept of AI-assisted development

📚 What you will learn

1. Understand AI's role in the development process and its capability boundaries
2. Master AI-assisted development strategies for different project types
3. Learn how to use Claude Code in scenarios such as new feature development, bug fixing, and code refactoring
4. Build a project knowledge base to improve collaboration efficiency with Claude Code
5. Master practical techniques for improving AI collaboration efficiency

1. Understand AI's Capability Boundaries

Before we start using AI to assist development, we first need to understand what AI can and cannot do. Only then can we build the right collaboration model.

1.1 What AI Is Good At

Think of AI as a very smart assistant that still needs clear instructions. It can quickly generate a code skeleton based on your description, and it can also read thousands of lines of code in seconds to find the part you need. If there are obvious syntax errors or common security vulnerabilities, it can help you discover them too. Repetitive tasks such as batch-renaming variables, formatting code, and generating documentation comments are especially suitable to hand over to AI.

Put simply, AI is good at work that has clear rules and can be automated.

1.2 What AI Is Not Good At

But AI also has its limitations. It does not understand your business logic. Unless you tell it in detail, it will not know how your company's order flow works. It also cannot make decisions such as technical selection or architecture design that require weighing trade-offs, because those depend on your experience and understanding of the project. AI also does not know your team's special conventions, such as "all APIs must have logging" or "error codes must use enums." You need to configure those rules or tell it explicitly.

Most importantly, code generated by AI cannot be used directly. You must review and test it. It may generate code that looks correct but is actually problematic, and it may ignore certain edge cases.

1.3 How to Collaborate with AI

Once you understand AI's capability boundaries, the collaboration model becomes clear: you are responsible for deciding what to build, making decisions, and ensuring quality; AI is responsible for executing concrete coding work, finding information, and surfacing obvious problems.

It is like working with a junior developer. You tell them what needs to be done, they implement it, and then you review the code. The difference is that AI executes much faster, but its judgment is weaker than a human's.

2. Development Strategies for Different Project Types

Different types of projects require different development styles and AI usage strategies. Choosing the right strategy can greatly improve development efficiency.

2.1 Brand-New Projects (Starting from Scratch)

Project characteristics:

• No historical baggage, so you can design freely
• You need to establish project structure and code conventions
• Suitable for fast iteration and trial-and-error

Recommended workflow:

Step 1: Plan the project structure

Before you start coding, first ask AI to help you plan the project structure and technical choices:

I want to build a task management app with these features:
- User registration and login
- Create, edit, and delete tasks
- Task categories and tags
- Task reminders

Please help me:
1. Recommend a suitable tech stack
2. Design the project directory structure
3. Plan the database schema

Step 2: Build the basic framework

Based on the plan, ask AI to create the basic project structure:

Based on the plan we just discussed, help me:
1. Create the project directory structure
2. Initialize config files (package.json, .env, etc.)
3. Create the basic server code

Step 3: Implement features one by one

Implement feature modules one at a time by priority:

Now implement the user registration feature with these requirements:
- Register with email and password
- Store passwords in encrypted form
- Email verification

Key points:

• Establish code conventions early so AI generates code that follows them
• Test and verify every feature module as soon as it is completed
• Keep project documentation updated in time

2.2 Mature Projects (Large Existing Codebases)

Project characteristics:

• Large codebase with historical conventions
• You need to keep coding style consistent
• Changes must consider the scope of impact

Recommended workflow:

Step 1: Understand the project structure

Before changing code, first ask AI to help you understand the project:

This is an e-commerce project, and I need to add a coupon feature.
Please help me:
1. Analyze the overall project structure
2. Find the order-related code
3. See how other similar features are implemented

Step 2: Find reference code

Ask AI to find similar implementations in the project as references:

Find how other promotional features in the project, such as full reduction and discounts, are implemented

Step 3: Follow the existing style

Ask AI to implement the new feature in the style of the existing code:

Please implement the coupon feature by referring to how the full-reduction promotion is implemented.
Keep the same code style and directory structure.

Key points:

• Understand first, then change things, so you do not damage the existing architecture
• Keep coding style consistent
• Test related functionality after the change

2.3 Rapid Prototypes (Validating Ideas)

Project characteristics:

• Speed matters most, code quality matters less
• Used to validate product ideas or technical approaches
• May later be discarded or rewritten

Recommended workflow:

Describe the requirement directly and implement quickly:

Build a simple todo app with these requirements:
- Add, delete, and mark tasks as completed
- Store data locally
- Keep the UI simple, as long as it works

Iterate quickly:

Add search
Switch it to a dark theme
Add task categories

Key points:

• Do not worry too much about code quality or conventions
• Validate ideas quickly and adjust direction in time
• If the prototype succeeds, it will need refactoring later

2.4 Maintenance Projects (Mostly Bug Fixes)

Project characteristics:

• The code is already stable, and the main task is fixing issues
• You need to locate problems quickly
• Changes must be made carefully to avoid introducing new issues

Recommended workflow:

Step 1: Locate the problem

User feedback: after clicking the "Submit Order" button, the page freezes
Console error: TypeError: Cannot read property 'id' of undefined

Please help me:
1. Analyze possible causes
2. Find the relevant code

Step 2: Analyze the root cause

Check in what situations this error occurs
Inspect the data flow

Step 3: Apply the fix

Fix this problem, and:
1. Add defensive code to avoid similar issues
2. Add error messages to improve user experience

Key points:

• Test thoroughly after the fix to ensure it does not affect other functionality
• Add defensive code to improve system robustness
• Record the problem and solution for future reference