Cursor for Facebook: Shop Posts from Your Repo

Cursor for Facebook

A small web shop adds products and features in the same repository where its developer works all day. The Facebook Page then lags behind, because writing a post means leaving the editor, finding the photo, remembering the price and typing it all again. Cursor is already in the repository, so it can read the product data, the changelog and the descriptions, and write posts that match. Tareno saves the result as drafts on the Page. This page follows a one-developer shop through a product launch, including what Cursor can verify in the code and what only the shop owner knows.

Example: a ceramics shop launches three new mugs

Imagine a ceramics shop whose developer-owner adds three mugs to the product data file and merges the change. In Cursor she asks for a Facebook post for each new item. Cursor reads the product file for names, colours and prices, finds the matching photos with list_media and notices that one mug has no price in the file. She fills it in. Cursor writes three posts of about 50 words each, uses the live product URLs as links and saves the drafts with create_drafts for the shop's Page. She checks stock in the shop admin, which Cursor cannot see, and requests a Thursday 18:00 slot for the first mug.

Step by step

1. 01

   Point Cursor at the product data

   Name the file or the commit that adds the products. Cursor reads names, prices and descriptions from the repository, which is more reliable than retyping them from memory.

2. 02

   Let it flag gaps in the data

   Ask Cursor to list products with missing prices, photos or URLs before it writes anything. A gap in the data becomes a hole in the post.

3. 03

   Match photos from the library

   Cursor looks for the product photos with list_media by name or tag and reports any product with no photo, rather than picking a lookalike.

4. 04

   Write one short post per product

   Ask for about 50 words per product with the price copied from the data and the product link in the text. Facebook shows a preview card for links in Tareno's configuration.

5. 05

   Save as Page drafts

   Cursor confirms the Page with list_accounts and saves the posts through create_drafts. Facebook publishes as the Page, so make sure it is the shop's.

6. 06

   Confirm stock, then request a time

   Check stock in the shop admin yourself, because Cursor sees the repository and not the warehouse. Then give a day, a time and an IANA time zone; the requests become pending actions you approve in the dashboard.

Prompts to copy

Read the new entries added in [commit or file] and list every product with a missing price, photo name or product URL. Do not write any post until I have filled the gaps, and say which fields you would use for the post text.

Use Tareno to look up the product photos for [mug names] in my media library and report which product has no matching photo. Return a table with product, price from the file and photo name.

Write one Facebook Page post of about 50 words for each new product, copying name, colour and price exactly from the product file and adding the product URL. Do not add claims about materials or shipping that are not in the file.

Use Tareno to confirm the Facebook Page [shop name] and save the three approved posts with their photos as drafts. Return a table with draft ID and product, and request no time until I have checked stock in the admin.

Mistakes to avoid

• Announcing a product that is not in stock. Cursor cannot see inventory, so check the admin before you approve a request.
• Trusting a price from a stale branch. Make sure Cursor reads the merged data, not an older working copy.
• Adding claims to the post. Anything about materials or care that is not in the product file should be checked by the owner.
• Posting the link to a product page that is not published yet. Open the link before you approve the request.