Ask Cumbersome Pro's AI to create a website, save its files, and write a checklist. Here's the workflow on iPhone.
The AI creates and saves the files in the first image, shown with a corrected header composite. The second shows the page after revision. The HTML and checklist stay in the Project for the next request.
I want to be able to say "move the price up" and have the AI change the saved page. I also want to check that it hasn't rewritten the refund policy while it's there. That's what we'll walk through: creating files, reviewing edits, and keeping enough context to continue the job later.
Our example is the fictional Juniper Garden Club's Balcony Herb Workshop. We'll build its page and review checklist, then use the same Project for source documents and planning conversations.
What you need before starting this Cumbersome Pro tutorial
You'll need Cumbersome on your iPhone, an active Pro subscription, iCloud Drive available for your files, and a configured AI provider. I used OpenAI GPT-6.1 Sol through OpenRouter for the examples. If you haven't connected a provider yet, start with the API provider setup.
Cumbersome Pro adds the file workspace and its search tools, including searching other chats in the same Project when enabled. Creating Projects and running an HTML preview are part of the supporting workflow; they don't themselves require Pro. Your AI provider bills model usage separately.
We'll keep the page in one HTML file, with its styling included. That's enough for a workshop description, agenda, and FAQ, and it keeps the preview simple.
1. Ask the AI to create and save your site
Create a Project named Juniper Garden Club and start a chat inside it. Check that the chat's Project chip shows that name. The generated page, checklist, and later conversations will belong to the same job.
Give the AI your brief in the message, or ask it to read source files you've already added to the
Project. Tell it which files to create and where to save them. For this site, we'll use
Site/index.html for the page and Notes/launch-checklist.md for our review notes.
You can start with a request like this:
Create and save Site/index.html and Notes/launch-checklist.md in this Project. Create the Site and Notes folders if needed.
The page is for Juniper Garden Club's fictional Balcony Herb Workshop: Saturday, July 10, 2027, from 10 am to noon. It costs $35 per person, has 12 places, and includes supplies. It's for beginners starting a small balcony herb garden. Full refunds are available up to 48 hours before the start.
Include this agenda: welcome at 10 am, choosing a planter and reviewing materials at 10:10 am, guided planting at 10:25 am, writing a care plan at 11:10 am, and individual planter checks from 11:40 am until noon.
Make one HTML page with embedded CSS, a cream background, deep green text, and an orange accent. Include the workshop details, agenda, and a short FAQ. Make it readable on an iPhone. Mark it as a tutorial demo with registration closed. Leave out invented addresses, reviews, and booking links. The checklist should cover the facts, refund terms, mobile layout, and demo notice. Save both files in this Project.
For my run, I kept those details in brief.md and workshop-agenda.csv and asked Sol to read them
before creating the outputs. We'll cover importing and writing those source files below. The AI
handles creation of the site and checklist either way.
Find the files the AI created
Watch for File created in the response and a file card marked Saved to Project, as shown at
the top of this article. Sol created both Site/index.html and Notes/launch-checklist.md. Tap a
file card to open the saved result.
You can also open the menu at the top left, tap Files, and choose Project: Juniper Garden
Club from the location menu. Open Site to find index.html, or Notes to find the
checklist. The files are available to the next chat you start in this Project.
New files save as the AI creates them. When you ask for changes to existing files in a later message, Cumbersome presents those edits for review. We'll do that after looking at the page.
2. Run the HTML preview on your iPhone
Opening index.html in Files shows its source. To see the rendered page, ask the AI to read the
saved file and return its complete contents in an HTML code block. Then use the code block's Run
action to open HTML Preview.
Be specific about keeping the contents intact:
Read the saved Site/index.html and return its exact contents in one HTML code block so I can use Run. Keep the file unchanged, and include the complete HTML.
Scroll through the preview as a visitor would. Can you find the date and price? Does the agenda make sense? Is the refund answer easy to read?
The initial page put the details below the introduction and navigation. I wanted the date, hours, price, and place limit immediately below the headline. Someone deciding whether to come shouldn't have to hunt for them.
3. Review AI changes before applying them to your files
Ask for that layout improvement in a new message, along with a corresponding checklist update:
Move the date, hours, price, and 12-place limit together immediately below the headline in Site/index.html. Make the refund policy easier to scan without changing its wording. Add a check for those four details and their placement to Notes/launch-checklist.md.
Cumbersome collected the proposed edits into a 2 files card. Tap Review to inspect the changes before applying them.
In the HTML diff, the refund words stayed the same. The edit added bold formatting and a line break. Elsewhere, the existing fact cards moved under the heading. The checklist gained one item asking us to check those details and their position, including on mobile.
Inspect both files, then tap Apply All. If the proposal misses the mark, use Discard All and ask for a different change. I applied this group and checked the saved versions: the date, hours, $35 price, 12 places, and refund terms were unchanged. The layout and checklist had the requested edits.
When you want to inspect the revised page, ask for the saved HTML again and run that new code block. The earlier preview contains the earlier code; it doesn't refresh itself when you edit a Project file.
4. Add your own source files with Import or New File
Once the AI is creating files, you'll often want to give it documents to work from: a customer
brief, a timetable, or notes you've already written. For this workshop I used brief.md and
workshop-agenda.csv as the source material. Keeping those facts in their own files lets another
chat retrieve them later.
If you already have the documents, open Files, choose Project: Juniper Garden Club from the location menu, and tap Add > Import. Select the files in the iPhone picker, then tap Open. Import copies them into the Project's folder in Cumbersome's iCloud Drive storage. The original files stay where they are. You can also write a file yourself inside Cumbersome. Here's how to create the two sources used in this example.
Open the Project's files and choose New File
- Tap the menu button at the top left of Cumbersome, then tap Files near the bottom of the drawer.
- Tap the current location name at the top of the Files screen. Choose Project: Juniper Garden Club if it is not already selected, so the new file belongs to the workshop Project.
- Tap Add, then New File. This opens an editor with a filename field, a text area, and Save at the top right.
Enter the filename and write the brief
In Filename, enter brief.md, including the extension. The .md extension identifies it as a
Markdown document. You can write ordinary paragraphs and lists in it; you don't need to know
Markdown to give the AI a useful brief.
Tap the large text area below the filename and type or paste your workshop facts and design instructions. This editor writes the file directly; the AI can read it once you've saved it.
These are the facts in my brief:
| Detail | Workshop brief |
|---|---|
Event | Balcony Herb Workshop |
Date and hours | Saturday, July 10, 2027, from 10 am to noon |
Price and capacity | $35 per person, 12 places |
Supplies | Included |
Refund policy | Full refund up to 48 hours before the start |
Audience | Beginners starting a small balcony herb garden |
Registration | Tutorial demo. Registration is not open. |
I also specified a cream background, deep green text, and an orange accent. The brief asks for a page that reads comfortably on an iPhone and tells the AI to leave out invented addresses, reviews, and booking links. A convincing fake ticket button would be a fairly annoying addition to a demo.
Tap Save. When the editor closes, look for brief.md in the Project's file list. To check or
change its contents, open the file's three dot menu and choose Edit. A row marked Unsaved
changes still needs saving; it isn't the finished source file for the next step.
Create the agenda as a second file
Tap Add > New File again. Enter workshop-agenda.csv in Filename, paste this timetable into
the text area, and tap Save:
start,end,activity
10 am,10:10 am,Welcome and workshop introduction
10:10 am,10:25 am,Choose a planter and review the materials
10:25 am,11:10 am,Guided planting activity
11:10 am,11:40 am,Write a simple care plan
11:40 am,noon,Individual planter checks and questions
Return to the Project chat and ask the AI to read both files. In this walkthrough, Sol used Search and Read Source to retrieve them. Give the files useful names and refer to them directly in your request. That saves you from pasting the whole brief again whenever you want a small change.
Use this chat for the planning decisions, too. I recorded why we wanted a small group: each person should get an individual planter check before leaving. We also ruled out countdown timers and "selling fast" copy, and rejected "Tiny balcony, big harvest" as a headline because it promised too much. I asked the AI to acknowledge those decisions without changing the files. We'll come back to them from another chat.
5. Start a fresh chat and reuse the Project's files
You don't have to keep the entire job in one long conversation. Start a new chat, tap its Project chip, and select Juniper Garden Club. I named this one Workshop follow-up. Check the Project name before sending: the new chat in this walkthrough initially opened outside the Project.
Ask for the facts you need to continue:
Read this Project's workshop brief and agenda. What are the workshop hours, ticket price, and refund terms? Cite the source files you used.
Sol searched the saved files and read the source. It returned 10 am to noon on July 10, 2027, $35 with supplies included, and a full refund up to 48 hours before the start. Tap the brief's citation to open the saved source and check the answer.
This is where saving the brief starts paying off. A new conversation can work from it without making you copy everything out of the earlier chat. Ask for the relevant source, then use the answer to write an invitation, revise the page, or check a proposed change against the refund terms. File search runs locally; when you ask an online model to use a source, the relevant text goes to your selected provider.
6. Find a decision from another conversation in the same Project
The brief has the price and timetable. It doesn't contain every conversation that led to the page. Suppose you're writing a second version a week later and can't remember why you dropped a headline.
Open Edit Project and check Conversation Search > Allow AI search. This lets the AI search conversations in that Project. You can still look up saved files when this switch is off.
In Workshop follow-up, I asked about the earlier planning decisions. Sol found the reason for the 12 places, the decision against urgency messaging, and the rejected headline. I then narrowed the request to:
Find the rejected headline in our earlier Project chat and cite it.
It returned "Tiny balcony, big harvest" and cited the planning message where we'd rejected it. Open that citation to read the original passage.
I then asked Sol to add an FAQ answer explaining the group size, using the decision it had found. It proposed one added line about giving each participant an individual planter check. I reviewed that addition and tapped Apply All. The earlier conversation now informed a useful change to the page.
That's how I'd resume work after a break: find the decision, open its source if I need a reminder, and use it in the next edit. Keeping related chats in one Project gives the follow-up conversation somewhere to find that discussion.
7. Rename a file and make a small edit yourself
You can work directly in Project files when a change is too small to warrant another AI request. I wanted to rename the checklist and add a reminder about the new FAQ answer.
In the Project's Files view, open Notes, then the menu beside launch-checklist.md. Choose
Rename..., enter review-checklist.md, and tap Save. The renamed file appears in the
folder. Use its new path, Notes/review-checklist.md, in subsequent requests.
Open that file's menu again and choose Edit. Under the title, I added:
Reviewer note: Check the rendered FAQ against the planning decision.
Tap Save to keep the change. This is handy for a precise wording fix or a short note you already know how to write. You can make it directly, then ask the AI to work from the updated file later.
8. Use version history to recover an earlier file
Open the checklist's menu, choose More Actions > Version History, and look through the saved versions. For this file, the history includes the original generated checklist, the AI update, the rename, and our manual edit.
To undo the note, open the menu for the version immediately before the manual edit and choose Restore This Version. The confirmation explains that the current version stays in history. Tap Restore to return to the selected version. You can go back through history again if you need the newer work.
I restored the version from before the manual edit. The added reviewer note was gone, and the checklist was back to its previous contents.
Recovery remains available after Pro expires. Creating and saving new edits requires Pro, but restoring an existing version doesn't. I don't want a subscription decision to prevent someone from recovering their own work.
9. Search inside your saved files without asking the AI
Suppose you want to check everywhere the workshop's refund policy appears. Open Files, tap the
magnifying glass, and set Location to Juniper Garden Club. Turn on Search file contents,
enter refund, and tap Search.
The results found all three relevant files: review-checklist.md, index.html, and brief.md. Tap
a result to open the file. I opened the brief to check the original policy against the wording on
the page.
The Search file contents switch matters here: none of those filenames contains "refund." Filename filtering helps you locate a file you can name. Content search helps when you remember a phrase inside it. For a quick check like this, I can open the matching files myself without waiting for a model to explain them.
10. Export the site and reuse a copy in Personal Files
We've finished a page. Let's keep a copy of its design for another job.
Open the menu for Site/index.html and choose Export.... In the iPhone file picker, choose a
destination and tap Save. I saved ours to On My iPhone.
Back in Cumbersome, choose Personal Files from the Files location menu. Tap Add > Import,
select the exported index.html, and tap Open. It appears in the file list. I renamed this copy
workshop-example.html so its purpose would be obvious later.
Start a new chat outside any Project, check that its organization chip says Personal Files, and ask:
Read workshop-example.html in Personal Files. List its colors and sections so I can reuse the design. Cite the file.
Sol read the saved design and returned layout details with a citation to workshop-example.html. I
opened the citation to inspect the HTML, including its colors and FAQ.
Personal Files works well for reusable examples, writing guides, and standard checklists. An ordinary chat uses that library; a Project chat uses its own Project's files. Keep an ongoing job in a Project when you also want to search the conversations behind its decisions.
A few file options for other kinds of work
For noneditable reference files such as PDFs, Create Editable Copy makes a text copy you can work on; it doesn't edit a PDF's page layout or Word formatting. More Actions > Replace... updates a saved source file while keeping its file identity and version context. These options are useful when someone sends you a revised brief midway through a job.
You can keep refining the mini site in this Project, share the exported HTML, or use the copy as the starting point for another page. Publishing it on the web needs a separate hosting service. Pro's file editing and search tools keep the brief, working files, and earlier decisions available for the next edit. I can ask for another change without writing the whole brief again.
Bless up! 🙏✨