The Experios AI Assistant (Kelda) helps you design and style responsive publications quickly and efficiently through natural conversation. This guide explains how to communicate clearly with Kelda to achieve accurate results, reduce revisions, and streamline your workflow for ease and efficiency.
Understanding Processing Time
Kelda may take a few moments to process your request. This is normal — the AI analyses your layout, intent, and the Experios design framework before applying your changes. Even for complex tasks, Kelda remains much faster than manual design. As a rule: the clearer your request, the better and faster the outcome.
Best Practices for Communicating with Kelda
Specify the Task Precisely
State exactly what you want Kelda to change. Include:
– Element type (e.g., heading, paragraph, image, button)
– Page location (e.g., “above the fold,” “footer,” or the name of a specific row)
– Constraints (e.g., “do not change padding,” “use fixed width 800px”)
Example:
“Replace the H2 in the row named ‘features’ with ‘Why customers choose us.’ Keep existing styles and spacing.”
Use Clear Action Words
| Action | Example |
|---|---|
| Add / Create / Place | “Add a text box.” / “Place an image.” |
| Change / Modify / Set | “Change the font to Roboto.” / “Set the background color to blue.” |
| Move / Align / Distribute | “Move the button 50px down.” / “Align all images to the center.” |
| Generate / Suggest | “Generate a short article about sustainable fashion.” / “Suggest a calm, professional color palette.” |
Provide Assets and References Up Front
Upload any required media to the asset library before referencing them. Name assets clearly (e.g., hero-bg.jpg, product-demo.mp4) and specify which one to use.
Good: “Uploaded ‘team-photo.jpg’ to assets. Use that in the team section with layout=cover and alt text ‘Our team in the office.’”
Bad: “Use this image: https://site.com/pic.jpg”
Use Step-by-Step Instructions
Build layouts progressively using structured steps. This reduces ambiguity and ensures accurate results
Example workflow:
1. Set up a 3-column grid.
2. Place a title placeholder across the top.
3. Add an image placeholder in the left column.
4. Fill the other two columns with placeholder text.
Specify What Not to Modify
If your request targets a specific area, make that clear.
Example: “Update only the hero heading text; do not modify padding, margins, or other rows.”
Generating Copy
When asking Kelda to write text, specify tone, length, and key ideas. Example: “Generate a concise, friendly paragraph introducing the brand’s new sustainable collection.”
Using Experios Terms
Use standard Experios language for best results:
– Elements: Components on the page (e.g., text, image, button).
– Populate: Fill an element with an uploaded file.
– Asset library / asset lib: Your media storage.
Use percentages or numeric values for measurements (e.g., “Increase padding by 20px”). Use responsive terms like max-width, min-height, and min-width to preserve adaptability.
Working with Attachments
If you upload a page or screenshot:
1. Ask Kelda to analyze it first: “Summarize the layout and content of this page.”
2. Then build from that summary: “Recreate this layout and content, keeping spacing accurate.”
Note: Blocks already included in Experios don’t require summaries — they are pre-optimized.
Limitations and Alternatives
Kelda will inform you when a request cannot be completed (e.g., absolute positioning, unauthorized uploads, project-level JSON edits). In such cases, it will suggest a supported alternative and explain why the original request isn’t possible.
Common Mistakes and How to Avoid Them
Avoid common pitfalls by providing specific, structured requests. The following examples illustrate good versus bad phrasing:
| Mistake | Poor Example | Better Example | Why? |
|---|---|---|---|
| Vague instructions | “Improve this page.” | “Convert the top row into a hero with ‘hero-bg.jpg’, H1 ‘Welcome’, subheading, and centered CTA with the text ‘View Projects’” | Specific details eliminate guesswork. |
| Using external images not in assets | “Use this image: https://site.com/pic.jpg” | “Uploaded ‘team-photo.jpg’ to assets. Use that.” | Experios requires uploaded assets. |
| Unsupported techniques | “Use absolute positioning.” | “Place text in a column over a background image.” | Maintains responsiveness. |
| Unavailable fonts/icons | “Use Google font [google font name].” | “Use a project-installed font or ask Kelda to suggest the closest match.” | Kelda can only access fonts in the project list. |
Example Prompts
| Goal | Prompt |
|---|---|
| Add an image | “Add a new image element and populate it with the first item in my asset lib.” |
| Adjust spacing | “Increase the padding on the content blocks by 20px.” |
| Write short text | “Generate a 40-word product intro for a [insert product here] in a friendly, professional tone.” |
| Improve layout | “Review this page and suggest small visual improvements that keep it responsive.” |
Quick-Reference Checklist
– [ ] Identify the element and location
– [ ] Provide asset names if needed
– [ ] Give clear copy or tone guidance
– [ ] Specify what not to change
– [ ] Use numbered steps for complex tasks
Some Final Tips
- Talk to Kelda like you would to a human designer.
- Explain why you’re making a change to help Kelda tailor results.
- Build in steps (layout → content → style).
- Ask for alternatives if a request isn’t supported.
- Remember: Kelda is a creative collaborator, not just a command executor. With clear intent and structured requests, you can design responsive, professional Experios layouts quickly and efficiently.