Updated 245 chained refinement prompts in the libraryDocs re-read 23 Oct 2026

    Advanced Lovable prompting: Skills, goals, Plan mode and prompt chains

    Advanced prompting in Lovable is using the controls around the chat box: the mode picker (Build, Chat, Plan), the slash menu with Skills and /goal, the @ menu for other projects and files, and chained follow-up prompts against a build that works. Each has a different cost and a different job. The library here carries 245 chained refinement prompts, counted from the data, and one rule changes how you write a goal: Lovable stops asking questions once a message is set as a goal.

    By Marco Kohns · Every description re-read in Lovable's docs on 23 October 2026

    10hours

    The longest Lovable works on one Build message or goal; the last half hour wraps up.

    20credits

    The default credit check-in: a long message or goal pauses and asks before going on.

    245refinements

    Chained prompts across the 8 library categories, each run after a working build.

    The controls

    What makes a Lovable prompt advanced?

    Length does not. These five mechanisms do, and each is documented by Lovable.

    Lovable's advanced prompting mechanisms: what each does, when to use it, its cost or limit, per the docs read 23 October 2026
    MechanismWhat it doesUse it whenCost or limit
    Plan modeInvestigates and writes a plan; changes no code until you approveA fix missed twice, or a feature needs scoping1 credit per message plus subagent research
    Chat modeDiscusses the open app without editingYou want to understand before decidingA fraction of a credit, daily chat allowance first
    SkillsWorkspace-level instructions loaded on demand when a request matches, or picked from the slash menuA task repeats: a release checklist, a content formatCreated by workspace owners and admins; Lovable ships built-in ones
    /goalA Build message Lovable keeps working on until the goal is achievedA large task you want finished in one messageUp to 10 hours; pauses at the credit check-in
    @ referencesReads another project's files, patterns and chat history; the referenced project stays unchangedReusing a brand, a component or a solved problemRead-only on the source project
    The Lovable chat input with the mode picker open after the SaaS build: Build, make changes directly; Chat marked Free, ask anything; Plan, detailed spec for complex builds; and the Switch modes shortcut
    The mode picker under the chat input; Option+P or Alt+P cycles the three modes. My workspace, 26 September 2026.

    Sources, read 23 October 2026: Plan mode, project chat, Skills, goals, cross-project references.

    Chaining

    How do you chain prompts without breaking what already works?

    Run the next prompt against a build that works, name the one change, and say what stays untouched.

    Lovable's best practices define a change prompt in three parts: what to build, where it goes, and what must stay untouched. Every Pro variant in the library ends with a numbered Refinement Prompts section written that way, to run after the base build. The counts below come from the data.

    Chained refinement prompts per library category, counted from the Pro variants at build time
    CategoryRefinement prompts
    App Builder60
    API & Integration32
    Backend Logic30
    SaaS App30
    UI/UX28
    Landing Page25
    CRM App20
    Admin Dashboard20

    Chain

    A refinement that holds

    • Names the thing that already exists
    • Asks for one change
    • States the rule that must still hold
    • Runs after you checked the last build in the preview

    Break

    A refinement that regresses

    • Re-sends the whole original prompt
    • Bundles three features with and
    • Leaves the boundary unstated, so Lovable may touch working parts
    • Runs before the previous build was checked

    Reuse

    When do you use a Skill, project knowledge or a goal?

    Three mechanisms for three jobs. The docs draw the lines.

    Always on

    Project knowledge

    “Always included in context.” Rules for everything: audience, naming, the style keywords, roles. Project and workspace knowledge hold 10,000 characters each; a root AGENTS.md is always read too.

    On demand

    Skills

    Loaded “when the request matches” or picked from the slash menu. Instructions for one kind of task. Workspace owners and admins create them; Lovable's built-in Skills cover accessibility checks, redesigns, SEO reviews and more.

    One message

    A goal

    A Build message that runs until the goal is achieved, up to 10 hours. Lovable makes routine decisions itself and stops early only for something only you can provide, such as access to another service.

    Quotes from Skills and Knowledge, read 23 October 2026.

    Goals

    How do you turn a library prompt into a goal Lovable can finish alone?

    Replace the question line with the answers. Lovable does not pause to ask questions during a goal, so the decisions have to be in the message.

    Every library prompt ends by asking Lovable for its questions, because in a normal Build message that saves a correction round: on my runs Lovable asked up to four. A goal works the other way. The goal docs ask for three things in the message: what a finished result looks like, the decisions you care about, and access to other services set up before you send it. The Done When section of a library prompt already describes the finished result, so the conversion is one section.

    A library prompt, converted to a goal

    Build the team habit tracker described below and keep working until every item under Done When passes. /goal
    
    [the library prompt, Context to Safe-Guard Instructions, unchanged]
    
    ## Decisions Already Made (instead of Before Building)
    - Audience: team leads of remote teams of 3 to 20 people
    - Sign-in: email and password; no social login in this goal
    - A week starts on Monday in each user's own time zone
    - Teams are private: nobody sees another team's habits
    - Stop and report if anything needs a service I have not connected

    A goal still pauses at the credit check-in, 20 credits by default, and costs what the work costs. Use it for a foundation you have already scoped; for a first build where you want to steer, keep the question line.

    Plan mode

    Which advanced prompts does Lovable recommend for debugging?

    Its debugging guide ships three, to run in Plan mode so you get analysis before anything changes.

    Plan mode

    Codebase audit

    When the project has grown and the structure feels wrong: misplaced logic, coupling between data and UI, overly complex code, as an ordered list of steps.

    Plan mode

    Performance audit

    When it works but feels slow: duplicated network and database calls, components that re-render too often, large assets, ordered by expected impact.

    Build mode

    Fragile change

    Before touching sign-in or payments: examine related code first, avoid unrelated components, pause and explain if anything is uncertain, then the task.

    Summarised from Lovable docs, Debug and improve your app, read 23 October 2026; the fix order is in the common mistakes guide.

    Meta prompting

    What are meta prompting and reverse meta prompting?

    Two techniques from Lovable's Prompting Bible, published 16 January 2025, that still hold.

    Before you run

    Meta prompting

    • Ask a model to rewrite your prompt to be more concise and detailed
    • Then check the rewrite against the sections a library prompt carries: states, access rules, Done When
    • Run the rewrite, not the draft

    After you fix

    Reverse meta prompting

    • When a debugging session ends, ask Lovable to summarise what broke and how it was fixed
    • Save that summary as a prompt or to project knowledge
    • The next project starts with the lesson

    Chains, already written

    Every Pro variant ends with refinement prompts that follow the chaining rule. The 122 base prompts are free.

    Disclosure: if you create a Lovable account through links on this page, we may earn a commission. It costs you nothing and does not change what we recommend. Create a free Lovable account

    Frequently asked

    What counts as an advanced Lovable prompt?

    One that uses Lovable beyond a single Build message: Plan mode to scope or debug, a Skill, a goal set with /goal, an @ reference to another project or file, or a chained refinement that names what must stay untouched.

    What is a Lovable goal and how long can it run?

    A Build message Lovable keeps working on until the goal is achieved, for up to 10 hours, using the last half hour to wrap up. It does not pause to ask questions about the work, stops early only for something only you can provide, and pauses at your credit check-in level, 20 credits by default.

    Should I keep the question line when I set a prompt as a goal?

    No. A goal does not pause for questions, so replace the Before Building line with the decisions themselves: audience, sign-in method, privacy rules, edge cases. The Done When section of a library prompt already tells Lovable what finished looks like.

    What is the difference between a Skill and project knowledge?

    Knowledge is always in context and suits rules that apply to everything. A Skill loads on demand when a request matches its description, or when you pick it from the slash menu, and suits one kind of task. Workspace owners and admins create Skills; Lovable also ships built-in ones.

    When should I switch from Build mode to Plan mode?

    After one or two failed fix attempts. Lovable's debugging guide says repeated blind fixes pile up code that hides the cause, and Plan mode investigates without changing code. A Plan message costs 1 credit plus any subagent research.

    Can Lovable read another of my projects?

    Yes, with an @ reference in the chat: it can explore the other project's files, read its code and chat history, and reuse assets such as images and fonts. The referenced project stays unchanged.

    What we did not publish

    • A measured goal run. I have not set a library prompt as a goal yet; the conversion above follows the goal docs.
    • Credit costs for Skills, which run inside normal messages and are billed as such.
    • The 26 September description of Skills as available on all plans: the 23 October docs did not repeat it, so it is out.

    Sources

    1. Lovable docs: Skills, read 23 October 2026
    2. Lovable docs: Goals, read 23 October 2026
    3. Lovable docs: Plan mode and Subagents, read 23 October 2026
    4. Lovable docs: Cross-project referencing, read 23 October 2026
    5. Lovable docs: Debug and improve your app, read 23 October 2026
    6. Lovable blog: The Lovable Prompting Bible, 16 January 2025
    7. The library's Pro variants, counted at build time

    Written by

    Marco Kohns

    Marco Kohns

    Founder of ProtoBites - Venture Growth Studio

    Growth PM at a Silicon Valley scale-up (a16z and General Catalyst backed), ex-Techstars where he consulted 13 early-stage startups, Reforge-trained. Every prompt on this site comes out of shipping ProtoBites' own portfolio products.