How to build your first AI tool
Updated July 2026
To build your first AI tool, pick a task you've done 3 times in the last 2 weeks, set up a Claude Project for it on claude.ai, have Claude write its own instructions from a good and a bad example of your writing, test it on something from your inbox, and update the instructions as you go to fine-tune your results. The whole build takes about 10 minutes and involves no code.
Plenty of people watch AI videos every week and still haven't built anything with the tools they keep hearing about. The usual reason is that the first project feels like it needs to be impressive, so it never gets started. A first build should be small enough to finish in one sitting, useful enough that you open it again tomorrow, and simple enough that no code is involved.
This walkthrough builds exactly that kind of tool in about 10 minutes: an email drafter that takes any rude email you paste in and writes a calm reply in your voice. The same process works for meal planning, marketplace listings, workout plans, or whichever part of your job repeats every week. It's also the exact first build we do inside AI Builder Society, the free community I run for people learning how to start with AI, so every step below has been walked by beginners many times.
The five parts of the build
The tool is a Claude Project, which is a workspace inside claude.ai that remembers your instructions, files, and preferences so you don't need to re-explain yourself every chat. The build has five parts, and none of them require anything beyond a Claude account:
- Create a project: load your instructions and files in once and it remembers them for every conversation.
- Pick a task that qualifies: something you've done at least 3 times in the last 2 weeks.
- Let Claude write its own prompt: you describe what you want done, and Claude researches prompting best practices and writes the instructions for you.
- Test it on an email from your inbox: so you can see how close the voice is.
- Fine-tune as you go: every time you dislike an output, one new line in the instructions fixes it going forward.
Pick a task that qualifies
If you've done the same task 3 times in the last 2 weeks, it qualifies. That's the core rule we teach, and it saves you from trying to invent a project just to have one. The best first build automates something you already do by heart, because you'll know immediately whether the output is any good.
If nothing comes to mind right away, walk through every hour of your day from the moment you wake up. Somewhere in there you're repeating something: replying to the same kind of email, writing the same kind of listing, planning the same meals every Sunday.
Is a Claude Project the right home for your task? This is the quick check:
| Your task looks like | Build it with |
|---|---|
| A repeated chat task with the same instructions every time (emails, listings, plans) | A Claude Project (this guide) |
| A one-off deliverable: a doc, research, a summary | A plain chatbot conversation |
| Building or changing real files and software | Claude Code (see the architecture guide below) |
Create the Claude Project
Go to claude.ai, click Projects in the sidebar, and create a new project named after the task, something like "Email Drafter." A project holds instructions, files, and memory that load into every conversation inside it, which is what turns it from a chat into a tool you can reuse.
Projects are the right fit when two things are true: the task follows the same instructions every time, and it comes back often enough that re-explaining it in a fresh chat would get annoying. Email replies pass both tests easily.
Let Claude write its own prompt
You don't need to write the instructions yourself. In the project chat, type something like "research prompting best practices, then write an email drafting prompt that always responds calmly and confidently." Claude searches for current best practices and writes a more thorough prompt than you would have written from scratch.
Then we need to make Claude write in your style, and the fastest way to do that is by providing it one good and one bad example of writing. The good example should read calm and own mistakes plainly. The bad example can be full of AI giveaway phrasing like "in today's fast-paced environment." Paste the exact quotes into the session where you're creating your prompt, and Claude will adhere to the writing style more strictly than if you just tell it "do this" and "don't do that."
Copy the finished prompt into the project's instructions and save it. If the prompt contains markdown symbols like # or **, leave them in; Claude reads them like normal language.
This exact build is the first win we ask for in AI Builder Society, a free Skool community where you go from watching AI videos to a working AI assistant in about 10 minutes.
Join AI Builder Society (free)Test it on an email from your inbox
Paste something from your inbox into the project chat rather than a made-up example. In the video I used a snarky "per my last email" message, and the drafter came back with a calm reply that owned the mistake and gave a specific timeline for the fix.
You don't have to send the output word for word. Treat it as a starting point in your voice, edit the details, and send it. The value of the project is that the starting point shows up instantly, every time.
Fine tune the result
When the assistant does something you don't like, add one line to the instructions telling it not to. One random example is if you didn't want it to promise specific delivery dates: you'd add a line like "don't ever promise a specific date of delivery" to the don't section, save, and it behaves that way from the next draft onward.
This is why the build gets better while you use it. You'll add a few of these lines over the first week, and after that it drafts the way you would.
Build it today
Your first AI build shouldn't take a weekend, and it shouldn't require code. Pick a task you've repeated 3 times in the last 2 weeks, set up a Claude Project for it, have Claude write its own instructions from a good and a bad example of your writing, and update the instructions as you go to fine-tune your results. The full 10-minute walkthrough is on YouTube: watch the build start to finish. And if you want the simplest place to learn how to start with AI alongside people doing the same thing, join AI Builder Society for free and post this build as your first win.
FAQ
Do I need to know how to code to build my first AI tool?
No. The whole build happens inside a Claude Project on claude.ai: you write instructions in plain language, Claude does the drafting, and no code shows up anywhere. The only requirement is a Claude account.
What should my first AI build be?
Automate a task you already repeat. The rule: if you've done the same task 3 times in the last 2 weeks, it qualifies. Email replies in your voice, meal planning, marketplace listings, and workout plans are all good first builds, because you already know what a good output looks like.
How do I make Claude write in my style?
Provide it one good and one bad example of writing. Paste the exact quotes into the session where you're creating your prompt, and Claude will adhere to the writing style more strictly than if you just tell it "do this" and "don't do that."
What's the difference between a Claude Project and Claude Code?
A Claude Project is a workspace inside claude.ai that remembers your instructions, files, and preferences, which fits repeated chat tasks like drafting emails. Claude Code builds and changes real files and systems in a folder on your computer. Start with a Project; move to Claude Code when you want to build software.
How long does a first AI build take?
About 10 minutes. Create the project, have Claude research prompting best practices and write its own instructions, paste in a good and a bad example of your writing, and test it on something from your inbox. The fine-tuning after that happens while you use it.
Related: how to build anything with AI (the architecture cheatsheet) and the best free Skool communities for AI builders.