# ==AI Prompt Guide for Development==

### This guide helps ensures structured AI-assisted development with proper planning and debugging workflows.==
==

* * *

## Start a New Chat

### Give the AI context to the as small as possible, but fully outlines entire project right off the bat. This helps it know context to your questions and requests. (Review `README.md` File)

```
Please review @README.md to understand the project.

But first, the @README.md is a large file, chunk it up so you can digest it more easily.
once you've processed all the chunks and the entire @README.md file go ahead and poke around the codebase too.

Once you understand everything say: What shall we do?
```

* * *

## Wrap up a Chat

### Have the AI fully update the project context file. (Update `README.md` File)

### Watch this file carefully, like a hawk! IT IS YOUR PROJECT LIFE BLOOD!

```
Please review @README.md as it hasn't been updated with the latest changes we've made. Review our chat we had and code changes carefully and figure out everything we changed, removed, updated, etc. Make a comprehensive list and then update the @README.md accordingly.

VERY IMPORTANT: Do not remove anything from the README unless its no longer accurate. Also, do not add anything that isn't actually known to be true. No guessing, just the facts.

Go ahead and review everything as instructed then update the README now.
```

* * *

## Writing a New Feature

### <span style="color: #3598db;">Have the AI add a new "large" feature. (`README.md` Already in Context)</span>

```
We need to focus on ((@DIRECTORY/@PAGE))

It's time to build a new feature: ((DESCRIBE FEATURE))

Please review the codebase and start planning what we need to do here.

Don't write any code, just explain your plan thoroughly to me.
```

* * *

## Implementing Features - Planning

### Break "large" features into manageable chunks for the AI to be successful!

### After Pass 1, do Pass 2 and so on. The larger the feature the more "main" passes you need. If "very large" you need more than this prompt alone can solve for - it needs to be structured in sub features first by you, basically.

### Once you're aligned with the AI's plan for each pass, tell it to proceed. (It's always itching to write code not chat!)

```
Before you proceed, break this up into logical chunks. don't bite off more than you can chew with one pass. Let's break this up into 2 main "passes". explain what you will be doing in each pass, from a high level.
```

- **Pass 1 - Code Review and Planning**

    ```
    Review the code and files for Pass 1

    Once you have reviewed, outline exactly what you need to do in detail. Don't code yet, we're just planning.
    ```


* * *

## Bug Fixing (`README.md` Must Be Up to Date)

### <span style="color: #3598db;">Give AI full context of your app/code then have it tell your the plan! (`README.md` Must Be Up to Date)</span>

**<span style="color: #3598db;">Once you're aligned with the AI's plan, tell it to proceed.</span>**

```
I need your help fixing something. Please review @README.md and understand the entire project.

The bug: ((DESCRIBE BUG))

Please review the code that pertains to this. do deep discovery and research around this issue. then report back your findings.

Do NOT write any code, just explain in English for now.
```

* * *