Hire an AI sale-day store speed review and checklist

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A keep, change or remove verdict on every heavy feature, with a lighter replacement and a score out of 100 for how light the pages are
• A keep, remove, delay or one page only verdict for each app, with the app stack scored before and after
• A speed budget for page weight, mobile score and outside scripts
• A pre-sale checklist with an app freeze, a testing routine and a plan for overload

How it does the job well

• Work from the real catalogue, prices, stock and policies. Check variants and currencies.
• Judge changes by contribution margin, not revenue alone.
• Change one thing at a time on a live store and keep a way to roll back.
• Keep product claims consistent with supplier data and labels.

Mistakes it avoids

• Editing live products, prices or themes without approval or a backup.
• Ignoring shipping, returns and fees when judging profit.
• Copying competitor listings.

What a good result looks like

An example, not your task: A sale, launch or ad push is coming and you need the store fast when traffic peaks.

• Heavy feature trimmer. A keep, change or remove verdict on each heavy feature, a lighter replacement, theme advice and a lightness score out of 100.
• App script auditor. A keep, remove, delay or one page only verdict for each app, with blocking time and the app stack scored before and after.
• Speed budget and sale check. Limits for page weight, mobile score and outside scripts, plus a testing routine, app freeze, pre-sale checklist and overload plan.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Trim heavy features. Judges each slider, quick view, autoplay video, popup and animation keep, change or remove, suggests a lighter replacement, and scores how light the pages are.
• Audit your apps. Marks each app keep, remove, delay or one page only, ranks apps by blocking time, and leaves your tracking tags alone.
• Set the budget and checklist. Uses your new PageSpeed results to set limits on page weight, mobile score and outside scripts, and writes the pre-sale checklist with an app freeze and an overload plan.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id get-your-store-ready-for-a-big-sale-day only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/get-your-store-ready-for-a-big-sale-day/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The homepage, a collection page and a product page, as links or screenshots
• Your theme name and the popup and video apps you use
• The sale date, expected traffic, platform and plan
• Heatmap or click data (optional)
• PageSpeed results and page weights, after you make the cuts

Tools and access

• Google PageSpeed Insights: Shows how heavy a page is and which files cost the most.
• A heatmap tool such as Microsoft Clarity: Free click maps show whether shoppers use quick view, sliders and popups.
• Shopify theme library: Lets you try a free default theme on a copy before you decide.
• Google PageSpeed Insights: Its third-party and blocking time sections show which scripts cost the most.
• Shopify admin Apps and theme editor: The Apps list and the theme editor's App embeds show what is installed and what is switched on.
• Any good chat AI: Reads your screenshots and matches scripts to apps. No code or paid tool needed.
• Google PageSpeed Insights: Gives the scores and page weights to set limits from.
• Shopify online store speed report: Tracks your store's speed score over time.
• Google Search Console: Shows real-user results after the sale.

Functions and deliverables

• Sale-day store speed review and checklist: Review heavy features and app scripts, plan approved cuts and set speed limits and a checklist for the sale.
  • A keep, change or remove verdict on every heavy feature, with a lighter replacement and a score out of 100 for how light the pages are
  • A keep, remove, delay or one page only verdict for each app, with the app stack scored before and after
  • A speed budget for page weight, mobile score and outside scripts
  • A pre-sale checklist with an app freeze, a testing routine and a plan for overload
• Slow website feature review: Find which sliders, popups and videos slow your store. Give it your pages. You get a keep, change or remove call on each, and a lightness score.
  • A list of heavy features with what each costs, and keep, change or remove
  • A replacement for each (static hero, lite video embed, thumbnail)
  • Theme advice
  • A score out of 100 for how light your pages are now, with the sum shown, and a projected score after the changes
• Store app script reviewer: Give it your apps and speed report. Get each app marked keep, remove or delay, and a score.
  • A table with each app, what it loads, which pages need it, the verdict and the reason
  • A score out of 100 for your apps, now and after the changes, with the sum shown
  • A list of apps to uninstall, with a follow-up for the leftover app code finder
  • A list of apps to delay, for the theme script and style loader
  • A rule for the next app you install
• Store website speed reviewer: Plan your store's speed budget before a sale. Give it your speed results and sale date. You get limits, a test routine and a pre-sale checklist.
  • A speed budget: maximum page weight, minimum scores, maximum outside scripts
  • A monthly and after-change testing routine
  • A pre-sale checklist, with an app freeze date
  • A plan for what to do if traffic overloads the site
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one

Tasks you can use it for

• A sale, launch or ad push is coming and you need the store fast when traffic peaks.
• Your homepage has a slider, a popup and autoplay video, and you do not know which earn their place.
• You cleaned up speed once and it crept back after new apps and banners.

Limits to check before starting

• Your store has no sale or launch coming in the next few months: run a simple PageSpeed check on your key pages instead.
• Your mobile report fails across the board: use a longer speed fix workflow, not this sale-day one.
• You need the live store tested for you: this workflow cannot open your store, so a developer or PageSpeed must run the checks.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Attach screenshots of your homepage, a collection page and a product page. Add your app list and the sale date.
• At the pause, make the cuts, then run the key pages through PageSpeed and note the results.
• Give it those results to get your speed budget and checklist.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/get-your-store-ready-for-a-big-sale-day for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.