Start with a real store task. These 20 original prompts help you define the work, supply the right inputs, and review what an AI tool produces.
Published November 1, 2026 · AdsX Team · Free to use, no email required
These are illustrative briefs, not tested builds or guaranteed capabilities. This page does not connect to your store or run prompts. Use only information you are authorized to share; never paste credentials or unnecessary customer data.
Choose the right tool before copying
Sidekick-generated apps run inside Shopify admin. Theme prompts need a coding tool and an unpublished theme copy; a general assistant can help plan but does not automatically have store access. Review current Sidekick eligibility and limits and the Shopify AI Toolkit documentation. The tool label is a suggested environment, not a promise that every requested feature is supported.
Bring: App names, bills, used features and connected systems
Map each supplied Shopify app to the functions we actually use. Separate storefront display, admin work, automation and external integrations. Identify overlapping features and missing dependency information. Recommend what to investigate before keeping, replacing or removing each app. Do not recommend uninstalling anything yet.
Expected output: A feature and dependency table
Review: Compare the table with app settings and ask the people using each workflow.
Illustrative prompt — not execution-tested
Planning · General assistant
Compare build versus buy
Bring: Subscription cost, build estimate, maintenance hours and hourly cost
Compare keeping this app with building the limited replacement described here. Calculate twelve-month cash costs and show labor separately. Include hosting, maintenance, support and update assumptions. Identify which unknown could reverse the decision. Do not invent a savings figure.
Expected output: An assumption-based cost comparison
Review: Recalculate the arithmetic and distinguish hypothetical inputs from actual quotes.
Illustrative prompt — not execution-tested
Planning · General assistant
Write a narrow app brief
Bring: One merchant problem and three representative examples
Turn this merchant problem into a one-page app specification. Define its user, data inputs, visible output, read or write actions, exclusions, failure states and acceptance cases. Recommend the appropriate Shopify surface. Ask about missing requirements before proposing implementation.
Expected output: A reviewable specification
Review: Make sure the specification excludes unrelated features and names the platform surface.
Illustrative prompt — not execution-tested
Admin apps · Sidekick Generate app
Build a catalog QA admin app
Bring: Product statuses to include and the definition of missing data
Generate a read-only Shopify admin app listing products without a meaningful description or product image. Show title, status and missing fields, with a way to review the product. Handle pagination, loading, failures and an empty result. Do not modify products or send data externally. Explain unsupported requirements and permissions before installation.
Expected output: An app draft and permission explanation
Review: Compare known complete and incomplete records, including one beyond the first results page.
Illustrative prompt — not execution-tested
Admin apps · Sidekick Generate app
Draft a team task tracker
Bring: Task fields, team workflow and storage requirements
Plan a simple Shopify admin task tracker for our internal team. We need task title, owner, due date and status. First explain whether the required storage and team behavior are supported in this environment. Flag unsupported features. Do not use customer records as task storage or request unrelated permissions. Build only after the plan is reviewed.
Expected output: A feasibility plan, then a scoped app draft
Review: Verify persistence, staff access and required fields; do not assume a visible list is durable storage.
Illustrative prompt — not execution-tested
Admin apps · Sidekick Generate app
Plan a reorder review dashboard
Bring: Date range, inventory locations and supplier lead times
Plan a read-only reorder review dashboard using supported store data. Explain the sales period, stock measure and proposed calculation. Identify missing supplier lead times and stock adjustments. Show assumptions beside results. Do not create purchase orders or change inventory. Flag unsupported data before building.
Expected output: A dashboard plan with data gaps
Review: Check calculations on known products and handle returns, stockouts and location differences.
Illustrative prompt — not execution-tested
Development · Coding agent
Find missing app requirements
Bring: App specification and relevant repository files
Review this specification against the current Shopify documentation and this repository. List missing API fields, permissions, persistence requirements and failure behavior. Separate supported implementation paths from assumptions. Do not modify files or run store mutations during this review.
Expected output: A gap list with source references
Review: Open the cited documentation and resolve blocking questions before implementation.
Illustrative prompt — not execution-tested
Development · Coding agent
Write acceptance cases
Bring: Feature brief and sample records
Create acceptance cases for this feature: normal use, empty data, invalid inputs, permission failure and partial network failure. State expected output and evidence for each case. Use supplied fixtures rather than private customer data. Do not claim tests have run.
Expected output: A test matrix
Review: Ensure cases test the desired behavior rather than merely repeat implementation details.
Illustrative prompt — not execution-tested
Development · Coding agent
Review requested permissions
Bring: Manifest, routes and feature list
Compare the requested Shopify permissions with the code paths and feature requirements provided. Explain each scope and identify unused or excessive access. Distinguish read from write access. Do not remove a scope automatically; list the impact and a verification step.
Expected output: A permission review
Review: Confirm every required action remains possible and no secret is included in the report.
Illustrative prompt — not execution-tested
Development · Coding agent
Prepare a rollback plan
Bring: Deployment method, changed files and data changes
Write a rollback plan for this change. Separate code rollback from data recovery. Identify backups, compatibility concerns, the person who can stop rollout and the evidence needed to resume. Do not assume reverting code reverses stored data changes.
Expected output: A release and recovery checklist
Review: Verify that recovery steps exist in the actual environment before deployment.
Illustrative prompt — not execution-tested
Theme · Coding agent with theme access
Draft a size-chart section
Bring: Unpublished theme, size table, product mapping and units
In the unpublished theme copy, propose a size-chart section using the supplied measurements and units. Inspect existing theme patterns first. Include accessible headings and mobile behavior. Keep chart assignment explicit per product. Do not publish the theme or invent measurements. Explain how the merchant edits the data.
Expected output: A theme change proposal or draft
Review: Review different products, long labels, keyboard access and narrow screens before publishing.
Illustrative prompt — not execution-tested
Theme · Coding agent with theme access
Draft an announcement bar
Bring: Unpublished theme, approved text and destination
Inspect this theme for an existing announcement setting before adding code. If a new section is needed, build a simple text-and-link announcement bar in the unpublished copy using existing conventions. Include editor settings and readable mobile styling. Do not add tracking, timers or fabricated urgency. Do not publish.
Expected output: A native-setting recommendation or small section draft
Review: Check the destination, contrast, keyboard access and behavior when the text is empty.
Illustrative prompt — not execution-tested
Content · Sidekick or general assistant
Write product copy from facts
Bring: Approved specifications and brand voice
Draft a concise product description using only these supplied facts. Separate included items from optional accessories. Preserve dimensions, materials and compatibility exactly. List unanswered buying questions separately. Do not add certifications, performance claims or delivery promises. Return a draft without publishing.
Expected output: A factual product-description draft
Review: Compare every claim, quantity and unit with the supplied specifications.
Illustrative prompt — not execution-tested
Content · Sidekick or general assistant
Draft product FAQs
Bring: Real questions, approved product facts and policies
Turn these real customer questions into a short product FAQ. Answer only from the supplied facts and current policies. Mark unanswerable questions for review. Avoid repeating the description and do not invent guarantees. Return draft text only.
Expected output: A question-and-answer draft
Review: Check policy dates and ensure each answer resolves the actual question.
Illustrative prompt — not execution-tested
Content · General assistant
Build a product comparison
Bring: Product fact sheets and comparison criteria
Compare these products using the supplied facts and criteria. Use the same units, mark unavailable information and keep opinion separate from fact. Do not pick a winner without a stated customer need. Return a table and the questions a buyer should resolve.
Expected output: A comparison table
Review: Verify source facts and avoid treating missing information as a negative product feature.
Illustrative prompt — not execution-tested
Content · Vision-capable assistant
Describe product images
Bring: Product images and their page context
Draft concise alt text for each supplied image based on what is visible and its purpose on the page. Distinguish product color or angle where useful. Do not infer material, certification or included accessories from appearance alone. Flag decorative images for human review.
Review: Inspect each image and avoid unnecessary repetition or keyword stuffing.
Illustrative prompt — not execution-tested
Planning · Sidekick or general assistant
Plan collection merchandising
Bring: Collection goal, product data and constraints
Propose a collection merchandising brief for this goal using the supplied products. Explain grouping, ordering and exclusions. Identify stock or seasonality assumptions and distinguish recommendations from verified facts. Do not move or publish products.
Expected output: A merchandising proposal
Review: Review available stock, customer intent and business constraints before applying changes.
Illustrative prompt — not execution-tested
Theme · Browser-capable coding agent
Review mobile shopping
Bring: Preview URL and target device widths
Review this preview as a mobile shopper. Inspect product options, price visibility, purchase controls, images and navigation at the supplied widths. Report observable issues with evidence and reproduction steps. Do not place orders or change the site. Distinguish screenshots from interactions actually tested.
Expected output: An evidence-based issue list
Review: Reproduce findings and prioritize blockers over cosmetic preferences.
Illustrative prompt — not execution-tested
Planning · General assistant
Check a discount brief
Bring: Eligibility, combinations, dates, currency and examples
Review this proposed discount specification for ambiguity. Work through the supplied carts, eligible products, combination rules and date boundaries. List expected outcomes and missing facts. Do not create a discount or assume the platform supports an unstated rule.
Expected output: A discount acceptance matrix
Review: Validate supported rules in Shopify and confirm totals before activation.
Illustrative prompt — not execution-tested
Planning · Sidekick or general assistant
Explain a store report
Bring: Authorized report, date range and metric definitions
Analyze this report using its stated date range and metric definitions. Separate traffic, orders, revenue, refunds and contribution where available. Identify missing denominators and reporting delays. Show calculations, distinguish correlation from causation, and suggest one useful next investigation.
Expected output: A bounded report analysis
Review: Check totals, time zones, comparison periods and whether revenue is gross or net.
Illustrative prompt — not execution-tested
Keep a record of what worked
Save your tool, prompt, inputs, revisions and observed results. A useful prompt library gets better through documented outcomes. Copying a prompt here does not prove an app runs correctly or that an app subscription can be canceled.