lite
Buy now

Help Desk › Working with your AI

Sample prompts for the eight use cases

The prompt behind each one on the Use Cases page. Copy it, change the parts in brackets, and give it to whichever AI you use.

These prompts create HTML pages in your Showspace. Some make one page; others make a linked set. Replace the parts in brackets and let your AI ask any questions it needs before starting.

01 · Reports — The progress report you can talk back to.

Here are some starter prompts. How well they work depends on how your AI is set up, so adjust them to fit yours.

Sample prompt

Read [the project folder / these documents / these links] first. Then write me a progress report on [PROJECT] as one self-contained HTML page, saved in my Showspace. Cover what shipped, what is stuck, and what decisions you need from me. Use the colors and typefaces from the brand guide in my Showspace, and keep each section to one screen so I can read it without hunting. Before you write anything, ask me what you need to know — who it’s for, how much detail, and what period it covers. I’ll read it in lite.computer and leave comments; next session, read my comments and revise the same page.

02 · Dashboards — The dashboard that keeps itself current.

Sample prompt

Build me a dashboard as one HTML page in my Showspace, with changing figures in a small data file beside it. Show [THE NUMBERS THAT MATTER] from [WHERE THEY LIVE — a spreadsheet, a CSV, an API you can read]. Make the big figures readable from across a room, use my brand colors, and show both the source time and last successful refresh. Keep the last good figures and mark them as old if an update fails. [OPTIONAL: Add a short, dated AI briefing.] Follow the lite.computer guide for pages that stay current. Tell me where the update job runs and what access it needs, and ask before installing anything on my Mac. Before you build, ask which numbers matter most, how often they change, and exactly where you can read them from. Verify the first unattended run.

What your AI sets up depends on where the numbers live: a spreadsheet, a cloud service, the open web, a file you edit. See Keeping a page current.

03 · Brand — The brand guide every model can reach.

Sample prompt

Read [our logo files, our existing documents, our website] and write our brand guide as one self-contained HTML page in my Showspace. Show the palette as real swatches with hex values, set each typeface in itself, and write the rules plainly enough that another AI could follow them without asking me anything. Where we don’t have a rule yet, propose one and mark it as a proposal. Before you start, ask me what we already have, what we’re unsure about, and what tone we want.

04 · Concepts — The website concept, staged as pages.

Sample prompt

Read [my brief / my notes] first. Then look at [two or three sites I admire] and tell me what you’d borrow from each for layout and pacing. Draft [SITE] as separate self-contained HTML pages in one folder in my Showspace — one page per screen, linked with relative links so I can click through the whole thing. Real copy, not placeholder text, in my brand colors and typefaces. Before you draft, ask me what you still need: the audience, the one thing each page must do, and what we’re selling.

05 · Presenting — Make unique, show‑stopping presentations.

Sample prompt

I’m presenting [SUBJECT] to [AUDIENCE] for [DURATION]. Read [my materials] first. Then find three presentations or websites online whose design you’d draw on, and tell me why. Build the deck as one self-contained HTML page in my Showspace, one full-screen section per point, sized to read from the back of a room, in my brand colors. It will be shown on [WHICH SCREEN — landscape or portrait, and its shape: a 16:9 wall panel, an ultrawide, a laptop], so lay every section out to fill that shape with nothing cut off. Add transitions and a small animation where it sharpens a point, not everywhere. Keep my speaker notes in a separate page beside it. Before you build, ask me what the one takeaway is, what I want people to do afterwards, and anything you’re unsure of.

06 · Reading — The long document you actually read.

Sample prompt

Read [my research / notes / sources] and write [SUBJECT] as a set of self-contained HTML pages in one folder in my Showspace — one chapter per page, each linking to the next and back to a contents page. Lay it out to be read for an hour, not skimmed: one column, generous margins, no sidebars, my brand typefaces. Wherever a diagram or infographic would explain something faster than a paragraph, make one. Before you write, ask me who the reader is, how long it should be, and what I already know, so you don’t explain it back to me.

07 · Records — A database that you like using.

Sample prompt

Read [the CSV / spreadsheet / export] at [path]. Build me one self-contained HTML page in my Showspace holding every record on it — a row each, with the two or three figures I care about most called out as summary tiles across the top. Lead each row with the name and what it is worth, then the supporting detail. Sort largest first. Use the colors and typefaces from the brand guide in my Showspace, give every row a small color-coded status tag, and make the table collapse into readable cards on a phone rather than scrolling sideways. Keep the page self-contained: styles inline, any images embedded, no external files. Before you write it, tell me how many records there are and show me one finished row so I can check the layout. When I send you an updated export, rebuild the same page rather than making a new one. Once the layout is settled, write me a small script that reads the file and regenerates the page, so I can run it on a schedule and stop asking you.

08 · Displays — Make signs that come alive.

Sample prompt

Make a full-screen display page for [WHAT IT SHOWS — a room’s schedule, today’s specials, a welcome board] as one self-contained HTML file in my Showspace. It will run on [WHICH SCREEN — give the size in inches, whether it hangs landscape or portrait, and the pixel dimensions if you know them]. Fill that shape exactly: no scrolling, nothing to click, nothing cut off at the edges. Read from across a room: high contrast, large type, in my brand colors. Have it keep itself alive — a clock, a countdown, live numbers from [SOURCE], or rotate between things on a timer. Look at [signs I like] for the feel. Before you build, ask me the exact shape and resolution of the screen, what must be on it, and what changes and how often.

A sign that shows today's menu or live numbers stays current the same way a dashboard does. See Keeping a page current.

Six tips before you ask

  • Make a brand guide before you make pages. Ask your AI for a short brand guide first: a few colors, one or two typefaces, how headings and body text should feel. Then tell it to follow that guide in this Showspace. Pages made after a guide look like they belong together; pages made without one look unrelated.
  • Ask for a different shape, not a different color. If every page looks the same, color is rarely the reason; the layout is. Say what shape you want: a dense table with no big heading, one number per screen, a timeline, a sidebar with sections. That changes the page. A new color does not.
  • Make a page that updates itself. For anything you re-read often, a dashboard, a tracker, a menu, have your AI build the page once and keep its numbers in a small data file beside it. After that, a refresh rewrites only that small file, and can never mangle the layout you liked. See Keeping a page current.
  • Let it run on a schedule. Your AI can set up a local script or a scheduled AI job at an interval that fits the source. The page checks its data file and redraws when new figures arrive. A local script can run without an AI plan; scheduled AI analysis uses your AI plan. lite.computer displays the saved result.
  • Keep everything in one folder. Point your AI at this Showspace and let it write there by default. Copies of files made somewhere else are dead: the original changes and the copy never does.
  • One page, one file. Ask for self-contained pages: styles inside the file, images embedded, no separate stylesheet. The recipient can download the HTML file and open it in a browser. They do not need lite.computer.

Still stuck? Write to support@lite.computer.