AI and maps
Give your app’s AI custom context
Use the project’s AI tool to enter reference information in Always-use context, then choose Save context. Div-idy includes this information with supported text and image-understanding requests. It helps an existing AI feature answer in context; it does not create the feature, train a new model, or start a build.
Understand project memory and your instructions
The AI Context screen separates Project memory from Always-use context. Div-idy maintains project memory from the project plan, including the app’s goal, pages, design, integrations, and shared data. You provide the business facts and response rules in Always-use context.
Use the editable field for information such as workshop dates, service descriptions, cancellation policies, terminology, and answer style. Keep facts dated when they may change. The context field accepts up to 20,000 characters.
Add clear, useful reference information
- Build the AI interaction you need in the project prompt bar.
- Open the project’s AI tool and find AI Context.
- Add the facts, examples, and instructions the feature should use.
- Choose Save context and wait for confirmation.
- Test the AI feature with a question that depends on your saved information.
If context cannot load, refresh before editing. Writing over information you have not successfully loaded can lose useful instructions.
Example: support for an event page
Event: Saturday pottery workshop, October 10, 2026, 10 am–noon. Materials are included. Guests should wear clothes that can get messy. Answer in a welcoming tone using no more than three short paragraphs. If someone asks about a detail not listed here, say that it is not provided and direct them to the inquiry form. Never say an inquiry confirms a place.
Specific facts and an explicit unknown-answer rule give you something concrete to test.
Combine AI with relevant published records
A saved context field does not automatically query every database record. For a catalog assistant, ask the app to load published catalog data, select relevant details, and include them in the text request. Use consistent field names across the catalog and assistant.
Owner-only records and submissions are not a visitor-readable source. Do not put secrets into shared AI context or treat response instructions as database permissions.
Test known facts, unknowns, and changes
Ask about a supplied date, an omitted detail, and a changed policy after saving an update. Check the reply in the actual AI feature. Context can improve relevance, but you still need to review answers for accuracy.
Text and vision requests use saved context. Image generation and speech have their own inputs. See building a text assistant for the interaction itself.