// AI & Tools
Base44 prompts you can adapt
Useful starting points for a small build, a clearer plan and a focused fix.
A starting prompt should help you explain the job your app needs to do. Replace the bracketed details and remove anything you do not need.
These are SHE//BUILDS examples to adapt, not pre-tested templates for every business. Check the output before using real customer information.
Plan a first version
Help me plan a small Base44 app for [type of user]. They need to [one useful task]. The first version should let them [main action] and finish with [clear result]. Propose the pages, data, relationships and access rules. Ask me about missing decisions before implementation. Identify which features can wait.
Use this when you have an idea but the scope is unclear. Read the plan and answer questions rather than accepting features you do not understand.
Build a private tracker
Build a private tracker for [tasks, enquiries or projects]. Each record needs [fields]. A signed-in user can access only their own records, enforced in data access rules. Include add/edit forms, a list, [useful statuses], an empty state and clear saving/error feedback. Make it readable on mobile. Explain how to test the main journey and ownership rules with fictional records.
Decide who owns a record and whether any administrator needs access. Different users should not share data accidentally.
Create an enquiry form
Create an enquiry page for [business]. Collect [only the fields we need] and save each valid enquiry privately. Visitors must not be able to read other enquiries. Include validation, a spam-control approach, duplicate-submission protection and visible success/error messages. Show a private admin list. Treat submissions as requests, not confirmed bookings.
Test public submissions and private administration separately.
Fix a specific problem
Problem: [what happens].
Steps: [exact steps to reproduce it].
Expected result: [what should happen].
Actual result: [what happens instead].
Investigate and fix the cause. Preserve [important existing behaviour]. Explain what changed and give me checks to confirm the fix.
Remove private account details from errors or screenshots before sharing them.
Check a build before sharing
Review this app's main user journey, permissions, validation, empty states and error handling. Identify what can be checked automatically and what I need to test myself. Do not claim an item passes unless it was actually verified. Keep the review focused on the current version.
Your next step
Pick one example, tailor it to your own app and keep a note of what you tested. Plan before you prompt or follow the first app tutorial.
Reference: Base44's official prompt guide.