Your mini project: build, test and maintain

When you finish, you can build a small AI tool of your own, test it with tricky inputs and keep it working over time.

Choose a small, real job

Pick something you do at least weekly that is repetitive, low risk and easy to check. Good first projects: a reply helper for common questions, a meeting-notes formatter, a lesson-plan starter, a weekly summary of your own notes. Avoid anything involving private records about other people or high-stakes decisions.

Write one sentence: “This tool helps [who] do [what] so that [benefit].” If you cannot finish that sentence, the project is too vague. Shrink it until you can.

Build it in four steps

Step one: write the saved instructions, using role, audience, rules, format and fallback. Step two: make a template or form for the input. Step three: if useful, plan one simple automation, with a human check. Step four: write a short guide for users, covering what to enter, what to expect and what never to paste.

Keep the first version plain. It is better to have a small tool that works than a clever one that nobody trusts. You can add features after you see how people actually use it.

Test it like a skeptic

Make a list of test inputs: normal ones, odd ones and ones that try to break your rules. Include missing information, a very long input, a rude request and a request outside the tool’s job. For each, decide in advance what a good response is, then compare.

Where it fails, change the instructions, not just the test. Add a rule, an example or a fallback. Then run all the tests again, because a fix for one problem can break something else. Keep a short log of what you changed and why.

Maintain it

Tools drift. Products update, models change behavior, links break, and your own needs shift. Put a reminder on your calendar to rerun your tests every month or after any known update. If results get worse, adjust the instructions.

Also review who uses it and what they paste. Remind people of the rules, remove old connections, and keep a copy of your instructions outside the tool. Worked example: a community center in Mumbai built a flyer-text helper. When the underlying product changed its style, their monthly test caught longer, more formal answers, and a one-line instruction fixed it.

Practice now

Write your one-sentence purpose, saved instructions and a template for a small tool. Try it on five normal inputs.
Write ten test inputs including at least three tricky ones. Run them, record what went wrong, change your instructions and run them again. Put a monthly reminder on your calendar to retest.

Use any AI assistant you have. Do not paste private, client or patient information into it.

Check yourself

1. What makes a good first project?

2. When your tool fails a test, what should you do?

3. Why retest your tool every month?

Ask the AI tutor

Ask anything about this lesson, in any language. The tutor is an AI: it can be wrong, and it never needs your personal details.

Take the final exam

AI-drafted. Checked by an automated validator and a separate AI reviewer; a person has not read every lesson. Translations and tutor answers are AI-made. Found a mistake? Tell us. AI can be wrong. General information only, not professional advice. Not affiliated with any AI company named. Current University is not accredited.