AI Agent Use Cases
Views —

AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

Marketing & Design

Creating an Invitation Webpage by Describing It in Words

They described their desired look to Cursor and created an invitation page with animations. They manually edited the final phrase and spacing in the code themselves.

Cursor

How it works

  1. In the first request, they specified the goal of creating an invitation using only the frontend. They described the desired components, including animations, images and text, and buttons to navigate between screens.
  2. They got stuck on the envelope-opening animation. Even after repeatedly requesting changes in words, there was no improvement, so they searched for HTML and JavaScript examples themselves, pasted code with changed colors into the prompt, and used it as a base.
  3. After the animation worked, they added buttons, fonts, and screen layouts. When creating other screens, they reused previous requests. There was an issue where styles only applied to the current screen unless specified as common styles.
  4. Once the page was about 90–95% complete, they started editing the code directly. For small adjustments like text, inner padding, and outer margins, it was faster to finish by hand.

Results

The author said they completed the invitation site in 2–3 hours. They estimated that it would have taken about 4–8 hours if they had built it themselves in their usual way.

Notes

They found it more helpful to provide reference examples than to vaguely ask for changes. Manual work was needed for the final detailed adjustments.

Source

DEV Community Original post ↗

Example prompt · Cursor

Please implement an event invitation webpage that can be viewed on both mobile phones and PCs.

Input: Event name [name], date and time [date/time], location [address], invitation message [content], image to use [file], reference screen [material]. First, check for any missing information and define the scope that can be implemented using only the frontend.

On the first screen, include the invitation, main text, event details, and links for location and contact. For animations like opening an envelope, use the provided reference as a basis, and ensure that content is immediately readable when motion reduction is enabled. Manage fonts, colors, buttons, and spacing as common styles across multiple screens.

If the desired behavior is not achieved, do not repeatedly request vague changes. Instead, explain the differences between the current result and the reference example, then change only the relevant part. When you receive example code, use only the necessary parts to match the existing screen.

Deliverable: A working page and preview, with instructions for replacing text and images. Check that there is no horizontal scrolling on mobile, that the date and address are correct, and that buttons, links, and keyboard navigation work.