FREE SHARED SKILL · BUILD / PORTABILITY

Use Lovable to build the project. Do not make Lovable the project.

The Lovable Portability Guardrail is a reusable pre-project instruction set for turning a Lovable membership into code and working systems you retain. It keeps GitHub as the source of truth, makes Cloudflare-ready independent deployment the default, and keeps authentication, data, email, storage, secrets, and external services under accounts you control.

FreeCurrentCopy / adapt / use

Open the full skill All shared skills

The operating model

Lovable → GitHub → Cloudflare optional source production builder of truth deployment ↓ services you control auth · database · email · storage · APIs

What it prevents

Accidental platform lock-in.The skill rejects implementations where cancelling Lovable would break the application, authentication, database, storage, email, deployment, or normal maintenance.

What it preserves

Code, configuration, migrations, functions, operational knowledge, and provider ownership.The repository carries the rebuild path. Secrets remain outside source control, and direct provider accounts remain yours.

Default stack

GitHub + Cloudflare + independently owned services.Supabase is a practical default for PostgreSQL, auth, and storage; Google OAuth credentials stay in your Google Cloud project; transactional email can use Resend, Postmark, SES, or another provider you control.

The test

Before a major feature is considered complete, ask one question:

Could I clone this repository on a new machine, configure the documented environment variables, deploy it without opening Lovable, and keep the complete application working?

If not, redesign the dependency. Lovable can remain a useful development interface. It should be optional to production.

Why share it

This came from a practical lesson: AI development tools are most valuable when the speed they provide becomes durable work you own. The full skill includes the pre-project prompt, architecture rules, OAuth and email boundaries, migration requirements, an EXIT.md convention, and a portability QA checklist.

Read / copy the skill

Free-tier hosting depends on the workload and provider limits. The architecture is intentionally free-tier-capable for suitable small projects, not a promise that every application will cost $0 forever.