Skip to main content
Fimo is an AI-native builder. Every time you send a prompt, credits are consumed:
  • When you generate new pages or layouts
  • When you ask Fimo to restyle or rewrite content
  • When assets are uploaded (captions and alt text are generated automatically)
Credits are valuable. The way you prompt and work with Fimo can stretch them further. This guide shows you how.
Before you read this guide: start with Prompt Engineering 101. It explains how to craft strong prompts. This page focuses on using them efficiently to save credits.

Principle: Create via AI, edit via UI

The golden rule in Fimo is: Create via AI, edit via UI.
  • Use AI to generate new things: pages, structures, or visuals.
  • Use the built-in editors (Content tab, Style editor, Media Library) for tweaks and corrections.
This avoids spending credits on small changes that the UI can handle instantly.

Plan before prompting

Prompts are cheaper when they’re well thought out. Before you hit enter:
  • Decide what type of page or section you need.
  • Note the must-have elements (e.g., hero, pricing, testimonials).
  • Think about tone and audience.
For a step-by-step framework on how to write effective prompts, see Prompt Engineering 101.

Be specific and focused

Vague prompts burn credits. Instead:
  • “Make it better.”
  • “Rewrite the hero headline to be shorter and more playful.”
Clearer prompts mean fewer retries and less credit usage. Learn more examples in Prompt Engineering 101 examples.

Work incrementally

Big, overloaded prompts often need fixing. Break them down:
  1. Generate the base page.
  2. Add a testimonial section.
  3. Translate into Spanish.
Step-by-step = cleaner results + fewer wasted credits.

Reuse and refine

Don’t prompt for things you already have:
  • Edit text directly in the Content tab.
  • Restyle elements visually in Preview.
  • Replace images via the Media Library.
This keeps credits for when you really need AI power.

Avoid repeated retries

If a result isn’t what you expect:
  • Rephrase once with more detail.
  • Or adjust it in the UI directly.
Repeated prompts asking for the same thing just drain your credit wallet.

Use History to undo

If a prompt creates unwanted changes, don’t burn more credits trying to undo it. Go to History and restore a previous version. It resets your content and code without spending credits.

Save strong prompts

When a prompt works well, save it in your own library. Reusing effective prompts avoids credit waste and makes your workflow faster.

What’s next?