Features

Everything on this page ships with SpiderCaster 0.1.0. Real copy goes in, and a self-contained static site comes out. The structure, layout, and assembly are plain code, so the bulk of every build costs zero tokens.

See it work

Real output from SpiderCaster 0.1.0, captured on the build machine.

Offline drafts

One command builds a site from your words. The draft costs nothing and needs no keys.

  • No model runs on the offline path.
  • The ledger records the run at zero tokens.
  • The output is plain HTML and CSS.
Screenshot: terminal output of an offline build, with tokens requests=0 and est_cost $0.0000
build --offline

A strict checker

Every page must pass every check with zero failures. One failure stops the job.

  • Words against copy, links, photos, and the small print.
  • A skip means the check did not run, and not run is never a pass.
  • The last line counts pass, fail, warn, and skip.
Screenshot: the last lines of the checker run on this site, ending with the result line
check

Seven seats

Architect, content, frontend, graphics, visual critic, SEO, deployer. None of them publish.

  • The doctor checks that every seat has its hands.
  • It lists the molds and the section frames.
  • "ok": true means everything lines up.
Screenshot: terminal output of the doctor command, listing 4 molds, 14 frames and 7 seats with ok true
doctor

Plain files out

The site is ordinary HTML and CSS with the style baked in. No database, no login, no upkeep.

  • Pages read well on a phone.
  • Fonts and photos sit in the site folder.
  • Nothing loads from another site.
Screenshot: the Commands docs page of this site on a 390-pixel-wide phone screen

What you get

Offline drafts

One command builds a site from your words. The draft costs nothing and needs no keys.

Optional AI help

A free chain of models can plan the shape of the site. Paid models join only on an explicit flag.

Small edits

The refine command patches one section of a built site instead of rebuilding the whole site.

Zero-token rebuilds

Edit site.json and rebuild from it with build --from. No model runs.

A strict checker

Every page must pass every check with zero failures. One failure stops the job.

Plain files out

The site is ordinary HTML and CSS with the style baked in. No database, no login, no upkeep.

A studio desk

A desk on localhost with rooms for the plan, the paint, the check, and the preview. It does not publish.

Seven seats

Architect, content, frontend, graphics, visual critic, SEO, deployer. None of them publish.

The rules it runs on

Six rules sit under every build.

Nothing invented

The builder only uses words it was given. A missing fact stays missing.

Hidden first

Pages stay out of search results until a person signs off on the words.

Local photos only

A photo must sit in the project folder. Web addresses for photos are dropped.

Keys stay out

The engine reads key names from the environment. The values never touch the disk.

Every run counted

Each attempt lands in a ledger with its token count, pass or fail.

Plain Python

Version 3.11 or newer, standard library only, nothing to install.

The check gate

The checker reads every page before anything moves. Words against copy, links, photos, and the small print: title, description, noindex. One failure stops the job. Zero is the only passing score.

Start with words.

Build a site like this. One page of writing is enough for a first draft. The draft costs nothing, and the files are yours to keep.