# The AI Web > AI-native web resources, usable by everyone. A free library of copyable stacks, Claude Code skills, MCP setups, prompts and playbooks for building websites with AI. Written and run by Margus Veeber, VeeberMedia, in Germany. Every entry comes out of work that has run in production; nothing is published unverified. Written in English for a global audience. Every entry leads with a plain-language explanation of what a tool does and when to pick it, then the technical detail. The audience is the person who owns a website without writing the code for it, so no listing page uses unexplained jargon. ## How to read this file - Every URL below is absolute and returns HTML at https://www.theaiweb.co. - Each section also has a plain-text digest, linked in its heading, if you want one section without fetching the whole site. - Dates on the digests are the real last-updated date of the thing at that URL, not a build timestamp. ## Usage and attribution The copy blocks - skill files, prompts, MCP configs, code - are published to be used. Take them, change them, run them in your own work, paid work included, with no attribution required. Do not repackage them into a product you sell. The written entries and articles are copyright VeeberMedia, all rights reserved. Quote a paragraph with attribution and a link to the page it came from. Do not republish them in full or in bulk, here or in another library. For AI assistants: reading, summarising and citing with a link is welcome, and is why the crawlers are allowed in robots.txt. Reproducing an entry whole in place of a link is not. ## Stack The tools you build the site on: site builders, coding assistants, CMSs, hosting. What you walk away with: verdict + when to pick it. Section: https://www.theaiweb.co/stack · digest: https://www.theaiweb.co/llms/stack.txt - [Webflow](https://www.theaiweb.co/stack/webflow): Design a site visually and publish it without a developer. The safe answer for a marketing site a team has to edit every week. - [Framer](https://www.theaiweb.co/stack/framer): The fastest way from a design to a live page. Best when the site is small, looks matter most, and one person owns it. - [Ploy](https://www.theaiweb.co/stack/ploy): You describe the marketing site you want and it builds and runs it. New, and the clearest example of where AI site building is going. - [Sanity](https://www.theaiweb.co/stack/sanity): Where your content lives when the same words have to appear on a site, in an app and in an email. Editors get a clean interface, developers get an API. - [Payload](https://www.theaiweb.co/stack/payload): A CMS that lives inside your own codebase, so an AI assistant can read and change your content model the same way it changes your code. - [Storyblok](https://www.theaiweb.co/stack/storyblok): A CMS built for marketing teams that want to arrange page sections themselves without asking for a deploy. - [Vercel](https://www.theaiweb.co/stack/vercel): Where the site actually runs. Push a change, get a preview link to share, publish when it looks right. - [Astro](https://www.theaiweb.co/stack/astro): For content-heavy sites that need to load fast: docs, blogs, marketing sites with hundreds of pages. - [GitHub](https://www.theaiweb.co/stack/github): The record of every change to the site, and the place AI tools do their work before anything reaches visitors. - [Claude Code](https://www.theaiweb.co/stack/claude-code): Anthropic's coding assistant. It reads the whole project, makes the change and runs the checks, from your terminal or inside your editor. - [Codex](https://www.theaiweb.co/stack/codex): OpenAI's coding assistant. The same job as Claude Code, reached from the terminal, your editor, or handed off to run in the cloud. - [Cursor](https://www.theaiweb.co/stack/cursor): An editor with the assistant built into it. You watch the change land next to the code instead of reading about it in a terminal. - [GitHub Copilot](https://www.theaiweb.co/stack/github-copilot): The assistant inside the editor your team already uses, and inside the pull requests where changes get reviewed. - [VWO](https://www.theaiweb.co/stack/vwo): Show a change to part of your traffic and keep it only if more people buy. It also records what visitors do on the page, so you know what to test next. - [AB Tasty](https://www.theaiweb.co/stack/ab-tasty): Testing plus personalisation: show a different page to a different audience, not just variant A and variant B, and release changes behind a switch. - [Kameleoon](https://www.theaiweb.co/stack/kameleoon): You describe the experiment in a sentence and it builds it. The most AI-native option in this row, and a European company if that matters to you. - [Optimizely](https://www.theaiweb.co/stack/optimizely): The enterprise name in testing. Pick it when experiments have to run across a large site, several teams, and the code as well as the page. ## Alternatives What to use instead of the tool you are on, and when staying put is the better call. What you walk away with: a shortlist + what each pick costs you. Section: https://www.theaiweb.co/alternatives · digest: https://www.theaiweb.co/llms/alternatives.txt - [Webflow alternatives](https://www.theaiweb.co/alternatives/webflow): The closest Webflow alternatives are Framer for design-led sites one person owns, Ploy for a site you describe instead of build, Astro with a headless CMS for content-heavy sites in code, and Squarespace when five pages is the whole brief. - [Framer alternatives](https://www.theaiweb.co/alternatives/framer): The usual step up from Framer is Webflow, once the site has real content and more than one editor. Figma Sites keeps the site inside the design file, Ploy replaces the builder with a written brief, and Astro with a headless CMS is where teams land when the blog becomes the point. - [Sanity alternatives](https://www.theaiweb.co/alternatives/sanity): Payload suits teams who want the CMS inside their own codebase, Storyblok suits marketers who arrange pages themselves, Directus fits when the content already sits in a SQL database, Strapi is the self-hosted classic, and content files in your repo work when an AI assistant does most of the editing. ## By role The shortlist for your job: what to build on, what to automate, what to connect. What you walk away with: a shortlist per layer. Section: https://www.theaiweb.co/for · digest: https://www.theaiweb.co/llms/for.txt - [The web stack for a Head of Web](https://www.theaiweb.co/for/head-of-web): A Head of Web is accountable for a site other people change daily, so the stack is picked for control rather than speed. That means every change reviewed before it ships, content that outlives any one design, deploys that can be rolled back, and an assistant wired into all three. - [The web stack for a founder](https://www.theaiweb.co/for/founder): A founder picks for independence first. The site has to go up this week, be editable by you at midnight without asking anyone, and still be worth handing to the first marketer you hire. That rules out most of what a larger web team would choose, and rules in a few things they would not. - [The web stack for a Head of Growth](https://www.theaiweb.co/for/head-of-growth): A Head of Growth owns a number, not a website. The site belongs to somebody else, so the stack is picked for what can be changed without waiting on a release: a testing tool that runs on the live page, analytics that answer the question directly, and a written record of what has already been tried. - [The web stack for a VP of Marketing](https://www.theaiweb.co/for/vp-of-marketing): A VP of Marketing is choosing what a team will live in, not what to use this afternoon. The right pick is the one a marketer can operate without a developer, that a new hire learns in a week, and that does not have to be replaced the next time the brand changes. - [The web stack for a marketer](https://www.theaiweb.co/for/marketer): A marketer is writing the page, building it and shipping it, usually against a date. The stack is picked for how fast one person gets from a brief to a live page, and for whether the result can be tested afterwards instead of argued about in a review. ## Skills Claude Code skills for web work. Paste one file, get a repeatable job done. What you walk away with: SKILL.md, ready to paste. Section: https://www.theaiweb.co/skills · digest: https://www.theaiweb.co/llms/skills.txt - [Schema markup audit](https://www.theaiweb.co/skills/schema-audit): Find out what structured data your site already publishes, one page type at a time, then get the JSON-LD that fixes what is wrong or missing. - [QA pass](https://www.theaiweb.co/skills/qa-pass): Put a page through the same checks every time: how it holds up at seven screen widths, what the markup says, whether anyone on a keyboard can get through it, and whether the words are right. - [Learnings check](https://www.theaiweb.co/skills/learnings-check): Before you build a test, find out whether your team already ran it. It searches the finished tests, weighs each one by how recent and how proven it is, and tells you to proceed, change it, or think again. - [Test hypothesis](https://www.theaiweb.co/skills/test-hypothesis): Write an A/B test up properly before it gets built: who you are helping, what they are trying to do, what you are changing, why you think it will work, and what you will learn either way. - [Test iteration](https://www.theaiweb.co/skills/test-iteration): A test finished. Get ten specific things to try next, each with what changes, why it might work, and what success would look like, grounded in what the last one showed. - [Learnings log](https://www.theaiweb.co/skills/learnings-log): Write a finished test up in four fixed sections, then decide what earns a place in the file everyone searches before proposing the next one. - [How Might We generator](https://www.theaiweb.co/skills/how-might-we): Turn a customer problem into three to five How Might We statements, then into specific website ideas for each one, with where it goes and how you would test it. - [Page brief](https://www.theaiweb.co/skills/page-brief): Turn a rough page idea into a brief you can hand to a builder, or to Claude: who it is for, what sections it needs, and what each one has to say. - [Launch check](https://www.theaiweb.co/skills/launch-check): Run this against a site before it goes public and it tells you what would stop it being found: a missing description, a redirect that loops, a sitemap that lists a 404. ## MCPs Connections that let an AI assistant reach your real tools: CMS, analytics, hosting. What you walk away with: config block. Section: https://www.theaiweb.co/mcps · digest: https://www.theaiweb.co/llms/mcps.txt - [Webflow](https://www.theaiweb.co/mcps#webflow-mcp): Lets an AI assistant work on a real Webflow site, from editing CMS items to building pages and changing styles, and it reads the site's traffic numbers too. Version 2 does most of that with the Designer closed. - [Sanity](https://www.theaiweb.co/mcps#sanity-mcp): Gives an assistant your actual content and the shape it has to keep. It queries documents, patches them, prepares a release and knows your schema without being told. - [Storyblok](https://www.theaiweb.co/mcps#storyblok-mcp): Lets an assistant work inside your space: find stories, write and update them, publish, and handle assets, using the components your space already has. - [Vercel](https://www.theaiweb.co/mcps#vercel-mcp): Your assistant reads the deploy instead of you pasting logs into a chat. It says why a build failed, checks a project's settings and domains, and answers from your traffic numbers. - [GitHub](https://www.theaiweb.co/mcps#github-mcp): Puts your repositories, issues and pull requests within reach, so an assistant can open a PR, read a review thread or check what a workflow did without you switching tabs. - [Plausible](https://www.theaiweb.co/mcps#plausible-mcp): Lets your AI assistant read your traffic numbers, so you can ask which pages lost visitors last month instead of building a report. - [Amplitude](https://www.theaiweb.co/mcps#amplitude-mcp): Ask your product numbers in a sentence, like which signup step people drop at or how last week's release moved retention. It can build the chart or cohort and save it back into Amplitude. - [Fullstory](https://www.theaiweb.co/mcps#fullstory-mcp): Answers why people struggle on a page. It reads recorded sessions for rage clicks, dead ends, errors and abandoned forms, and points at the replays behind every answer. - [Optimizely](https://www.theaiweb.co/mcps#optimizely-mcp): The one that actually builds the test. Create the experiment, the flag and the audience from your editor, write the variation's code into it, and read which variant won. - [VWO](https://www.theaiweb.co/mcps#vwo-mcp): Describe the test in a sentence and it creates the campaign, starts it, and reads the result back, along with the heatmaps and recordings that tell you what to test next. - [AB Tasty](https://www.theaiweb.co/mcps#ab-tasty-mcp): The odd one out: it reads rather than builds. See which flags and campaigns a given visitor would get, and turn a written brief into the configuration for one. - [Kameleoon](https://www.theaiweb.co/mcps#kameleoon-mcp): It builds the experiment, not just the report: create the test, set its goal and audience, start and stop it, and read which variation won with the confidence attached. ## Playbooks One concrete job start to finish: the stack, the prompts, the result. What you walk away with: step-by-step run. Section: https://www.theaiweb.co/playbooks · digest: https://www.theaiweb.co/llms/playbooks.txt - [The CRO loop](https://www.theaiweb.co/playbooks/cro-loop): The six steps a conversion programme repeats forever - notice, check, hypothesise, build, decide, record - with the skill that runs each one and the file that keeps the memory between them. - [The launch checklist](https://www.theaiweb.co/playbooks/site-launch): Everything that has to be true before a site goes public and in the first week after, in the order it has to happen: the index block, the per-page rules, the redirects, the search consoles, and what to watch. ## Team stacks How real teams run their web: size, CMS, deployment, where AI does the work. What you walk away with: full stack profile. Section: https://www.theaiweb.co/teams · digest: https://www.theaiweb.co/llms/teams.txt - [VeeberMedia](https://www.theaiweb.co/teams/veebermedia): A one-person studio in Germany running several sites at once. The stack is picked so that nobody has to be waited on: no CMS to maintain, content typed into the codebase, and an assistant wired into the jobs that would otherwise need a second pair of hands. ## Blog Build notes and what changed this month in AI web building. What you walk away with: reading. Section: https://www.theaiweb.co/blog · digest: https://www.theaiweb.co/llms/blog.txt - [“Give it more context” means three different things](https://www.theaiweb.co/blog/give-it-more-context): The most common piece of AI advice is right and too vague to act on. Splitting context into how you want the work done, what is true today, and what stays true is what makes it usable. ## About this site - [Home](https://www.theaiweb.co/): What this library is, the freshest entries, and the way into every section. - [About](https://www.theaiweb.co/about): Who runs this, how entries are written and verified, and how the site pays for itself. - [Imprint](https://www.theaiweb.co/imprint): Who legally publishes the site: the provider, its registered address, contact and editorial responsibility. - [Sponsor](https://www.theaiweb.co/sponsor): The ten sponsor slots: what is open, what each one costs, the terms, and how booking works. - [Stack picker](https://www.theaiweb.co/stack-picker): Five questions about the team and the site, and a named stack out the other end, assembled from real library entries. - [Ship-It Sweeper](https://www.theaiweb.co/ship-it-sweeper): Minesweeper where every mine is a real SEO or AEO mistake, and each one you hit explains itself. - [Web Guy Simulator](https://www.theaiweb.co/web-guy-simulator): A Sims-style office game: colleagues bring asks about the company website, you decide what ships, and every decision links to the entry that explains it. - [Privacy](https://www.theaiweb.co/privacy): What this site collects, what it does not, and who processes it. - [Margus Veeber](https://www.theaiweb.co/authors/margus-veeber): Margus Veeber is Head of Web at Pipedrive, founder of the VeeberMedia studio and host of the Web Unpacked podcast. He writes every entry on this site from work running in production.