Amp vs LovableUpdated 2026-03-16

SUMMARY

Amp (CLI) uses markdown configuration while Lovable (Platform) uses markdown. They differ on 4 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

FeatureAmpLovable
Config formatmarkdownmarkdown
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file
IDE integrationCLIPlatform
Schema / structureFree-form (Markdown)Free-form (Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeAmpLovable
Project instructionsAGENTS.mdAGENTS.md

SIDE-BY-SIDE CODE SAMPLES

Amp
AGENTS.md
markdown
# Agent Instructions

## Project Context
Go microservices monorepo using Bazel for builds.

## Build & Test
- Build all: bazel build //...
- Test all: bazel test //...
- Integration tests: docker compose up -d && bazel test //integration/...
- Lint: golangci-lint run ./...

## Code Conventions
- All services follow standard layout in /cmd and /internal
- Use structured logging with slog
- Error wrapping with fmt.Errorf("op: %w", err)
- See @docs/api-style-guide.md for API conventions

## Cross-Repo References
- Shared proto definitions in sourcegraph/proto
- Common Go libraries in sourcegraph/lib

## Security
- Never log sensitive data (tokens, passwords, PII)
- All external inputs must be validated
- Use parameterized queries for database access

Lovable
AGENTS.md
markdown
# Project Instructions

## Stack
- React 19 with TypeScript
- Supabase for backend (auth, database, storage)
- TailwindCSS v4 + shadcn/ui components
- Vite for building

## Architecture
- Feature-based folder structure
- Each feature owns its components, hooks, and types
- Shared components in src/components/ui/
- All API calls go through src/lib/supabase.ts

## Conventions
- Use shadcn/ui components before creating custom ones
- Mobile-first responsive design
- Use Supabase RLS policies for authorization
- Prefer server-side filtering over client-side

## Brand
- Primary color: #6366F1 (indigo)
- Font: Inter for body, Cal Sans for headings
- Rounded corners (radius-lg) on all cards

KEY DIFFERENCES

1. Hierarchy support

Amp: Supported. Lovable: Not supported.

2. Global config

Amp: Supported. Lovable: Not supported.

3. Subdirectory scoping

Amp: Supported. Lovable: Not supported.

4. IDE integration

Amp: CLI. Lovable: Platform.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Amp, configure AGENTS.md. If you use Lovable, configure AGENTS.md. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh
bash
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md

SEE ALSO

Tool pages:
File references:
agentconfig.ing2026-03-16COMPARE(1)