SECTION_17

Pro Workflow Tips

Advanced techniques from experienced builders to level up your process.

These tips come directly from experienced Caffeine builders. They won't show up in the official docs — they're earned through trial, error, and wasted credits. Apply them and you'll build faster with less frustration.

> Tips shared by fran.icp on Discord

> Project & File Management

> Build New Features in a Separate Project

Create a fresh Caffeine project to develop and test a new feature in isolation. Once the code is clean and working, download the files and integrate them into your main app. This prevents half-finished features from breaking your main project and saves credits by keeping debug cycles short.

Step 1

Create a new project in Caffeine

Step 2

Prompt the full feature from scratch

Step 3

Test and iterate until clean

Step 4

Download the relevant files

Step 5

Integrate into your main project

Integration prompt — use this exact phrasing

Replace [filename] with the attached version — do not change anything else.

[The File Replacement Workflow]

When a file is broken or complex, download it, open it in Claude or ChatGPT for analysis, get the fix explained, then reattach the corrected file to Caffeine with a precise instruction. This bypasses the AI's tendency to rewrite too much context and gives you surgical control.

Replacement prompt — precision prevents unintended rewrites

Replace [filename] with the attached version. Do not change any other files. Do not rewrite unrelated sections.

[Base64 for Images That Won't Display]

If a static image consistently fails to display, you can ask Caffeine to embed it as a Base64 string directly in the component. Important: this bloats file size significantly — only use it for small, static images (logos, icons). For anything dynamic or user-uploaded, always use Storage instead.

[Clean Up Attached Files Regularly]

Over time, attached files in Caffeine accumulate — old versions, replaced components, obsolete docs. Periodically delete files you no longer need. A cleaner attachment list means the AI focuses on what's actually relevant and makes it easier to find the file you want to attach next time.

> Debugging & Recovery

[Use Git to Verify What Changed]

After a critical AI-generated change, use the Caffeine GitHub Export to download your project and run a git diff to see exactly what was modified. This is especially useful for complex prompts where the AI touched multiple files — you know precisely what changed and can catch unintended edits before they cause problems.

[Revert When You're Stuck]

If you've made 3+ failed attempts to fix the same issue and the app is getting worse, stop. Use Caffeine's version history to roll back to the last working version and try a completely different approach. Layering changes on top of a broken state almost never works — it just costs more credits.

Revert instruction — be specific about the baseline

Revert the app to [version/description of last working state]. Something went wrong after [what you tried] — I want to go back to the clean baseline and try a different approach.

[Canister Startup Delay is Normal]

When you first open a freshly deployed Caffeine app (or one that hasn't been visited in a while), the backend canister may take 2–10 seconds to wake up. This is normal — the Internet Computer "cold starts" idle canisters. Wait a moment before assuming something is broken.

> Use the Browser Console

Open your browser's developer tools (F12 or Cmd+Option+I) and check the console when something looks wrong. It often shows the exact error, failed network call, or missing variable. Copy the error and paste it back to Caffeine or use another AI to get a targeted fix.

Console error prompt — paste the full error for best results

I'm getting this error in the browser console: [paste error here]. Here is the relevant component: [paste code]. Fix only the error — do not rewrite anything else.

> The Core Principle

Caffeine is a powerful tool — but it isn't magic. If you hit an error, never hesitate to ask it for a situational analysis. The builders who get the most out of it are the ones who treat it as a collaborator, not a vending machine.