Your copy-and-paste prompt
Replace the [brackets] with your details, then paste this into your assistant.
Make the spreadsheet I already use easier to check on my phone. Use [workbook copy or authorized read-only source]. It tracks [my project, household plan or collection]. The three questions I most want answered are [questions], the relevant tabs are [tabs], and my intended device/browser is [details]. Build a small read-only interface first. Keep the workbook authoritative and preserve its formulas and original layout. Before writing the app, inspect the workbook and return a compact data dictionary: important tabs, headers, date and number formats, input cells, formulas, totals, hidden rows relevant to those totals, and ambiguous meanings. Ask me to resolve any ambiguity that changes a calculation. Do not silently repair a total or assume a blank is zero. Distinguish a formula from its stored result. If the available export lacks current calculated values, ask for a refreshed export from the spreadsheet application rather than inventing results or rebuilding the formulas in code. Propose one screen with at most three useful summary cards and a searchable, filterable list. Each card and row should have a Source detail showing its tab and cell/range or stable row identifier. Use the spreadsheet's calculated values where possible. For any additional aggregation I approve, document exactly which rows and rules it uses and reconcile it with a small hand-checkable example. Preserve locale, units, date meanings and rounding. Keep missing values visibly missing. Choose the simplest private way to use it with the tools already available. A local file-import app is fine; show the imported filename and export date when known, plus the time it was loaded. If using an authorized read-only live connection, show the last successful refresh, source timestamp when available, and connection errors. A recent load does not prove that the underlying workbook is current. Do not put credentials into client-side code or invent an access-control setup. If a private phone preview is unavailable, deliver the app files and label phone access as not yet verified. Make it comfortable at the target phone width: stacked cards, large touch controls, useful empty states and readable text without sideways page scrolling. Include search, one or two meaningful filters, Clear filters, and a visible way to reload or import a newer snapshot. Refresh should replace the displayed snapshot, not append duplicate rows. Do not write back to the workbook, deploy it publicly or add accounts or paid services in this first version. Check with a sanitized sample first, then reconcile the approved source's displayed values. Test several rows and every summary against their recorded cells or rules. Try a blank, a negative number if relevant, a locale-formatted date/number, an unknown column and the same import twice. Show an error for an incompatible file instead of silently displaying old data as new. Check filters, clearing, source details, refresh status and the actual narrow layout. List passed checks, explained differences and unresolved mismatches separately; do not describe unexplained differences as reconciled. Return the working app and editable source, data dictionary, source map, refresh instructions and a short check report. State whether it is a snapshot or connected view and what you actually opened on the phone or in an emulated viewport. If code execution or browser inspection is unavailable, return a labeled interface specification and data map instead of claiming a working app. Any future editing, automatic refresh or sharing is a separate step with explicit scope.
Automatic copying is unavailable. Select the prompt text above and copy it.