voidsmith

Rules, not adjectives

What the forge will and will not do.

Every rule here is enforced in code. The numbers on this page are read from the same file that applies them, so they cannot drift apart.

Hard limits

Files per site
24
Total size
512 KB
One file
128 KB
Prompt length
4000 chars

File types it will write

.html.css.js.json.md.svg.txt.webmanifest

Anything a server or a shell would execute is refused outright, as is every hidden dotfile and any path that tries to leave the folder.

What every generation is asked for

  • A unique title and a 50 to 160 character description on every page.
  • Semantic landmarks, and real alt text on every image.
  • A visible focus ring that is never removed, and reduced motion honoured.
  • Responsive from 320px, with nothing that scrolls sideways.
  • No invented testimonials, statistics, addresses, phone numbers or prices.

And the patterns it is told to refuse

Two-tone gradients running violet into azure. A centred hero with a subheading and two buttons. Three-column feature cards with a line icon on each. Frosted glass as the only idea. Copy about supercharged workflows and futures that arrive today. These are described rather than quoted, because this site’s own auditor scans for the exact strings and cannot tell a rule from a breach of it.

Not done yet

Five honest gaps.

  1. 01

    The content security policy ships report-only

    It reports violations rather than blocking them, and it allows inline script because the framework inlines a bootstrap script. It widens from real reports and then flips to enforcing — never from guesswork.

  2. 02

    The forge only makes static sites

    No database, no login, no server code. That is a deliberate first-version limit, not an oversight, and the case studies show what happens when you ask for more.

  3. 03

    No push to GitHub or Vercel yet

    Output is a zip. Pushing directly into your own accounts needs OAuth apps that are not registered yet.

  4. 04

    No free tier and no subscriptions yet

    The spend gate for a shared key is written and tested, with a per-person daily limit and a hard monthly ceiling. The ceiling is set to zero, so it is closed.

  5. 05

    Generated output is not reviewed by a person

    The forge validates file paths and types. It does not audit the code it hands you for correctness or security. That part is yours.