For Pixfizz customers · Claude

Give your AI assistant the Pixfizz manual

Connect the Pixfizz knowledge base and skills to a Claude project, so it answers from how the platform actually works instead of guessing. About fifteen minutes, then optional extras for images, video and marketing.

About 15 minutesKnowledge base14 skills · v0.5.1Built for Claude

Before you start

Labels inside Claude change from time to time. If a button is named slightly differently from what you see here, look for the closest match, or use the search box.

Create a Claude project

A project keeps a set of files and instructions loaded across every conversation, so you do not re-explain your store each time you ask something.

  1. Go to claude.ai and sign in, or create an account
  2. In the left sidebar, click Projects
  3. Click New project
  4. Name it after your store — for example Acme Photo – Pixfizz

Switch on two settings

  1. Code execution and file creation. On a Pro or Max plan: Settings › Capabilities. On a Team or Enterprise plan the owner turns it on for everyone under Organization settings › Plugins & skills, together with Skills. Without it the Pixfizz skills in step 6 do not load, and Claude cannot open a backup, a CSV or a template export you give it.
  2. Web search. Keep it on in the conversation’s tools menu. Step 5 needs it to visit your storefront.

Use the desktop app for day-to-day work

The browser at claude.ai is fine for questions. The Claude desktop app is where the rest of this page pays off: it installs the Pixfizz plugin, works with Claude in Chrome, and can work on files in a folder on your computer. The project you create here shows up there too.

Which plan? Projects and Claude in Chrome need a paid Claude plan. A free account can still do this by pasting the knowledge files into each conversation, but you will be repeating that every time — the project approach is what makes this worth doing. The same pattern works in ChatGPT or Gemini if you already pay for one of those; the file names and the prompt below transfer, the menu labels and the plugin do not.

Add the Pixfizz knowledge base

The Pixfizz platform reference is maintained as a public GitHub repository — the architecture, product hierarchy, pricing engine, fulfillment, order lifecycle, Liquid reference and Shopper template rules. Connect it once and your project reads from it.

Connect it to your project

https://github.com/pixfizz/pixfizz-knowledge
  1. Open your project (not the general settings) and find the project’s files panel, labelled Project knowledge or Context
  2. Click + or Add in that panel
  3. Choose GitHub. The first time, Claude asks you to sign in to GitHub and allow access. A free GitHub account is fine
  4. Paste the repository address you copied above. If pressing Enter does nothing, click the small link icon next to the box, paste the address there, then press Enter
  5. Tick the checkbox at the top of the file list so every file is selected, then click Add files
Do not look for GitHub under Settings › Connectors. Searching there finds nothing useful for this step. GitHub is added from inside the project, as above.

No GitHub account? Download the files from the repository as a ZIP, unpack it, and upload the markdown files to Project knowledge by hand instead.

Updates are not automatic. Claude reads whatever it pulled when you connected the repository. When Pixfizz updates the knowledge base, open Project knowledge, find the GitHub connection and click Sync now to fetch the latest version. Worth doing monthly, or whenever we tell you something has changed.

Tell it about your setup

Pixfizz is deployed in more than one shape, and the right answer often depends on which one you are on. Pick yours — steps 4 and 5 rewrite themselves to match.

Your store

Saved in this browser only, so you can come back to this page without retyping.

Not sure which one you are on? If your storefront runs on the Pixfizz CMS using the Shopper template, pick Full Pixfizz — Shopper. If it runs on the Pixfizz CMS with a storefront built specifically for you, pick Full Pixfizz — custom. If your storefront is Shopify and a Personalize button opens a Pixfizz editor, pick Shopify + Pixfizz. If your own application calls Pixfizz directly, pick API integration. Still unsure — ask your Pixfizz contact rather than guessing, because the answers differ.

Set the project instructions

This tells the assistant who it is working for, which deployment you are on, and how to behave. Copy it, open your project, click Instructions (or Set project instructions), delete anything already in the box, paste, and save.

Fill in your store name and storefront address in step 3 first. They are written into the text below.

The rule about naming its source is the one that matters most. If the assistant tells you which knowledge file an answer came from, you can check it. If it cannot name one, treat the answer as a guess.

Teach it about your store

The knowledge base covers the platform. This step covers you — your products, your collections, your tone. Start a new conversation inside the project and paste this prompt.

What happens next

  1. It browses your storefront and summarises what it finds
  2. It writes a SITE_CONTEXT.md for you to review
  3. Read it and correct it — it will get some things wrong
  4. Upload the corrected file to your Project knowledge
  5. Update it whenever your catalogue or setup changes in a way that matters, such as a new product line or a new fulfillment partner
On its own it only sees your public storefront. It cannot see fulfillment destinations, pricing formulas, custom fields, product XML templates or anything behind a login. Add those to SITE_CONTEXT.md yourself, or give it more to work from with one of the two options below.

Get a much better SITE_CONTEXT.md

Attach the backup to the conversation, not to Project knowledge. It is for building the context file once, and it would use up space the knowledge base needs.

Add the Pixfizz skills v0.5.1

The knowledge base is a reference. The plugin is a set of skills — working procedure for a specific job, each one loading itself when your question matches it. Ask about a price that is doubling and the pricing skill loads on its own, with the rules that make prices go wrong on this platform.

It is free, it is public, and it works alongside everything above. Skills need Code execution and file creation switched on (step 1).

In the Claude desktop app
  1. Open Customize, then Plugins
  2. Click + or Add, then Add marketplace (it may say Add from repository)
  3. Paste the line below and confirm with Add or Sync
  4. Install Pixfizz Storefront from the list
  5. Open the ··· menu next to the Pixfizz marketplace and switch on auto-update, so new skills reach you without doing this again

If Claude says Marketplace is already added, that is fine. Go straight to installing Pixfizz Storefront.

pixfizz/claude-plugins
In Claude Code, from a terminal
/plugin marketplace add pixfizz/claude-plugins /plugin install pixfizz@pixfizz
The two are separate. Claude Code and the desktop app keep their own plugin lists and do not sync. If you use both, install in both. In the browser at claude.ai the /plugin commands are not available at all.

What is in it

liquid-patterns
Shopper templating rules — CSS delivery order, the sort-then-filter trap, JavaScript that survives AJAX re-injection, option rendering, redirects.
pricing-formulas
Ruby pricing formulas and the traps that make a price silently wrong, plus automatic discounts and extra fees.
product-variants
Variants and template options: which object a choice belongs on, where the price actually lives, children and triggers, and the export traps that fail silently.
xml-templates
The production specification behind a design product — geometry, bleed and safe area, PDF layers, output and fulfillment.
template-resize
Derive a product at a new size, or a whole size range from one seed, with the geometry rewritten, priced and proofed per size.
photobook-layouts
Generate the frame arrangements customers pick from in the Design Tool, written straight into a theme export.
shopify-integration
The Shopify plus Pixfizz path — metafields, product linking, theme snippets, cart previews, order webhooks, and a fault index.
shopper-ux
Conversion review of a page or flow, with separate guidance for photo labs, gifting, and school and sports photography.
storefront-copy
Hero sections, headlines, CTAs, page structure and social proof placement.
storefront-launch
What to have ready and in what order, the blocker per phase, and a pre-launch checklist.
lightspeed-importer
Turns a Lightspeed or Vend CSV export into a Pixfizz Static Product Importer CSV.
storefront-audit
Read-only health check of your live store — broken menu links, empty collections, products with no price or image, a dead Add to Cart, missing SEO titles, a sitemap that was never generated. Works best with Claude in Chrome.
fulfillment-setup
How finished orders reach production — FTP or HTTP delivery, file and folder naming, job tickets, sending the original files, and why files did not arrive.
seasonal-campaign
The offer, the landing page, order cutoff messaging and the switch-off for a holiday or promotion, using automatic discounts or promo codes.
Run /pixfizz:help after installing for the same list with an example prompt against each one. You do not have to use the commands — the skills fire on their own when your question matches.

That is the setup done

Open a conversation in your project and try one of these:

Ready-made prompt packs

Prompts written for photo and print stores. Copy one, fill in the parts in brackets, paste it into your project.

Common questions

Does it work on my phone or iPad?

Yes for asking questions: open the Claude app, go to your project and ask. Installing the plugin and working on files from your computer need the desktop app.

Will it remember my store next time?

Every new conversation inside the project starts with the Pixfizz knowledge base, your instructions and your SITE_CONTEXT.md already loaded. Always start new conversations from inside the project, not from the general chat.

Something here does not match what I see in Claude

Claude moves things around from time to time. Ask Claude itself, in the project: “Where do I add a GitHub repository to this project?” It knows its own menus. If you are still stuck, raise a ticket in myPixfizz with a screenshot.

Optional — connect your other tools

Connect your other tools

Connectors let Claude work inside the tools you already use, instead of you copying things back and forth. None of these are needed for the setup above. Pick the ones that match how you work. Tools from other companies need their own account, and some charge per use.

Two ways to add one. Listed connectors: Settings › Connectors, find it by name, connect and sign in. Anything with a URL below: Settings › Connectors › Add custom connector, paste the URL, connect. On a Team or Enterprise plan an owner may have to allow a connector first.

Start with these
Claude in Chrome

Lets Claude see and use your Chrome browser — your storefront and your Pixfizz admin, exactly as you see them. It is what makes the storefront-audit skill and a full SITE_CONTEXT.md possible, and it can walk you through an admin screen instead of describing it.

Install from the Chrome Web Store and sign in. Paid plans, Chrome only.

Let it read. You press Save, Delete, Publish and Import yourself.

Pixfizz help centre

Lets Claude search help.pixfizz.com directly, so an answer can point you at the written guide for the screen you are on.

Custom connector, URL below.

https://help.pixfizz.com/~gitbook/mcp
Images and video
Higgsfield

Image and video generation from inside Claude. One account covers several leading models, Nano Banana among them. Use it for seasonal banners, room scenes behind wall art, social posts and short product videos.

Needs a Higgsfield subscription; every generation uses credits. Custom connector, URL below.

https://mcp.higgsfield.ai/mcp
Nano Banana

Google’s image model, and our first choice for editing a real photo: placing a product shot into a scene, changing a background, keeping a look consistent across a set.

Easiest route: through Higgsfield, above. A direct connection runs on your own computer through the desktop app and needs a Google Gemini API key and a configuration file edit. Only worth it if you are comfortable with that.

Canva

Creates, fills in and exports Canva designs from a conversation, using your brand kit. Good for flyers, in-store signage, social posts and email headers.

Listed connector. Uses your Canva account.

Never let AI draw the product itself. It does not know what your lustre paper, canvas wrap, book binding or frame actually look like, and it will invent something plausible and wrong. Generate the scene, then put a real photo of your real product into it. An AI-rendered product on a product page is a misrepresented product and a refund waiting to happen. No identifiable real people without consent, and no AI-generated children for school or sports marketing.
Marketing and store
Klaviyo

Builds email campaigns and flows, and reads how they performed. Pairs with the seasonal-campaign skill: plan the offer and the page, then write and schedule the emails in one conversation.

Listed connector. Uses your Klaviyo account.

Shopify

Reads and updates your Shopify store — products, orders, collections, discount codes. Useful for catalogue clean-up and sales questions on the Shopify side of your setup.

Listed connector. Signs in to your Shopify store.

It can change your store. Products that open the Pixfizz editor are linked to Pixfizz, so ask it to check the link before renaming, deleting or changing variants on any of them.

Google Drive or Microsoft 365

Lets Claude read your own documents — price lists, supplier spec sheets, brand guidelines, order exports — instead of you pasting them in.

Listed connectors. Use the one your business already runs on.

Before you rely on it

What this setup is good at, and what it is not

It is good at explaining how the platform works, orienting you in the admin, drafting storefront copy, talking you through a setup you have not done before, and narrowing down where a problem probably sits before you raise a ticket.

It is not a substitute for support on anything that touches your live data. It sees your admin only through Claude in Chrome, and only what you open. It does not know your contract, your pricing or your production setup.

Never paste a formula or code change into a live store on its word alone. Pricing formulas, Liquid snippets and template changes affect real orders and real money. Test first, or send it to us.
If an answer looks wrong, it probably is. Ask it which knowledge file the answer came from. If it cannot name one, or names a file that does not exist, it is filling a gap rather than reading. Bring it to us and we will fix the underlying documentation.
Where to go next

Pixfizz resources