What a Claude Project is, why every lesson in this course runs inside one, and the six files it holds about your store: store profile, catalogue, customers, customer voice, policies and brand voice. You set up the Project, add its instructions, and build or export each file, with every gap marked “not known”.
You finish with: a store Project holding store-profile.md, catalogue.csv, customers.csv, voice-raw.md, policies.md and brand-voice.md
No store data of your own yet? Download the Northmill Coffee example-store files below and follow every lesson on them.
Northmill is a UK shop, so the video and example-store files show these figures in £. Your own will be in your currency.
The store Project created on screen: instructions added, six files uploaded, the store profile and brand voice drafted, and all six files checked.
You finish with: a store Project holding store-profile.md, catalogue.csv, customers.csv, voice-raw.md, policies.md and brand-voice.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The ten parts every product page needs, from the result headline and buy box to the FAQ, search layer and phone layout, and the four jobs they do: landing page, sales assistant, trust and answer source. You check your current product page against all ten and record which parts are there, which are partial and which are missing.
You finish with: pdp-elements.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Awareness, problem, comparison, transactional, skeptic and objection: the six things a buyer is trying to find out, and which part of the page answers each one. You sort your own support questions, reviews and site searches into a map of what your buyers ask, and how often.
You finish with: pdp-intent-map.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Result clarity, time expectation, objection coverage, trust signals and action guidance, each scored 0 to 2 with a quote from the page. You score your page out of 10 and get a ranked list of fixes, each one marked publish, decide or rewrite.
You finish with: pdp-audit.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Parts check, buyer intent map and five-pillar score, built in one conversation from the current product page, support questions and reviews.
You finish with: pdp-elements.md, pdp-intent-map.md and pdp-audit.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The four kinds of benefit customers describe, functional, emotional, outcome and objection, and how to pull each one out of your reviews in the customer’s own words. You build a benefit stack for one product, with every benefit quoted from a review of that product.
You finish with: benefit-stack.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The six parts of a description: result headline, objection subheadline, promise, proof, path and fit. You write a description where every sentence comes from your spec, a review, your policy or a labelled store view, and that says who the product suits and who it does not.
You finish with: description.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Result, time, fit, risk, ease, delivery, returns and guarantee: the eight kinds of question buyers ask before they buy. You write an FAQ from your buyers’ real questions, answer first, with every delivery, returns and guarantee answer in your policy’s own words.
You finish with: faq.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The five kinds of social proof, how to choose featured reviews by topic, where the review that answers a doubt goes, and the UK and US rules on showing reviews. You choose and place the reviews for one product page, using only reviews of that product.
You finish with: social-proof.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The seven images a product page needs, hero, detail, scale, in use, in the box, objection and customer, and which of them must be photographs of the real product. You write a shot list and a ten-field brief that a photographer or image tool can follow.
You finish with: image-brief.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Title tag, meta description, plain summary, image alt text and product markup: what Google’s guidance says about each one, and how to write them so search engines and AI assistants read the same facts the buyer sees. You write the search layer for one page and test its markup.
You finish with: seo-layer.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Benefit stack, description, FAQ, reviews, photo brief and search layer, built in one conversation for one product from the reviews, catalogue and policies.
You finish with: benefit-stack.md, description.md, faq.md, social-proof.md, image-brief.md and seo-layer.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Top, explain, prove, answer and details: which part of the page goes in each zone, and how to order them by what your buyers ask most. You write a wireframe of your page, with every missing answer shown as a named gap and the question it waits on.
You finish with: layout.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Name and price, rating, options, the button, the delivery line, and the returns and warranty line, plus the UK pricing rules that apply to them. You write a buy box with the delivery charge for that product worked out from your policy and shown beside the price.
You finish with: buy-box.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
First screen, stacking order, content parity, tap targets, reading and speed, with the published standard behind each test. You write the phone order for your page and record the result of all six tests.
You finish with: ux-pass.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Source, claims, words, consistency, plain reading and the phone: six checks every sentence goes through before it is published. You edit only what fails, log every change, and finish with the final copy for your page.
You finish with: polished-copy.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
Layout, buy box, phone tests and polished copy, built in one conversation from the files made in Section 2.
You finish with: layout.md, buy-box.md, ux-pass.md and polished-copy.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
How one prompt reads the 13 files you built in Sections 1 to 3, checks them against your catalogue and policies, and assembles the finished page, and how to start the same process for your next product. You finish with your product page in desktop and phone order, its search code, a list of gaps and a publish checklist.
You finish with: pdp-final.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The engine run on all 13 files for one product: the files checked against each other, the page assembled and scored, then one gap closed and the page updated.
You finish with: pdp-final.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
How to make one change, such as a new price, new reviews or a new returns policy, reach every page and part it affects, without running the whole course again. You keep a dated change log of every change that goes live.
You finish with: an updated pdp-final.md and change-log.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
One change carried through the three modular prompts: every page and part it touches found, only the affected lines changed, the page updated and the change dated in the change log.
You finish with: an updated pdp-final.md and change-log.md
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
A library of 24 standalone prompts, each one rebuilding one part of a product page: the title, headline, description, bullets, FAQ, buy box, reviews, photo brief, alt text, title tag, meta description, AI summary and product markup, plus whole-page checks and a first page for a new product. You save one house rules file, and every prompt returns new text ready to paste with a check table in the same format.
You finish with: pdp-house-rules.md and new text for any part of the page, each with its check table
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.
The house rules file saved, then everyday prompts run one at a time on the example store’s product page: a new title tag and meta description, a new description, the reviews and rating line, and the buy box lines, each ending with a check table.
You finish with: pdp-house-rules.md and new text for any part of the page, each with its check table
Northmill is a UK shop, so the video shows these figures in £. Your own will be in your currency.