Set up Kera with an AI assistant
Point Claude, ChatGPT or another assistant at the Kera docs so it answers from the real settings, and work with it safely.
Every docs page is also published as plain Markdown. Give an assistant the addresses below and it answers with the exact setting names the theme editor uses, instead of guessing from other themes.
Set it up#
- Open an assistant that can read web pages.
- Paste the
llms.txtaddress and ask it to answer from those docs with exact setting names and click paths. Add your question. - Follow the steps in the theme editor. Each guide's Where line is the click path from the Shopify admin.
The addresses to give an assistant#
| Address | What it holds |
|---|---|
https://spellnsell.com/themes/kera/llms.txt |
An index of every page with a one-line summary. Start here. |
https://spellnsell.com/themes/kera/llms-full.txt |
Every guide in one file, for assistants that can read a long document at once. |
Any docs address plus .md |
That page as Markdown, for example https://spellnsell.com/themes/kera/docs/cart/free-shipping-and-gift.md. |
https://spellnsell.com/themes/kera/docs/reference/sections/<file-name>.md |
One section's settings and blocks, for example .../reference/sections/gift-finder.md. |
Good to know#
Is there a quicker way to share one page?
Each docs page has Copy page and Open in buttons at the top that hand the page to an assistant in one click.
What should I paste?
For a setup question, something like this, with your own question at the end:
Read https://spellnsell.com/themes/kera/llms.txt and the pages it links to
that are relevant. I use the Kera Shopify theme. Answer with the exact
setting names and click paths from those docs.
My question: how do I add a free gift when an order passes $150?
To plan a whole page, ask for a list of sections, then build it in the editor. The full list is Sections A to Z.
Using https://spellnsell.com/themes/kera/llms.txt, plan a home page for a
store that sells gold hoops and engraved necklaces. List the Kera sections
in order, what content each needs (images, collections, products), and the
settings to change.
The answer names a setting I can't find.
Ask the assistant which docs page it came from and open that page. Setting names in the docs are checked against the theme on every release. If an answer and these docs disagree, the docs are right for Kera. If the docs are wrong, tell us.
What about Shopify Sidekick?
In the admin, Sidekick works with your store's data, such as products, collections and discounts. In the theme editor, it can change theme settings and add Kera's sections and blocks, for example "add a FAQ section under the product information". Nothing applies until you click Save. Sidekick can't create metafield definitions, menus or shipping rates yet; ask it to walk you through those. Guides for tasks it can do have a Do it with Sidekick box with prompts to copy.
Sidekick can also generate new blocks in the theme editor, for example "a block with a care icon and two lines of text". They can go in Rich text, Image with text, Product information, Featured product and Blog post. This needs the Edit code permission and a purchased theme, not a trial. Generated blocks are your own code, so they don't change when you update the theme.
For developers
| Address | What it holds |
|---|---|
https://spellnsell.com/themes/kera/reference/sections.json |
Every section and block with setting IDs, labels, types and defaults. |
https://spellnsell.com/themes/kera/reference/settings.json |
Every theme setting, grouped as the editor shows them. |
https://spellnsell.com/themes/kera/reference/metafields.json |
The metafields the theme reads, with owner, key and type. |
A coding agent should read sections.json before changing a template: section and block types, setting IDs and allowed values are all there. Blocks are private to their section (their files start with _), so a block type only works in the section that defines it. A template that references a missing metafield definition in a dynamic source breaks, so create the definition first. Work on an unpublished copy, never the live theme. Pull the latest editor changes before editing JSON files, then push and preview. Code changes don't carry over when you update the theme. See also the Developer reference.