Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.newly.app/llms.txt

Use this file to discover all available pages before exploring further.

The AI is making mistakes, undoing previous work, or consuming your monthly prompt limit without fixing the core issue.

​
Quick answer

Stop using single, massive prompts to build the entire app. Break your development into logical steps, provide screenshots of specific errors, and use Ask mode when you only need a question answered.

​
Steps to check your prompt usage

  1. Go to newly.app/pricing.
  2. Click the Usage tab to view your remaining prompts for the month.

​
Best practices for prompting

  • Iterate step by step: The ideal workflow is Prompt → Review App → Feedback Prompt → Review App. Do not paste a giant list of requirements into a single prompt.
  • Be specific: Avoid abstract commands like “fix the app” or “make things good”. Describe the exact user flow, the desired steps, and the expected outcome.
  • Use screenshots for errors: If you hit a build error or a visual bug, take a screenshot, upload it to the chat, and explain how you want it to look or function.
    Mac Press Shift + Control + Command + 4, then drag to select an area. The screenshot is copied to your clipboard, ready to paste with Command + V.
    Windows Press Windows + Shift + S to open Snipping Tool’s snip bar. Choose rectangular, freeform, window, or fullscreen mode, then make your selection. The screenshot is copied to your clipboard, ready to paste with Ctrl + V.
  • Use Ask mode for questions: If you are asking a question rather than requesting a code change, click the build dropdown and select Ask mode. This consumes 10x fewer prompts than a standard build request.
    Image
  • Read the prompts before sending: If you are copy-pasting a prompts from ChatGPT (or other LLMs), it’s best to read it to avoid sending something wrong and burning your prompt.
  • Make use of Restore function: If you have broken something that was working before, you can revert to a previous stable version by clicking “Restore” button next to it in chat history. In a lot of cases it would be easier to go back and redo than burn prompts on fixing.