Quitine

Quitine sells pharmacist-led nicotine gum, lozenges and patches, with a 90-day plan behind them. The store ran on a Shopify theme, a ready-made design template, and the theme had become the limit. The client wanted to publish a landing page in an afternoon, control every element on every page, and launch things a theme does not allow: a quiz that builds a kit and goes straight to checkout, pages without the usual menu and footer for visitors from ads, and A/B tests that compare two versions of a whole page.

The design came from the client's own team. Our job was everything underneath it: the store, the content system, and the way it gets edited.

The client did not want to learn new editing software. He wanted to say what he needed. So he edits the site through a Claude skill we wrote, a set of instructions telling Claude what the site is made of: every block and every field, how a page is put together, how the quiz works, and how tracking and A/B tests are set up. It sits in his own Claude, next to the Sanity MCP, a connection that lets Claude read and change the content, and a small MCP of ours that uploads images. Together they turn a request into the work. New landing page for a campaign. Duplicate this page and change the top section. Add three FAQs. Import this article with its images. Set up a test on the homepage.

The rules are in the skill: read before writing, save drafts first, publish only when he confirms, never invent a field, and ask before touching anything shared. It also says plainly when a request needs a developer, which is rare. When the content structure changes, the skill is updated with it, so Claude never works from an old version of the site.