< Documentation Home

Using AI Tools to Manage Your Site

A WebHaste site is comprised of HTML files on your device β€” which means Claude Code and other AI coding tools can read, edit, and even preview the site directly.

Every new WebHaste project is scaffolded with a CLAUDE.md file at its root. It's written specifically to brief an AI agent on this site's conventions β€” fragment pages, template placeholders, how nav.json/pages.json wire pages together, the block format, and so on β€” so a fresh agent session already understands the format before you ask it to do anything. Alongside it, four agent skills in .claude/skills/ go into more detail for common jobs β€” building pages and templates, migrating a WordPress site, auditing SEO and accessibility, and working with Lists.

You never have to explain WebHaste to your AI tools from scratch.

πŸ”ŽClaude Code in an IDE or terminal

Open your site's project folder as the workspace root (in VS Code, a JetBrains IDE, or a plain terminal) and Claude Code will automatically discover and read the root CLAUDE.md. From there you can ask it to do the same things you'd do by hand in the extension. 

Some examples:

  • "Add a new page called pricing.html and link it under the header nav's Documentation menu."
  • "Translate about.html into Spanish, save it as about-es.html, and set its language override in pages.json."
  • "Add a Testimonial block to index.html using this quote and name: ..."
  • "Mark blog/draft-post.html as a draft so it's excluded from Publish and the sitemap."

Because a page file is a body-content fragment, not a full HTML document, an agent can't just open the page in a browser to check its work β€” it needs the template/nav substitution applied first. Every project ships with .webhaste/compose.js to do exactly that headlessly:

node .webhaste/compose.js --out .agent-preview

That writes fully composed pages into a scratch folder inside your project, matching what "Render to Local Folder" or Publish would actually produce. Ask the agent to run this after making changes, then open the result in a browser to check it β€” and to delete the scratch folder when it's done, since it's not meant to be committed.

Add --packaged to check what a Packaged copy would look like. Some config files are regenerated every time you open the project in the extension, so edits an agent makes to them won't stick: .webhaste/compose.js, .webhaste/compose-core.js, and .webhaste/block-library.md. If you ask an agent to change how a block looks or add a new built-in one, point it at the extension's block system rather than a generated file.

Two further checks render nothing and write no files, so they're quick to run after every change:

  • node .webhaste/compose.js --check-links lists every internal link, in pages and menus, that doesn't lead to a page or a file in assets/, scripts/ or elements/. It's the same check as Check Links in the editor. Links to other websites, mailto:, tel: and same-page #anchors aren't checked.
  • node .webhaste/compose.js --validate checks your settings files against each other: a template that doesn't exist, a pages.json entry for a page that's been renamed or deleted, a menu item with no label, a {{NAV:name}} placeholder for a menu that isn't in nav.json, and redirect rules that are malformed or chained. This one matters because the editor quietly falls back to defaults when a settings file is broken, so a typo can otherwise go unnoticed until the site looks wrong.

Both report a problem with a non-zero exit code, which an agent reads as "something needs fixing". --validate separates errors from warnings and only fails on errors. Neither publishes anything.

Built-in agent skills

A skill is a short set of instructions an AI agent loads only when your request calls for it. Every WebHaste project gets four:

  • building-webhaste-site β€” the conventions for pages, templates, nav.json, pages.json, blocks, site.config.json and testing.
  • migrating-wordpress-to-webhaste β€” turns a static export of a WordPress site (we've tested it with sites exported by the Simply Static plugin) into a WebHaste template, pages, blocks and menus, and leaves a MIGRATION-NOTES.md listing what it skipped, replaced with placeholders, or wasn't sure about.
  • optimizing-seo-and-accessibility β€” audits titles, descriptions, headings, alt text, link text, page landmarks and structured data. It fixes the safe items (like a missing description or alt text) and writes a SEO-ADA-REPORT.md with everything that needs your decision.
  • using-webhaste-lists β€” creating and editing Lists, placing them on pages, and adding DataTables.

Agents usually pick the right skill on their own, but naming it in your prompt makes sure β€” for example: "Use the migrating-wordpress-to-webhaste skill. The static export is at C:\projects\old-site and the new WebHaste project is this folder."

WebHaste keeps the skills current for you. When a newer version ships, opening the project updates any skill file you haven't changed and leaves files you've edited alone (a replaced older copy is saved under .webhaste/backups/).

πŸ’»AI Desktop apps

Most AI desktop apps don't have direct filesystem access β€” it's chat-only unless you connect a local filesystem MCP server pointed at your site's folder (Settings β†’ Connectors). Without that, a desktop app is still useful for the parts of site work that don't need direct access: drafting page copy, brainstorming a page's structure or a new block's content, or reviewing a pasted-in nav.json/page fragment and suggesting edits you copy back by hand.

With a filesystem MCP server connected, your desktop app can read and write your project the same way Claude Code does, including running compose.js if the connector allows shell access.

Other AI coding tools

Cursor, Windsurf, GitHub Copilot Chat, and similar tools work the same way in principle β€” they read and write real files, and most look for a root instructions file to pick up project conventions automatically. If a particular tool doesn't recognize CLAUDE.md on its own, you can usually point it at the file directly, or copy the relevant sections into whatever instructions file it does expect.

❌What AI tools can't do

  • Publish. Your Cloudflare/Netlify credentials live in the browser extension's local storage, not in any project file, so only the extension's own Publish button can actually ship your site. An agent can compose and check pages locally, but the last step is still a click in WebHaste.
  • Reconnect folder access. Chrome requires a one-click "reconnect" after the extension's folder permission lapses β€” that's a browser security requirement.

πŸ’‘Prompt cheat sheet

Once you're up and running with a local AI agent to directly edit your site, here are a few prompts to get started:

  • "Read .webhaste/block-library.md and list the blocks available on this site."
  • "Add a new page, link it in the footer nav, and give it a title and meta description in pages.json."
  • "Using the generic HTML template found at C:/mytemplate.html as a basis, create a WebHaste template and block partials for this project, using Bootstrap 5.x as the CSS framework"
  • "Change this site's cssFramework to Tailwind and scaffold the build tooling."
  • "Run --validate and --check-links on this site and fix anything they report."
  • "Write a custom block for a pricing table and save it under .webhaste/blocks/ so it shows up in the Blocks dialog."
  • "Audit this site for SEO and accessibility and fix what is safe - put everything else in a report."
  • "Create a Team list with name, role, photo and profile link, then show it as a directory on about.html."

πŸ€–Hosted AI/content tools (Sintra, Marblism, Grammarly, etc.)

Hosted AI services or writing tools are typically not local agents that can open your project folder directly, so they can't read CLAUDE.md, site.config.json, or anything else the way Claude Code can or even make direct changes. But similar to a desktop AI app with no MCP connector, you can use these services to help create/manage/improve your site's content via copy-paste.

Some hosted AI services that you can use to edit/create content and then move to WebHaste via copy/paste:

  • Lindy
  • Copy.ai
  • Jasper
  • Grammarly
  • Sintra
  • Marblism

It helps to tell the remote tool, directly in the prompt, the handful of facts a local agent would need to look up:

  • Write body content only β€” no <!DOCTYPE>, <html>, <head>, or <body> tags. The site's template supplies all of that.
  • Which CSS framework to write class names for β€” check cssFramework in .webhaste/site.config.json (bootstrap5, tailwind, or none) and say so explicitly.
  • Which paragraph style to use β€” paragraphMode in the same file, either p or div.

Paste the content provided by your service directly into WebHaste's Code view rather than Visual view β€” hosted tools may add extra wrapper <div>s or inline styles, and Code view is where you can clean that up before it becomes part of the page. Since the tool never saw your real template, always check the result in Live Preview afterward rather than trusting it sight unseen.

If your service is consistently adding inline style definitions or unwanted structure, prompt it to provide content with only basic HTML tags like p, br, ul, ol, strong, and em.

If you are downloading DOCX or PDF formatted documents, you may end up pasting unwanted formatting into WebHaste, or lists may include spaces and bullet characters instead of the appropriate markup. If your AI service can't provide actual HTML code that you can paste into code view, ask it to provide your content with only basic formatting.

If you have an existing page and want your hosted service to make changes, you can copy the entire contents of that page in code view and paste that directly into the external tool's chat, coupled with your prompt. For example:

"Rewrite the HTML content below to summarize key concepts as groups of bullet points, and check to make sure the result has a Flesch reading score of 70 or lower. Return the edited page as an HTML stub similar to what is provided: <pasted page code here>"

Copy or download the edited HTML code to paste back into WebHaste in code view.

Additionally, these services typically are able to provide SEO-optimized titles, meta descriptions and summaries that you can paste into WebHaste, as well as generate social media posts to promote your site.