Approach and advantage
The change stays tied to named files and a visible requirement. Keeping a backup and a proposed edit list helps reviewers compare the requested behavior with the implementation before the team considers publication.
Plan Shopify theme customization with a coding assistant: describe the storefront change, supply the theme files and get a proposed edit with responsive and accessibility checks. This Skill helps translate requests such as a new product section or clearer mobile layout into work a developer can review in a theme preview.
Shopify Theme Customizer asks the agent to understand the existing theme, keep a backup and outline the files affected before editing. The work can include section settings, layout changes and checks for how the result behaves on different screen sizes.
It is most useful when an operator can describe the desired shopping experience but needs help turning it into a clear technical brief. Access to a development theme and the tools used to edit it must already be available.
The change stays tied to named files and a visible requirement. Keeping a backup and a proposed edit list helps reviewers compare the requested behavior with the implementation before the team considers publication.
Use it for a configurable storefront section, mobile spacing improvements or a theme review. Screenshots, the theme version and precise acceptance criteria make the handoff more useful than a broad request to redesign the store.
A local theme copy, the requested change, theme version, screenshots or requirements, and a development preview.
A model chat is enough to draft from these instructions. Real system access or file changes need separately configured tools.
The text assumes Admin API access but contains no connector or credentials setup. Use a development theme; publication is a separate action.
Use these instructions in a chat, or ask Codex / Claude Code to save them as a personal Skill for repeated tasks.
Set up a personal reusable instruction template for Shopify Theme Customizer in the app I am using.
1. Read the “Collected instruction template” section at https://ecomagenttools.com/skills/shopify-theme-customizer. Use only that complete instruction text, not the page’s reviews, FAQ or installation explanation. If you cannot retrieve the complete text, ask me to paste it; do not guess it or download a same-named third-party package.
2. Show which assumptions, placeholders and access requirements I need to supply. Preserve the collected task instructions. This is a locally adapted template, not an original-author package.
3. If you are Codex or Claude Code with local file access, create a personal Skill named shopify-theme-customizer-local under ~/.agents/skills/shopify-theme-customizer-local/SKILL.md for Codex or ~/.claude/skills/shopify-theme-customizer-local/SKILL.md for Claude Code. Add valid name and description frontmatter if absent; keep the collected instructions in the body and identify the local adaptation. Do not overwrite an existing Skill. If you are in a chat-only app, use these instructions in the current conversation instead and do not claim a local installation.
4. Return the saved path or current-chat setup result and a starter request for this task. List any required tools or data that remain unconfigured. Do not claim account/API access or a completed business workflow just because the template was saved.Network-collected; no confirmed author source. The collected text was reviewed, but it has not been linked to a verified original publication. This does not establish that no official package exists; the examples here use only the collected text.
You are a Shopify theme development agent with direct access to the store's theme files via the Shopify Admin API.
CAPABILITIES:
1. Navigate theme structure: sections/, templates/, snippets/, assets/, config/
2. Read and modify Liquid templates, JSON schemas, CSS, and JavaScript
3. Generate new sections with proper schema definitions
4. Optimize theme performance (lazy loading, image optimization, CSS minification)
5. Add custom metafields and dynamic content blocks
6. Ensure responsive design across mobile/tablet/desktop
WORKFLOW:
1. Understand the request → ask clarifying questions if needed
2. Backup current theme before modifications
3. Identify files to modify → propose changes → get approval
4. Implement with clean, commented Liquid code
5. Suggest testing steps
RULES:
- Always use theme app extensions instead of direct code injection when possible
- Follow Shopify's Liquid best practices and performance guidelines
- Use schema settings for configurable options (don't hardcode)
- Comment complex logic for future developers
- Test for accessibility (keyboard nav, screen readers, color contrast)Starter prompts for the main use cases—copy and use them directly.
Identify affected Liquid, JSON, CSS, or JavaScript files and propose a small reviewable change. Use for: Plan a theme edit. Prepare: A local theme copy, the requested change, theme version, screenshots or requirements, and a development preview.
Use the collected instructions above. Task: Identify affected Liquid, JSON, CSS, or JavaScript files and propose a small reviewable change.. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The text assumes Admin API access but contains no connector or credentials setup. Use a development theme; publication is a separate action.[INPUT][CONSTRAINTS]Generate a section with schema settings using the supplied theme conventions. Use for: Draft a configurable section. Prepare: A local theme copy, the requested change, theme version, screenshots or requirements, and a development preview.
Use the collected instructions above. Task: Generate a section with schema settings using the supplied theme conventions.. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The text assumes Admin API access but contains no connector or credentials setup. Use a development theme; publication is a separate action.[INPUT][CONSTRAINTS]Create checks for mobile layout, keyboard navigation, image sizing, and performance before publishing. Use for: Review mobile and accessibility. Prepare: A local theme copy, the requested change, theme version, screenshots or requirements, and a development preview.
Use the collected instructions above. Task: Create checks for mobile layout, keyboard navigation, image sizing, and performance before publishing.. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The text assumes Admin API access but contains no connector or credentials setup. Use a development theme; publication is a separate action.[INPUT][CONSTRAINTS]The text assumes Admin API access but contains no connector or credentials setup. Use a development theme; publication is a separate action.
Network-collected; no confirmed author source. The collected text was reviewed, but it has not been linked to a verified original publication. This does not establish that no official package exists; the examples here use only the collected text.
Use authorized inputs and keep secrets out of prompts. Review customer-facing claims, calculations, code changes, and any proposed external action before applying them.
Guide a coding agent through Shopify theme changes and a review checklist. The instructions ask for a backup, proposed files, approval, and responsive and accessibility checks.
Copy the collected instructions below into a model chat or project instructions. Replace assumed access, default policies, sample numbers, and placeholders with your actual context. Attach a small redacted sample, use a starter prompt, and review the draft before acting.
Plan a theme edit; Draft a configurable section; Review mobile and accessibility
The text assumes Admin API access but contains no connector or credentials setup. Use a development theme; publication is a separate action.
Network-collected; no confirmed author source. The collected text was reviewed, but it has not been linked to a verified original publication. This does not establish that no official package exists; the examples here use only the collected text.
The complete available Skill content is cataloged and reviewed; public web material does not currently name the original author. Attribution does not affect its directory visibility or content-based recommendation eligibility.
Network-collected; no author source is listed. This label describes attribution only, not capability, visibility, or recommendation eligibility.
No reviews yet.