Move from “it builds” to “someone can use it.”
Give Cursor the launch context and a concrete completion check before it starts changing files.
Start with a public URL. No account required for the first audit.
Audit https://example.com with LaunchBuddy. Pick one applicable conversion or technical gap, show the evidence, and implement the smallest fix in this codebase.
A finding. A useful resource. A finish line.
Separate launch, technical, and agent-readiness findings. Matching skills and guides. The next three actions, with evidence and a completion check.
Fix one gap, verify it, then learn from a real user.
Give Cursor the context.
The published installer adds LaunchBuddy’s skill and MCP bridge to Cursor. The downloadable packet contains the current focused recipes and references.
npx getlaunchbuddy install --allReview the actual change and keep publishing and account actions within the authorization you gave Cursor.
Try one useful request.
Audit https://example.com with LaunchBuddy. Pick one applicable conversion or technical gap, show the evidence, and implement the smallest fix in this codebase.Pair the fix with a mobile journey test. Observe the signup or first-value action rather than checking only the visual layout.
Audit the public URL
Use audit_my_launch and retain the returned JSON and native fix packs.
Find the right resource
Use search_launch_resources for a relevant skill, guide, or Swarm launch channel.
Check the result
Verify against the original finding after the authorized change is live. Missing evidence stays unknown.