What to Ask Your AI

This page is a cookbook of prompts. Each one does one common job. Copy it, change the words in capitals, and paste it into your AI assistant. Each prompt points your AI at the guide that explains the job, so it can follow the Insites way.

Before You Use These Prompts

• Your AI assistant is connected to Insites CloudShell. See Start Here: Build with AI.
• Your AI has read the Insites Logic Engine in this conversation. If you start a new conversation, paste the Logic Engine prompt again first. See Insites Logic Engine.
• Your staging instance is selected. Every prompt below asks your AI to work on staging and to check the logs.
• Ask for one job at a time. Check the result before you ask for the next one.

Pages and the Menu

Add a Page to the Menu

Use it when you have a new page and want a link to it on every page.

On my staging instance, add a page at /ABOUT with the title ABOUT US
and this text: PASTE YOUR TEXT. Add a link to it in the menu, which
lives in the layout or in the header partial the layout uses, so it
shows on every page. Deploy, check the logs, and give me the address.

Guide: Layouts

Set the Page Title and Description for Search

Use it so search engines and social sites show the right title and summary for each page.

On my staging instance, give every page a title and a description in
its metadata, and make the layout print them in the page head, as shown
at https://docs.insites.io/developers-guide/metadata
Show me the list of titles and descriptions before you deploy.

Guide: Metadata

Forms and Email

Build a Contact Form

Use it when visitors need a way to send you a message.

On my staging instance, build a contact form at /CONTACT with the fields
name, email and message. Save each message in a table. Add spam
protection to the form. Email me at MY-EMAIL-ADDRESS when someone sends
a message. Deploy, send one test message, and check the logs.

Guide: Building a Contact Form

Note: A staging instance only emails the test recipients set in the instance settings. Add your own address there first, or the test email will not reach you.

Send an Email

Use it when your site must email someone after something happens, such as a sign-up.

On my staging instance, create an email notification called WELCOME
that is sent when SOMEONE SIGNS UP. Use this subject: SUBJECT, and this
text: PASTE YOUR TEXT. Send it from an address on MY-DOMAIN. Deploy,
trigger it once as a test, and check the logs.

Guide: Creating an Email Notification

Sign-In and Access

Sign In Without Passwords

Use it when people should sign in with a link or a code sent to their email.

On my staging instance, build passwordless sign-in with an emailed
LINK (or: 6-digit code). Follow
https://docs.insites.io/developers-guide/passwordless-sign-in step by
step, including the same answer for every address and the limit on
attempts. Deploy, test it with my email address, and check the logs.

Guide: Passwordless Sign-In

Let Only Listed People Sign In

Use it when only certain email addresses may sign in.

On my staging instance, add an email allow-list to my sign-in, as shown
at https://docs.insites.io/developers-guide/email-allow-list
Use a table of allowed addresses. The page must give the same answer
whether or not the address is on the list. Deploy and test both cases.

Guide: Email Allow-List

Restrict a Page to Signed-In People

Use it when a page must not be open to everyone.

On my staging instance, protect the page at /MEMBERS with an
authorization policy so only signed-in people can open it. Send
everyone else to /SIGN-IN. Deploy, then test it once signed in and once
signed out, and tell me what each one showed.

Guide: Associating an Authorization Policy with a Page

Data

Add a Table

Use it when your site needs to store a new kind of data.

On my staging instance, add a table called MEMBER with these fields:
FULL NAME, EMAIL, and JOINED ON (a date). Choose the field types from
the Insites Logic Engine and explain them to me. Deploy the schema file
and check the logs.

Guide: Database Fields and Tables

Show Records on a Page

Use it when you want a list of stored data on a page.

On my staging instance, show the 20 newest records from the MEMBER table
on a page at /MEMBERS, newest first, with their FULL NAME and JOINED ON
date. If the table is empty, show a short message instead. Deploy and
check the logs.

Guide: Querying Your Databases

Import a Spreadsheet

Use it when you have data in a spreadsheet or an export from another system.

I have a spreadsheet saved as CSV at PATH-TO-FILE. Import it into the
MEMBER table on my staging instance, following
https://docs.insites.io/developers-guide/importing-json-or-csv-data
Convert it to the import format first, and show me the first five rows
before you import. After the import, count the records and compare the
count with the number of rows in my file.

Guide: Importing JSON or CSV Data

Note: Data can be loaded with the Insites CLI, the GraphQL import mutations or a migration. Your AI will tell you if it needs the CLI installed on your computer.

Languages and Secrets

Translate the Site

Use it when your site must work in more than one language.

On my staging instance, make the site work in ENGLISH and SPANISH.
Follow https://docs.insites.io/developers-guide/multi-language-sites
Move every piece of text into translation files, one file per language,
and let visitors choose their language. Deploy and show me both
languages.

Guide: Multi-Language Sites

Store an API Key Safely

Use it when your site needs a key for an outside service.

Store this key as an environment variable called SERVICE_API_KEY on my
selected instance: PASTE KEY. Read it in the code with
context.constants.SERVICE_API_KEY. Never write the key into any file,
any page or the logs.

Guide: Safety Rails for AI Builds

GitHub, Logs and Errors

Connect GitHub

Use it once per instance, so every change has a history you can undo.

Connect GitHub to my instance. Give me the install link. Tell me to
choose Only select repositories and one repository. When it is
connected, tell me the repository and the branch it watches.

Guide: Insites GitHub App

Check the Logs After a Deploy

Use it after any change, even when the page looks fine.

Check the status of my last deploy and the logs on my selected instance
since that deploy. List any errors in plain words, and say which file
each one comes from.

Guide: CloudShell Tools

Fix an Error

Use it when something is broken or looks wrong.

Something is wrong on my staging instance: DESCRIBE WHAT YOU SEE AND WHAT
YOU EXPECTED. The address is ADDRESS. Check the deploy status and the
logs, find the cause, and explain it in plain words before you change
anything. Check the gotchas file for this topic in the Insites Logic
Engine first. Then fix it, deploy, and check the logs again.

Guide: When Your AI Gets Stuck

Related

• Start Here: Build with AI
• CloudShell Tools
• What Insites Can Do
• Insites in Plain Words
• When Your AI Gets Stuck