Automated summary
This skill reads, summarizes, and emulates the system prompt and tool schemas of Lovable, a web app building agent.
Strengths
- Access to Lovable's actual published prompt text
- Ability to quote or summarize accurately
- Clear structure for emulating Lovable's style
Limitations
- Source files may drift from the live product
- Requires reading attached files, no paraphrasing from memory
- Does not provide a build tool directly, only analysis
When you need to analyze, compare, or recreate Lovable's agent prompting style.
When you need a generic web app builder without referencing Lovable's specifics.
Security analysis
SafeThe skill is purely informational; it contains no executable instructions, destructive commands, or sensitive data exfiltration risks. It only references external source files for reading, without executing any tools.
No concerns found
How this analysis is madeExamples
Read the file 'sources/Agent Prompt.txt' and summarize its key sections and instructions.Using the structure from 'sources/Agent Prompt.txt' and 'sources/Agent Tools.json', help me design a prompt for a web app builder that follows Lovable's approach.Compare the tool schemas in 'sources/Agent Tools.json' with Claude Code's default tools. Highlight similarities and differences.name: lovable description: Reference system prompt and tool schemas for Lovable. Use when imitating, comparing, or analyzing Lovable's prompting style; designing prompts inspired by Lovable; or answering questions about how Lovable is prompted.
Lovable
Lovable web app builder agent prompt and tools.
When activated, read the bundled source files below to ground your response in the actual published prompt text. Do not paraphrase from memory — the canonical content lives in these files.
Source files
sources/Agent Prompt.txt(20,301 bytes)sources/Agent Tools.json(27,944 bytes)
Usage
- Quote or summarise from the files above when answering "how does Lovable prompt its agent?" style questions.
- When emulating Lovable's style, mirror its structure (sections, tool-use rules, refusal patterns) rather than copying verbatim.
- These prompts were collected by the upstream
x1xhlol/system-prompts-and-models-of-ai-toolsrepo and may drift from the live product over time.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/lovable-system-prompt-and-tools-mrwakfnp/download' --output '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md.part' && mv '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md.part' '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md' && test -s '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/lovable' && cp -R '.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp' '.claude/skills/lovable'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/lovable-system-prompt-and-tools-mrwakfnp'openskills read 'lovable-system-prompt-and-tools-mrwakfnp'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/lovable-system-prompt-and-tools-mrwakfnp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.