Skip to content
Xylo Software

Markdown version · llms.txt

What to ask your agent

On this page

Your AI agent works in your GitHub repo. Speak like you would to a capable assistant. Short sentences. Real facts. The agent should open a pull request, show you the change, and wait for you to merge.

Pages and photos

  • “Change the homepage headline to ‘Open 6am to 8pm’.”
  • “Swap the hero photo for this image.”
  • “Add a page that explains how personal training works. Use only the copy I paste.”
  • “Put this Instagram caption and photo on the blog.”
  • “Add our address and phone to the footer. Phone is (614) 555-0123.”
  • “Redirect /old-class-pass to /packs.”

Do not let it invent prices, bios, testimonials, or results. If you did not supply the fact, it should ask.

Leads and follow-ups

  • “Rename the pipeline stage Booked to Trial booked.”
  • “Add a program called On-site visits.”
  • “Wait three days before the second follow-up text, and change the wording to …”
  • “Stop texting people who are already in Won.”

Plans, packs, and money

  • “Turn on memberships.”
  • “Add a plan called Unlimited, $149 every 28 days.”
  • “Add a 10-class pack for $120 that expires in 90 days.”
  • “Turn off Let members cancel online.” (You can also do that yourself in admin → Memberships.)
  • “Turn on invoices, with 14-day terms and no tips.”
  • “Turn on quotes.”
  • “Recorded payments should stay; just help me connect Stripe in test mode.” Then point them at Stripe setup.

Schedule and portal

  • “Turn on group sessions and the public timetable.”
  • “Let members book online, 14 days ahead.”
  • “Invite Maria from the customer list to sign in.” (You can also do that in admin.)
  • “Call customers members, sessions classes, and staff coaches.”

Files

  • “I uploaded a waiver in admin → Files. Put the signed-in-only link on the portal home.”

Give the slug from Copy link. Do not ask the agent to guess it.

Going live (technical)

These belong in the Technical section. Ask only when you mean it:

  • “Walk me through Stripe webhook setup for YOUR-DOMAIN.”
  • “Add the production env vars listed in hosting docs. Do not print secrets.”
  • “After we merge, confirm the Vercel production deploy succeeded.”

What the agent will not do (unless you clearly ask)

  • Dispatch the production database migration workflow, or approve a waiting production deploy
  • Merge a change without a pull request
  • Put secret keys in the repo
  • Invent business facts
  • Change the public /cms marketing page on xylosoftware.dev
  • Edit node_modules or generated sync files by hand

What it should check with you first

  • Prices, class times, staff bios, testimonials, and photos of real people
  • Turning a feature off that you already use (booking, memberships, invoices)
  • Anything that emails or texts your real customers
  • Ejecting (leaving Xylo). That is one-way. See Leave Xylo.

How a change goes live

  1. You ask.
  2. The agent opens a pull request.
  3. You read it (and a local preview, if they ran one).
  4. You merge with a merge commit.
  5. Vercel deploys main. If the change included database files, migrations apply automatically after a backup. See Backups and database changes.

Canonical: https://www.xylosoftware.com/cms/docs/ask-your-agent