1
0 Comments

We wrote a 1,900-line cookbook so your AI can build a webshop. Here's why.

Solo founder here, building WebsitePublisher.ai — a platform where AI assistants (Claude, ChatGPT, Cursor, and others) build and publish complete websites through MCP tools.

This week I shipped something that felt counterintuitive at first: a document as a product feature.

Here's the thing I keep seeing with new users. They treat AI like code: type a wish, expect a deterministic result. Then the AI improvises, gets 80% right, and the last 20% costs them a whole evening.

The fix isn't a smarter model. It's better context.

So we wrote the E-commerce Cookbook: 1,900 lines of markdown covering every step of building a webshop on our platform — 14 integrations, checkout orchestration, admin auth, all the pitfalls we hit ourselves (and we hit them all first, so users don't have to).

The user experience: a tile on the dashboard → copy one prompt → paste into your AI → it builds the whole shop following the recipe. Storefront, payments, shop admin.

What I learned shipping this:

  • Documentation is product when your users are AI agents. A markdown file on a CDN turned out to be the highest-leverage feature I shipped this quarter.

  • Writing down your own pitfalls compounds. Every mistake we documented is a mistake no user's AI makes again.

  • "AI = context" beats "AI = magic" every single time.

Curious how other founders here are handling this: are you writing docs for humans, for AI agents, or both?

posted toAvatar for product WebsitePublisher.ai
WebsitePublisher.ai