Rebuilding saults.io

The old site was a Squarespace template. Stock 3D renders I didn’t make, a green accent I didn’t pick, and a paragraph about crafting high-performance solutions that could have been about anyone. The new one is seven hand-written HTML files, no framework and no build step, on a design system locked to one palette and two typefaces.

What did the work:

• A locked design system, written as a skill. Palette, type scale, spacing and component anatomy decided once, then applied without re-deciding them every time. Two builds a year apart should look like the same hand.
• A critique agent that reviews the rendered page. It caught a nav that went illegible over screenshots, and a full-width figure sitting 24px from the next heading. That gap is 93px now.
• A mechanical detector on a file hook. It fired three findings on the home page. All three were false positives, and writing the reasons down took longer than a real fix would have.
• A de-slop pass followed by a voice pass. The first strips the AI tells, the second puts the register back. Run only the first and the writing comes out voiceless.
• Subagents for isolated work. One built the hero animation, which kept a twenty-minute verification loop out of my main thread. It also edited the same file I was editing, and the only way to know whose version survived was to check the rendered page against both our reports.
• A real browser in the loop. Every claim here about the site was checked against the live DOM rather than the source.

Where the system came from

Most of the scaffolding came out of the RoboNuggets community on Skool, and the Claude Living Masterclass inside it. Two pieces of that show up directly in this site.

The first is the design system. The palette, the serif and mono pairing, and the alternating ink and paper sections are adapted from Datapoem, which is CC BY 4.0 to RoboNuggets. The credit sits in the footer of every page here, including this one. What I added was locking it into a skill. Square corners, one green, two typefaces, hairlines instead of shadows. An agent building a new page reads that file, and the page comes out looking like the rest of the site.

The second is treating skills as the unit of reuse instead of prompts. A prompt is something you retype. A skill is a file that loads when it’s relevant, and it accumulates. The de-slop pass, the voice pass and the design system are all files in one folder, and they compose. This post was drafted, stripped and voice-checked by three of them in sequence.

The RoboNuggets community is here. That’s a referral link, so I get a cut if you join through it.

What paid off

What paid off was writing the decisions down once, in a form something else could apply consistently. That bought time for the judgment calls: what to cut, which findings were false positives, what looked wrong on the page.