shopify-liquid
Skill0 starsChanged 7 months agoMITView on GitHub
Build and modify Shopify Online Store 2.0 themes using Liquid, section schemas, template JSON, and Shopify CLI. Use when the user works with .liquid files, Shopify themes, section schemas, Shopify CLI commands, or mentions Shopify theme development.
- Installs packages
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Shopify/Shopify-AI-Toolkittheir own version, first seen Oct 13, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- itsmylife44/shopify-theme-buildertheir own version, first seen Oct 11, 2026
- Shopify/agent-skillstheir own version, first seen Apr 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- openai/plugins★ 7.8ksame name
- Shopify/Shopify-AI-Toolkit★ 621same name
- Shopify/agent-skills★ 84same name
- itsmylife44/shopify-theme-builder★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Every section follows this pattern:
- Very specific: line 150
Whitespace: Use {%- tag -%} (hyphens) to strip surrounding whitespace.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shopify Liquid — Theme Development
Build and modify Shopify Online Store 2.0 themes with Liquid templating, section schemas, and safe deployment workflows.
Theme Structure
theme/
├── layout/theme.liquid # Base HTML wrapper (required)
├── templates/*.json # Page composition (section order + saved settings)
├── sections/*.liquid # Reusable modules with schema
├── snippets/*.liquid # Reusable fragments ({% render 'name' %})
├── assets/ # CSS, JS, images ({{ 'file' | asset_url }})
├── config/settings_schema.json # Global theme settings for Shopify Admin
��── locales/*.json # i18n translationsSection Anatomy
Every section follows this pattern:
<section class="my-section">
{% if section.settings.eyebrow != blank %}
<span class="eyebrow">{{ section.settings.eyebrow }}</span>
{% endif %}
<h2>{{ section.settings.heading }}</h2>
{% for block in section.blocks %}
<div class="block-item" {{ block.shopify_attributes }}>
<h3>{{ block.settings.title }}</h3>
<p>{{ block.settings.text }}</p>
</div>
{% endfor %}
</section>
{% schema %}
{
"name": "My Section",
"settings": [
{ "type": "text", "id": "eyebrow", "label": "Eyebrow" },
{ "type": "text", "id": "heading", "label": "Heading", "default": "Section Title" }
],
"blocks": [
{
"type": "item",
"name": "Item",
"settings": [
{ "type": "text", "id": "title", "label": "Title" },
{ "type": "textarea", "id": "text", "label": "Text" }
]
}
],
"presets": [
{ "name": "My Section" }
]
}
{% endschema %}Schema Setting Types
| Type | Usage | Notes |
text | Single line input | |
textarea | Multi-line input | |
richtext | HTML editor | Returns HTML string |
image_picker | Image from file library | Use with image_url filter |
product | Product selector | Returns product object |
collection | Collection selector | Returns collection object |
select | Dropdown | Requires options array |
range | Numeric slider | Requires min, max, step |
checkbox | Boolean toggle | |
color | Color picker | Returns hex string |
url | URL input | |
header | Section divider | Label only, no id |
Access: section.settings.field_id (section level), block.settings.field_id (block level)
Template JSON
Templates define which sections appear on a page and their order:
{
"sections": {
"hero": {
"type": "hero-banner",
"settings": {
"heading": "Welcome"
}
},
"features": {
"type": "features-grid",
"settings": {}
}
},
"order": ["hero", "features"]
}CRITICAL: Template JSON contains merchant-saved data (images, text overrides). Never push templates without pulling first — it erases merchant customizations.
Layout File Pattern
<!doctype html>
<html lang="{{ request.locale.iso_code }}">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>{{ page_title }}{% if current_tags %} — {{ current_tags | join: ', ' }}{% endif %}</title>
{{ 'theme.css' | asset_url | stylesheet_tag }}
{{ content_for_header }}
</head>
<body>
{% section 'header' %}
<main>{{ content_for_layout }}</main>
{% section 'footer' %}
<script src="{{ 'theme.js' | asset_url }}" defer></script>
</body>
</html>content_for_header— required (Shopify analytics, editor JS)content_for_layout— where template sections render
Common Liquid Filters
Assets:
{{ 'file.css' | asset_url }}— CDN URL for theme asset{{ image | image_url: width: 800 }}— resized image URL{{ 'key' | t }}— i18n translation from locales
Display:
{{ price | money }}— format as currency{{ string | strip }}— trim whitespace{{ value | default: 'fallback' }}— fallback if empty{{ string | escape }}— HTML escape{{ string | truncate: 100 }}— truncate with ellipsis
Whitespace: Use {%- tag -%} (hyphens) to strip surrounding whitespace.
Shopify CLI Workflow
# Install
brew install shopify-cli
# Local dev (live preview, no live store affected)
shopify theme dev --store mystore.myshopify.com
# Pull remote changes (merchant edits) BEFORE pushing
shopify theme pull --store mystore.myshopify.com
# Safe push (sections + assets only, never delete remote files)
shopify theme push --store mystore.myshopify.com \
--allow-live \
--nodelete \
--only "sections/*:assets/*:layout/*:snippets/*:locales/*:config/settings_schema.json"
# Push specific template (only when intentional)
shopify theme push --only "templates/page.about.json"
# Create new unpublished theme
shopify theme push --store mystore.myshopify.com --theme-name "New Theme"Flags:
--allow-live— update the live (published) theme--nodelete— don't remove files missing locally--only— colon-separated glob patterns (not comma)
Common Gotchas
- image_picker crashes —
image_urlfilter on nil crashes silently. Always guard:{% if section.settings.image != blank %} - Schema defaults ignored — If template JSON has ANY saved settings for a section, ALL schema defaults are ignored. Design accordingly.
- CDN caching — Shopify uses Cloudflare. Pushes don't purge cache. Merchant must save in theme editor to force refresh.
- Block shopify_attributes — Always add
{{ block.shopify_attributes }}to block wrapper divs. Without it, blocks can't be reordered/edited in the theme editor. - Locale key fallback — Missing translation keys render as the key string itself (e.g.,
pages.home.hero.titleappears literally). - Form handling — Use
{%- form 'contact' -%}for native Shopify forms. Submissions appear in Admin > Customers. Usename="contact[body]"for custom fields. - Reveal animations in editor — Sections with
opacity: 0on load (reveal-on-scroll) won't show in the theme editor. Add:{% if request.design_mode %}style="opacity:1"{% endif %}
i18n Pattern
Locale file (locales/en.default.json):
{
"sections": {
"hero": {
"eyebrow": "WELCOME",
"heading": "Your Brand Here"
}
}
}Usage: {{ 'sections.hero.eyebrow' | t }}
Locale-aware links:
{%- assign base = request.locale.root_url -%}
{%- if base == '/' -%}{%- assign base = '' -%}{%- endif -%}
<a href="{{ base }}/products/my-product">Shop</a>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

