AI app builders create new projects. What about the one you already have?

Bolt.new, Lovable, and v0 can generate entire applications from a prompt. But if you already have a website in a Git repo, you need something that works with your existing code instead of starting over.

What AI app builders do

A new generation of tools lets you describe an application and get working code in seconds. Each takes a different approach:

Bolt.new (by StackBlitz)

Type a prompt, get a full-stack application in seconds. Bolt runs a WebContainer in your browser, generates code across multiple files, installs dependencies, and gives you a live preview to iterate on. You can deploy to Netlify or download the source code. It supports multiple frameworks and can scaffold both frontend and backend code from a single conversation.

Lovable

Similar concept, more polished output. Describe the app you want and Lovable generates a working prototype with clean code. It builds primarily with React and integrates with Supabase for authentication and databases. The results look more finished than what you'd get from a typical code generator.

v0 (by Vercel)

Vercel's take on AI code generation, focused on UI. Give it a text description or an image and it produces React components using shadcn/ui and Tailwind CSS. It's good at individual components and page layouts. v0 doesn't try to build entire applications; it creates the building blocks you'd assemble into one.

All three are good at the same thing: going from zero to something. They take a blank canvas and create a working application or component. If you're prototyping or building an MVP, they'll save you real time.

The existing codebase problem

Most teams aren't starting from zero. They have:

AI app builders don't connect to any of this. They generate new code in their own environment. The output ignores your existing components, your design system, and your deployment pipeline because it has no way to see them.

You can't paste a Bolt.new project into your existing codebase and expect it to work. The architecture won't match. The dependencies will conflict. You'd spend more time reconciling the generated code with your existing code than it would take to just write the change yourself.

Building vs. changing

These are different activities, and they need different tools.

Building means creating something new

You start with requirements, make architectural decisions, set up tooling, and write code from scratch. AI app builders work well here because there are no constraints. The AI picks the framework, the file structure, the component patterns. It doesn't have to worry about breaking anything because nothing exists yet.

Changing means modifying something that already exists

You need to understand what's already there, preserve what works, and modify only what needs to change. That requires different capabilities:

  • Reading existing code and understanding its patterns
  • Making targeted changes without breaking adjacent functionality
  • Following established conventions for naming, file structure, and styling
  • Testing that changes work within the existing system
  • Deploying through established processes

AI app builders are optimized for building. They generate comprehensive output but can't read your existing code or produce targeted diffs against it. They start from scratch every time because that's what they were designed to do.

How Intentify works with existing sites

Intentify does the opposite of these tools. Instead of generating new projects, it reads your codebase and makes targeted modifications to it.

Connects to your repository

Intentify clones your GitHub repository and reads your source files. It sees your components, your styles, your configuration. Changes are generated in the context of your real code, not in an isolated sandbox.

Understands your stack

React, Vue, Next.js, Nuxt, plain HTML -- Intentify detects your framework and generates code that fits. If you use Tailwind, it writes Tailwind classes. If you have a component library, it uses your existing components instead of creating new ones. The generated code looks like your team wrote it.

Makes targeted changes

Instead of generating an entire new page or application, Intentify modifies the specific files that need to change. If you want to update a heading and adjust some padding, it changes those lines in those files. The rest of your codebase stays untouched. The diff is small, reviewable, and predictable.

Creates pull requests

Changes appear as pull requests in your existing GitHub workflow. Your team reviews the diff the same way they review any other code change. CI runs, tests pass (or don't), you merge when you're ready. Your deployment process stays the same. It's just a PR in your repo.

Visual interface for non-technical users

Non-technical team members use a Chrome extension to annotate directly on the live site. They highlight elements, describe what they want changed, and preview the result before submitting. The person who knows what needs to change can request it without opening a terminal or learning your tech stack.

Same idea as AI app builders (AI writes the code), but pointed at your existing codebase instead of a blank canvas.

Questions

Can I use Bolt.new to modify my existing website?

Not directly. Bolt generates new projects in its own environment. You'd need to manually port the generated code into your existing codebase, which typically requires a developer to reconcile the differences in architecture and dependencies.

Is v0 useful for existing projects?

v0 generates standalone components that you can copy into your project. It's useful for design inspiration and prototyping individual components, but it doesn't read your existing code or create pull requests against your repo.

What if I built my site with Lovable and now want to make changes?

If you exported the code to a Git repository, Intentify can connect to it. If the site still lives inside Lovable's platform, you'd make changes there. Intentify works with code in Git repositories.

Do I need a developer to use Intentify?

You need a developer to initially connect your repository and to review pull requests. Once set up, non-technical team members can submit changes independently. The developer's role shifts from implementing changes to reviewing them.

Change your existing website without rebuilding it.

Create your free account and submit your first change today.

Get Started Free

Free to start. No credit card required.