Skip to content

0.34

Choose a tag to compare

@karero karero released this 28 Oct 14:16
Immutable release. Only release title and notes can be modified.
99b72e1

Croftweaver 0.34 — a launch check you can read, and lighter pages on phones 🚀

As always: your favorite AI assistant takes you by the hand. Just ask it, in your own words, and it does the work.

What's new:

  • 🚀 Know when your site is ready to launch. A new launch check runs your site's own build and tests first, then looks at what they can't: the imprint, privacy page and cookie banner, the signs that show visitors and search engines who is behind the site, permission for your testimonials, and what only the live site shows. It asks you only where your intent decides. Each run leaves a dated report in docs/launch/, as a page you can open in your browser. If your new site replaces an older one, it also compares the two and lists where every old address should point. Your assistant runs it three times along the way: right after setup, before launch, and once more when the site is live if you like.
  • 📱 Pages that stay light on phones. New sites get a check that loads every page the way a phone does and catches pictures far bigger than a phone can show, including background pictures, which Google's own speed test doesn't size. It also catches a picture that's downloaded but never shown. When it finds one, your assistant makes a smaller copy for phones. On a site built with this toolkit, fixes like these took Google's phone speed score from 98 to 100.
  • ⏱️ Speed checks without the homework. Your assistant now runs Google's speed test (Lighthouse) itself, five times, and reports the middle result, first on your preview and again once the site is live. It only asks you to run PageSpeed when it can't.
  • 🗂️ Your reports have fixed places. Search and AI-visibility findings now go in docs/seo/ and docs/geo/, and the raw data stays in an analytics/ folder that git leaves out, so it never lands in your repository. Nothing moves in your site until you run one of these helpers there; an existing findings file is moved once, and your assistant asks when it finds two.
  • ✅ Clearer word after publishing (for sites with a preview and a live version). While your site's address is still Cloudflare's own pages.dev one, publishing now ends "Published — verified on the pages.dev address", and says your site is live on your own domain only once that's connected. Before, it said "LIVE", which sounded as if your domain was already working.
  • 🛡️ Your site's checks run on a safe Node.js. When your site's automatic checks run on GitHub, they now fetch the newest Node.js 24 instead of an older copy GitHub had lying around. One site's checks had run on a version without the October security fixes.
  • ⌨️ A keyboard outline you can actually see. The test for your tables now also checks that the outline showing where the keyboard is stays visible: at least 2 pixels wide, and standing out clearly from the background, in light and dark mode. Before, an outline of zero width passed.
  • 📝 Contact forms that ask what you need to know. A page can now add its own fields to the contact form, such as a phone number or a preferred date, and a short hint above the message. Your assistant knows what to ask you and how to set it up. And the email your visitor's mail program opens now starts with a greeting you choose and ends with a polite sign-off in the form's language, so it reads like a real letter.
  • ✉️ Contact forms in more languages. If your contact form is in a language other than English or German, its test now catches an email address that would show up as "name [at] example [dot] com". And adding a language now reminds you that it needs its own privacy page.
  • 🟢 A smoother, safer first few minutes. When you start a new site, your assistant no longer shows red "Error" lines for checks that went fine, and it asks its first questions in plain chat instead of a pick-list box you might not see. It never tucks your site away in a hidden folder you couldn't find again; it asks you for a folder you can see. Setting up no longer stops halfway to wait for a key press, and your site's first test run is green.
  • 🔐 Your passwords and keys stay out of git from the start. Setting up a new site used to swap the toolkit's list of files to keep out of git for a shorter one, which no longer kept files like .dev.vars (where your site's secret keys live) out of your repository. Your assistant now puts the full list back straight away.
  • 🏷️ A small "made with Croftweaver" tag, and you decide. New sites carry a tiny name tag in their pages' code, the way many site builders sign their work. Visitors don't see it on the page, it sends nothing and links nowhere. Your assistant tells you about it once after the first build; say "remove the Croftweaver tag" and it's gone.
  • 🧪 Two copies of one site can test at the same time. Each copy of your site's folder now runs its tests on its own address, and a new test makes sure the page being tested really comes from that copy. Before, two copies could quietly test each other's pages.
  • 📖 A README that shows before it tells. The README now opens with a picture of croftweaver.com, a finished site to look at, and a one-line install, and it says plainly which Node.js version installing needs and which building a site needs. It also lists every outside service a helper talks to, and what it sends, with a link to the full details.
  • 🧹 Behind the scenes. The installers handle a relative skills folder correctly in an unusual shell setup, the Pages-or-Workers guide has a new speed-comparison step with every source re-checked, and your assistant's second opinion on its own work can now take measured evidence beside the change, names an empty reviewer balance plainly, and says so when only one of its two reviewers counted instead of quietly asking a third.

🔁 Already have a site? Nothing changes on its own. One check is worth doing today: ask "compare my .gitignore with the latest Croftweaver starter's and add the lines it's missing, keeping my own". To get the phone check, ask: "add the phone-images test from the latest Croftweaver starter". It may find pictures to shrink on your first run; that's the point. If your site publishes in two stages, ask: "update my publish script to the latest Croftweaver version". For the safer Node.js and the keyboard-outline check, ask: "update my CI file and tables test from the latest Croftweaver starter"; if the outline test turns red, the outline is what to fix. To add fields to an existing contact form, ask: "add a phone-number field to my contact form, the way the latest Croftweaver does it". For the greeting and sign-off, ask: "give my contact form's email a greeting and sign-off, from the latest Croftweaver"; your assistant keeps your own texts and merges the test by hand. If your contact form isn't in English or German, ask: "add the new [dot] check to my contact form test". For the launch check, ask: "copy the website-launch-check skill from the latest Croftweaver into my site". For separate test addresses per copy, ask: "take the test-port files from the latest Croftweaver starter, all three together". If you got the toolkit straight from GitHub (rather than as the download below), ask: "check if my site needs any updates from the latest Croftweaver version".

New here? How to start: download croftweaver.zip below, unzip it, and paste the starter prompt from the README into your AI assistant. It takes you by the hand from there. Works on macOS, Linux, WSL, and Git Bash on Windows. To check the download, put SHA256SUMS beside it and follow the README's two-line check.


For the technically curious, 0.34:

  • New skill website-launch-check (always-on, now twenty-eight): runs the site's build and tests first, then checks only what they cannot; writes docs/launch/<date> as Markdown and a self-contained HTML page (scripts/report_html.py: element allowlist, strict link pattern, escaping, CSP meta); a current-vs-new comparison with a redirect map from wordpress-inspector's moves.csv. new-website runs it at steps 5a, 10c and 12a. A site made earlier copies skills/website-launch-check in by hand (whats-new reports only skills a site already has). make test-launch-check, 17 tests — PR #426.
  • new-website §1–§3: the folder check, the interview and the §2a/§2b offers read with the assistant's file tools; where only a shell can read, commands that succeed on every ordinary answer (ls -A, cat). §2a, §2b, §3a and §4b ask in plain chat, not a pick-list. Later steps can still show a red line on an ordinary result — PR #425. §3 never offers a hidden folder (a path part starting with a dot) or a tool's scratch or temp folder as the websites folder; step 1 runs npm create --yes astro@latest . -- --template minimal --no-install --no-git --yes --skip-houston, then git checkout -- .gitignore, because create-astro replaces step 0's .gitignore with its own (no .env.*, .dev.vars, .wrangler/, sign-in file or /analytics/ lines); and it sets the domain in public/robots.txt and public/llms.txt too. Checked with npm 11.20.0 and create-astro 5.3.1; the starter's first npm test passed (114 passed, 1 skipped) — PR #435.
  • Starter: Base.astro writes <meta name="generator" content="Croftweaver"> into every page while GENERATOR_TAG in src/config.ts is true (the default); false removes it. new-website tells the owner once after the first green run and records "generator tag: on" in the project README; tests/seo.spec.ts checks the tag follows the setting. Existing sites get nothing unless they add it — PR #436.
  • Starter: the Playwright port is keyed on the folder holding playwright.config.ts, not SITE.url; scripts/build-marker.mjs writes dist/test-build-id.txt in test builds only, and the new tests/served-build.spec.ts checks the server answering is this checkout's build. Take playwright.config.ts, scripts/build-marker.mjs and the spec together (the spec alone fails). Several people or assistants publishing from one folder should also switch on ship.fromGitHub — PR #424.
  • Starter: tests/phone-images.spec.ts loads each page at 412px, 1.75x with touch, scrolls to a settled end (20 s budget) and judges every raster the page downloads, CSS backgrounds, masks and list markers included. It fails a file wider than 1.1 × 3 × its drawn width when cutting it to that width saves an estimated 4 KiB or more, a file downloaded but shown nowhere, one of 4 KiB or more hidden at phone width, and a size it cannot work out; a file used only as a border image, cursor or shape-outside is named in the log, not judged by width. A template-tests job proves it on generated images. whats-new.sh does not refresh a site's tests: copy the file in — PR #409, PR #412, plan status PR #410.
  • website-qa "Performance": the agent runs lighthouse@13 from a scratch folder against the main preview before launch and production after, five mobile runs plus one desktop, and reports the median; pagespeed.web.dev in the built-in browser is the fallback; a short list of fixes that worked — PR #409.
  • Report folders: seo-reposition keeps SEO-FINDINGS.md and SEO-CHANGELOG.md in docs/seo/; seo-audit can save docs/seo/seo-audit-<date>.md; the AI check's conclusions can go in docs/geo/; search-console-insights' --out paths point into analytics/<date>_gsc/ and analytics/<date>_bing/ — PR #406.
  • Two-stage sites: scripts/ship.sh and tests/check_ship_push.sh are template-version 0.23; take them together. A *.pages.dev site: ends "✓ Published — verified on the pages.dev address"; exit codes unchanged — PR #413.
  • Starter CI: actions/setup-node gets check-latest: true in the starter's ci.yml (and the toolkit's own 18 setup-node steps); whats-new lists ci.yml, and a site that keeps its own CI adds the one line. New guard G6 in scripts/check_node_floor.sh. tests/tables.spec.ts fails a focus ring under 2px or under 3:1 against the solid background, both themes; take the spec whole — PR #423.
  • website-contact-form: tests/mail-form.spec.ts fails when a non-English form's no-JavaScript address shows "[dot]" (a language missing from DOT_WORD in src/lib/obfuscate.ts); existing sites add the new lines to their own spec by hand rather than copying it over. "Add a language" gains a privacy-page step — PR #422. A page adds fields and a hint between <MailForm> and </MailForm> (new "Adding fields" section); a site that wants them takes the new MailForm.astro, and from the new spec the ADDED constant and its two tests; sites without added fields need nothing — PR #431. The mail starts with greeting="…" (required on <MailForm>) and ends with the language's signoff; take MailForm.astro, public/js/mail-form.js and src/components/mail-form-text.ts together (the new spec fails on the old script), and merge tests/mail-form.spec.ts by hand (keep PAGE, TO, SUBJECT, LANG, ADDED; add GREETING and the mail helper) — PR #434.
  • README: home-page screenshot, case study link, quick install near the top — PR #420; Node minimums (installer 22.12+, sites the starter's engines) — PR #432. README "What leaves your computer" — PR #404. Installers: a relative CLAUDE_SKILLS_DIR/CODEX_SKILLS_DIR is made absolute before the pin check, so an exported CDPATH can no longer re-point a pinned skill — PR #402. docs/PAGES-OR-WORKERS.md: trial step 9 (time to first byte), sources re-checked — PR #408; results of a one-site Workers trial (route B worked as documented; wrangler preview needs a previews block, a Preview's missing page gets a bare "Not found", workers.dev carries no noindex) — PR #433.
  • Releases also update the branch directory (the plugin without the toolkit's own tests and independent-review), for a future listing in Anthropic's plugin directory; .claude-plugin/icon.png — PR #403, plan PR #401.
  • independent-review: --wording-pass puts the prose-only scope in the script's own prompt — PR #405; --evidence <file> sends evidence beside the artifact as labelled data — PR #407, and read-backs of remote systems go there — PR #430; an empty Melious balance is named as quota — PR #411; with SECOND_SEAT=melious the Melious seat has no ollama fallback, ollama list is read only when ollama can run, and a round where only Codex counted ends with a line saying so; the default pair is unchanged — PR #417, plan PR #415; an empty balance (billing_insufficient_balance) ends the round "codex alone", no rerun owed — PR #429.
  • Maintenance: docs/BUGLOG.md merges with git's union driver, and scripts/check_buglog_rows.sh catches a row kept twice — PR #416; BUGLOG rows and plan status — PR #400, PR #414, PR #419, PR #421, PR #427, PR #428; version 0.34.0 — PR #418.