Verified:GitHub

lovable-cloud-knowledge

Enforce authoring scope and precedence rules for Lovable knowledge-field instructions.

4|1|Updated Mar 11, 2026

Search Tags:#knowledge management #PR review #lovable #workspace skills #scope precedence #instruction governance #configuration workflow

Ready to run

npx skills add https://github.com/jcdendrite/claude-config --skill lovable-cloud-knowledge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lovable-cloud-knowledge
Source: https://github.com/jcdendrite/claude-config/tree/main/plugins/lovable-cloud/skills/lovable-cloud-knowledge
Command: npx skills add https://github.com/jcdendrite/claude-config --skill lovable-cloud-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It resolves inconsistent or drifting Lovable instructions by defining how Project Knowledge, Workspace Knowledge, and Workspace Skills should be authored, scoped, prioritized, and reviewed.

Core Features & Use Cases

Knowledge precedence & scoping: Ensures project-specific rules live in Project Knowledge while cross-project conventions stay in Workspace Knowledge, with clear conflict resolution.
Repo mirror workflow: Treats .lovable/*.md as version-controlled mirrors of Lovable UI fields so changes can be reviewed and audited instead of being pasted ad hoc.
PR review checklist: Provides targeted review criteria for both knowledge files and workspace skill bodies, including perspective, specificity, scope, and character budget management.

Quick Start

Review or author updates to .lovable/project-knowledge.md, .lovable/workspace-knowledge.md, or .lovable/skills/*.md using the skill’s checklist, then bump the “Last synced to Lovable UI” date in the PR and paste the merged content into the Lovable UI after merge.

Frequently Asked Questions about lovable-cloud-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage Lovable project knowledge conflicts with workspace knowledge?▼

Manage Lovable knowledge conflicts by scoping project-specific rules in Project Knowledge and cross-project conventions in Workspace Knowledge, applying defined precedence rules to resolve overlaps during PR review.

What is the best way to version control Lovable UI instructions?▼

Version control Lovable UI instructions by treating `.lovable/*.md` files as repo mirrors, updating them via PRs, and pasting merged content back into the Lovable UI.

How do I review updates to Lovable workspace skills?▼

Review Lovable workspace skills by applying a checklist that verifies internal engineering perspective, specificity to prevent over-application, conflict scoping, and adherence to char-budget limits.

Does the Lovable knowledge workflow require manual synchronization?▼

The Lovable knowledge workflow requires manual synchronization by bumping the “Last synced to Lovable UI” date in the PR and pasting the merged content into the Lovable UI after merge.

Why should I use a repo mirror workflow for Lovable configuration files?▼

Use a repo mirror workflow for Lovable configuration files to ensure that instruction changes are audited and reviewed through version control instead of being pasted ad hoc.

When do I need to enforce scope precedence for Lovable workspace skills?▼

Enforce scope precedence for Lovable workspace skills when authoring updates to `.lovable/skills/*.md` to eliminate ambiguity and prevent instructions from over-applying across project boundaries.