On this page
Write Useful MiniUp Prompts
A useful MiniUp prompt states the audience, task, actual data, access requirements, and how the finished app will be checked. Include whether the AI should create a new Site or update an existing Site.
Prepare a prompt
- Name the workflow: new Site, existing Site edit, Table app, dataset dashboard, or member portal.
- Identify the uploaded file, hosted dataset, or approved Dataset Bundle.
- Ask the AI to inspect schema and sample values before choosing fields.
- Describe required behavior and who may see or change data.
- Require a published URL, changed-files summary, and verification results.
Build from an uploaded spreadsheet
Use MiniUp to build a mobile-friendly request tracker from my uploaded
spreadsheet. Inspect the columns first. Use a Table for editable records,
preserve private reads, and route protected operations through a Site
Members Function. Include search, loading, empty, and error states.
Do not invent rows or place private keys in browser files.Reuse approved hosted data
Use my approved Parks Dataset Bundle in MiniUp. Verify geometry and
field names, then build a map and a paginated list. Show only bounded
results and preserve the dataset's access settings. Publish a new Site
and return its URL. Explain any source-data gaps.Build from a PDF Knowledge Pack
Use this MiniUp PDF App Prompt to build a searchable reference guide.
Keep source citations visible. If the PDF does not support an answer,
say so. Use the pack's actual access instructions, avoid invented facts,
and test the result on a phone.Improve an existing app safely
Update my MiniUp Site named my-site. Add an accessible filter to the
existing dashboard. Keep the current API connection and access policy.
Show the file diff and preview, validate the filter, and summarize the
published change.Review AI output
Open the actual result and test its primary action. Check that the app uses real data and retains permissions. A realistic screenshot or example response does not prove the live API works.