ContentForger

How to work with the AI

Seven habits that get better results from the ContentForger app builder. Each one uses a button or panel that is already on the build screen.

By Thomas Lovas Lokoy · Updated 13 November 2026

  1. 1. One change per message

    Each message in the project chat becomes one change and one new version with its own diff. Small, single-purpose messages are applied as small edits, are easy to check in the diff, and are easy to undo by opening the version before. A message that asks for five things at once is more likely to miss one.

  2. 2. Attach screenshots and files

    Use Attach files under the prompt or in the chat: a screenshot of a design you like, a screenshot of the problem, a .md or .txt with your texts, a .docx brief or a short PDF spec. Up to 5 files of 10 MB each. They are stored privately, read by the AI for that message, and never copied into your app's code, ZIP or public preview.

  3. 3. Use Plan first for anything bigger

    Tick Plan first and the AI only plans: you see the pages, features, data files, stack and every file it intends to write, before anything is written. Press Build this, change the plan in your own words, or cancel. Building from the plan does not run the planner again.

  4. 4. Press Fix errors instead of describing errors

    When the live preview shows an error, the Fix errors button sends the exact error text to the project chat queue. That is more precise than retyping it, and it is applied like any other message.

  5. 5. Lock what you like in the AI profile

    The project's AI profile works like a short instruction file for that app: its goal, audience, brand words, rules, and a do-not-touch list for parts you are happy with. About me (in Settings) holds your own preferences for every project: skill level, tone, design taste, default stack, always and never. Both are sent to the AI with every plan and change. When the chat suggests a rule, you decide whether to save it.

  6. 6. Check speed with a real measurement

    Run PageSpeed from the build screen on your deployed address (or on our preview, which is not your final hosting). Fix with AI sends the failed audits as one chat message; Test again compares with the previous run on the same address. One run can move by 10 points or more, so compare several runs before drawing conclusions.

  7. 7. Keep keys in the key vault, not in messages

    Put API keys in API keys (or pick a preset under Integrations). The AI only ever sees the names and writes code that reads them from the environment; the values stay encrypted and never enter your code.