Thread by @HotepJesus

I don't know how to code...

Never knew how to code mobile apps...

But I literally launched my first iPhone app last week using AI.

(No, you CANNOT build a 'good' app in five minutes)

Here's what I learned in the process: 🧵

After breaking my code base the first time I realized that I should make a back up folder.

After corrupting the back up code base I realized that I need multiple back ups.

So, after every major change I make a backup and name it after the major change.

My backup folder now has a multitude of files from previous backups.

Before we continue, here's the app I built.



I created it to solve a problem I had with other workout log apps.

It takes too long to find the exercise in the app, or the app doesn't have the exercise, or uses a different name.

So, I solved this problem. Fitboy.app

If the AI hallucinates, that's not an AI problem.

That's a YOU problem (user error).

To resolve this you need SPECIFIC instructions!

Before we get to specifics, let's talk brevity and protocols.

For every new change, start a new chat.

Previous conversations in the same chat WILL cause the AI to perform unintended actions.

Keeps your chats BRIEF!

Protocols:

There are two main types of protocols: Bugs & Updates

You can find these on the web or create your own.

If you want to eliminate hallucinations then you NEED protocols!

🖌️Update protocols:

Create your own protocols using AI.

Ask the AI to create a protocol for your programming language with the below parameters to reduce hallucinations.

1. Understand Request & Validate Context
2. Analysis, Design & Planning (understand existing codebase)
3. Propose Implementation Plan (User Confirmation Required)
4. Implementation & Execution
5. Propose Verification (Mandatory After Successful Implementation)

I literally created one for you using Grok:

(Yes, you will copy and paste the entire thing in every prompt when updating your code base)

{You can set these as 'rules' but AI doesn't always stick to the rules}
x.com/i/grok/share/d…

🪲Bug Protocols:

Ask the AI to create a protocol for your programming language with the below parameters to reduce hallucinations.

1. Re-establish Context & Verify Environment
2. Deep Analysis & Root Cause Identification
3. Solution Design & Proactive Enhancement
4. Validation Strategy

(Again, I've done this for you using Grok but you should make your own based on your coding language)
x.com/i/grok/share/s…

🏗️ How to use protocols:

For every update or bug fix you'll enter your prompt (SPEC ALWAYS) and below that you'll paste your protocol.

(You may need to instruct the AI to follow the protocol in your prompt)

DO THIS EVERY TIME!

🎨 Prompt creation:

This is where the magic happens.

Do NOT ask the AI to create something and then sit back and watch.

THAT'S NOT GOOD AI PROMPTING!

Flush out as much of your plan as possible and then ask the AI to review your work to make sure it understands.

(You may need to say DO NOT UPDATE THE CODE BASE)

If you like what you see then proceed to the next step.

SPECS!

⚙️ Specifications:

Copy and paste the last AI output and prompt it to create a SPEC as if it were a PRODUCT MANAGER.

Review the SPEC carefully.

The AI will often add useful features or ideas you didn't think of during this process.

After you edit the spec you are now ready to update the code base.

(I literally created one using Grok in less than 5 min for a Macro Tracking app)
x.com/i/grok/share/C…

⌨️ Updating the code base:

Paste your SPEC and PROTOCOL into the chat and hit enter.

Voila!

You're now building something that will have minimal errors if any at all.

😴 NEVER code when you're sleepy.

I learned this the hard way.

Your mind misses things in the SPEC and you end up creating something you don't want.

🔖 Expect to do a ton of reading.

Specs are long and intense and you WANT to read through them carefully.

That's why you don't want to be sleepy.

🧠 Do NOT rely on the AI to solve all of your problems.

Most of the thinking is done by YOU!

The more smarter you are the smarter the AI will be.

You will have to think through some issues to get the outcomes you want.

🔨 Tools:

I built fitboy.app (download please) using Cursor AI.

Claude 4.0 is a godsend.

I use Gemini 2.5-pro-preview for specs.

Thinking models are best for planning but cost more.

Use them to think through planning and use the agent included in your subscription plan to create specs in order to save money.

For execution, Gemini works but for bigger tasks I use Claude 4 because safety first.

The website was built with Replit (it's a WIP).

I could have charged you $1,000+ for this information by selling you a course but I didn't.

However, I will be doing a workshop for anyone who is subscribed to any of our products on menoforder.com

Thank me by downloading (and using) our app.

You can download it at FitBoy.app