Getting Started with the Knack + Lovable Build Kit

What You'll Learn

The Knack + Lovable Build Kit helps you build a web app in Lovable with Knack as the backend, including sign-in, user roles, and data access that actually protects your records. This article explains what's in the kit, the two ways to use it, and how to set it up.

What the Knack + Lovable Build Kit Is

The Knack + Lovable Build Kit is a set of guides and fill-in templates for building a Lovable app on top of a Knack app. Knack stores your data, manages user accounts, and controls who can see which records. Lovable builds the screens your users see.

The kit is built on two ideas. First, frontend builders don't stop and ask when your instructions are incomplete. They guess, and every guess costs time and credits to undo. Second, some failures look exactly like success, so the kit tests your app by comparing two results instead of checking whether one screen looks right.

Download the Knack + Lovable Build Kit

Download the Kit Files here

• 00 Start Here
• 01 Plan Your App
• 02 Your Knack Backend
• 03 Design Your App
• 04 Knowledge File
• 05 Build Prompt
• 06 Build and Verify
• Quick Start: Zero to App
• Guided Project Instructions
• Provenance and Changelog

What's Included in the Knack + Lovable Build Kit

Each numbered file produces something you use in the next step.

The kit also includes three supporting files:

• Quick Start: Zero to App is a condensed path for anyone starting with no Knack or Lovable account.
• Guided Project Instructions lets an AI assistant walk you through the kit as an interview.
• Provenance and Changelog records why each rule in the kit exists and when it can be retired.

Choosing How to Use the Knack + Lovable Build Kit

You can use the kit in two ways. Both produce the same app.

Guided. You set up the kit once in a Claude Project, then answer questions about your app. The assistant works out which rules apply to you and hands you each piece already filled in. This is the faster option for most people.

Self-directed. You read the files and fill in the templates yourself. It's slower, but you see every decision, which helps if you want to understand how Knack works rather than just ship an app.

Setting Up the Guided Version in a Claude Project

Setup takes about five minutes, and you only do it once.

1. Create a new Project in Claude or ChatGPT.
2. Open the Guided Project Instructions file, copy all of it, and paste it into the project's instructions field.
3. Upload these eight files to the project's knowledge: 00 through 06, plus Provenance and Changelog.
4. Start a new conversation in the project and type start a new app build.

The assistant asks the first question and takes it from there.

Adding the Knowledge File to Lovable

The Knowledge file holds standing instructions that Lovable applies to every request in your project. You add it in two stages: the platform corrections first, then your app's details once they exist.

To open Knowledge in Lovable, click the plus icon, then Projects, then Knowledge. Paste your content and save.

Don't edit or shorten the corrections in the Knowledge file. Each one is there because leaving it out produced an app that looked like it worked and didn't.

The Order of Steps Matters

Follow the kit in order. Two steps are hard to undo if you do them out of sequence.

Set up and test Data Access Control before you build. Data Access Control decides whether a user's records are really theirs. If you build on a wrong setup, records get attached to the wrong person with no error.

Publish your Lovable project before you register sign-in. Your project's web address changes when you publish, and the sign-in registration can't be edited afterward. Once published, never rename the subdomain.

Configuring Data Access Is Not the Same as Enforcing It

Filling in the Data Access grid in the Knack Builder doesn't turn it on. Until you toggle Enforce data access rules for App on, every user can see every record, and a yellow Action Required banner stays on the page.

You can ask Lovable to configure Data Access for you through the Knack MCP Server, or set it up yourself in the Builder. Either way, open the Builder afterward and confirm the grid is filled in and enforcement is on.

See Data Access Control for how the grid works.

Testing Your App After the Build

The kit's tests each compare two things, because Knack often refuses a request by returning an empty result rather than an error. A denied record and a record that doesn't exist look the same on screen.

Your frontend builder can't run these tests for you. It doesn't have an account and can't sign in to your app, so run them yourself in a regular browser tab at your published address. File 06 walks through each test and what a pass looks like.

Choosing Between Your Own Data and Sample Data

The kit supports two ways to fill your Knack app. You can import data you already have, like a spreadsheet or an export from another system. Or you can have the AI assistant generate realistic sample data as CSV files for you to import. You can also test with sample data first and bring in your own later.

When you import a connection column, Knack lets you choose which field in the connected table to match on. Pick a unique field, like an email or ID number.

Imported records in data tables are owned by the App Builder, not your users. After each import, use a batch update to set Owned By to the connection field that points to each record's owner. Otherwise your users won't see their own imported records.

See Importing Data and Setting Record Ownership After Importing Data.

Using the Default Role as Your Holding Role

Knack's Default Role catches anyone who signs up without choosing a role. The kit uses it as your holding role, so you don't need to create a separate Pending Users role.

Set the Default Role's registration to approval required. In Data Access, give it View Only on its own records and No Access to everything else. View Only is the lowest setting Knack offers for records a user owns. For more on this choice, see Choosing a Default User Role for a Custom Frontend.

Before You Store Sensitive Data

If your app will hold protected health information, personal data, or research data about people, talk to your legal counsel before storing real records. Knack offers HIPAA-compliant plans. Any tool you use outside Knack needs its own compliance review. Start with fabricated sample data either way.

Keeping Your Knack + Lovable Build Kit Up to Date

Files you upload to a Claude Project are copies. They don't update when the kit updates. When a new version of the kit is released, re-upload the files to your project, or it keeps working from the old version with no warning.

Common Mistakes

• Skipping straight to the build prompt. Without the plan and backend steps, the prompt is incomplete and Lovable fills the gaps with guesses.
• Testing sign-in in Lovable's chat preview. Sign-in doesn't work there. Use your published address in a regular browser tab.
• Creating user roles as regular tables. A role created as a data table can't be converted. Check that every role appears under User Roles in the Builder, not under Tables.
• Skipping the ownership update after import. Imported records are owned by the App Builder until you batch update them.
• Trusting the AI's report. Check the Builder and run the tests yourself.

Next Steps

• Connecting Lovable to Knack: Complete Setup Guide covers connecting the Knack MCP Server to your Lovable project.
• Knack MCP Server explains what the MCP Server does while you build.
• Data Access Control explains how to control which records each user role can see.