You're exploring a live demo — every feature is clickable.

Start free trial

Prompt Builder

Collect data from your dashboard and generate a comprehensive prompt for your AI agent or developer.

Sample output
How the Prompt Builder works
As you browse your dashboard, click “Add to Prompt Builder” to collect findings — analytics snapshots, AI insights, competitor analyses, speed and uptime data. Then the AI synthesizes everything into one ready-to-hand-off document: an improvement prompt for Claude, ChatGPT, or your developer, or a Claude Code skill you drop straight into your project.
Improvement Prompt

A markdown prompt for Cursor, Claude Code, or your developer with prioritized actionable improvements.

Claude Code Skill

A reusable Claude Code skill (.md with frontmatter) you can drop into your project's skills folder.

Generated prompt
What the Prompt Builder produced for Winterline Architects from 4 collected data sources.
Sample output
# Improvement Prompt — Winterline Architects (winterlinearchitects.com)

## Context
Winterline Architects is a twelve-person architecture practice in
Portland, Oregon, working on houses, renovations, ADUs and small
commercial buildings. WordPress + Elementor. The site's job is to turn
someone browsing project photography into a sent enquiry; everything
else is secondary.

## Key findings (from Crafty Meerkat analytics, last 30 days)
- 14,305 page views, 6,637 visits, 4,628 visitors; 53% on mobile
- 162 visits reached /contact, 43 sent the form — 27% completion
- Pinterest and Instagram: 1,343 visits, 1 enquiry between them
- Houzz: 405 visits, 5 enquiries — the best-converting source by rate
- /projects/* average 2.3s to load; the rest of the site averages 1.1s
- 4 project pages have no meta description
- No LocalBusiness structured data anywhere on the site

## Prioritized tasks

### 1. Cut the enquiry form to three fields (high impact)
/contact currently asks for name, email, phone, address, project type,
budget range, timeline, how-you-heard and a message before it can be
submitted. Three quarters of the people who reach it leave. Reduce to
name, email, and "tell us about your project"; ask the rest in the
reply. Add one line above the form: what happens next, and how soon.

### 2. Fix project page weight (high impact)
Project pages serve full-size photography — several images over 2MB —
to an audience that is 53% mobile. Resize to the displayed dimensions,
serve WebP with a JPEG fallback, and lazy-load everything below the
first image. Target under 1.2s on a 4G connection.

### 3. Add LocalBusiness structured data (SEO + AI visibility)
Nothing on the site states the practice's address, phone, hours or
service area in a machine-readable form. Add a LocalBusiness JSON-LD
block sitewide with the studio address, (503) 555-0148, and a service
area covering the Portland metro and the Columbia Gorge.

### 4. Give every project page a next step
Project pages hold attention longer than anything else and then
dead-end. Close each one with a link to its service page and a single
line inviting an enquiry.

## Acceptance criteria
- /contact submits with three fields and no required phone or budget
- Largest project image under 300KB; project page LCP under 1.2s on 4G
- LocalBusiness JSON-LD validates in Google's Rich Results Test
- Every /projects/* page links to a service page and to /contact
- All eight project pages carry a unique meta description under 160 chars

Generate prompts like this from your own site's real data.

Start free trial