Forgevik Technologies

Engineering notes

This site was engineered with Claude, end to end.

Every page, every interaction, every line of code here came out of a spec-first, AI-native build process — the same one behind Forgevik’s product portfolio.

The process

1

Spec, then build

Nothing ships without a written plan first — the exact approach, the files it touches, and what "done" looks like — agreed before a single line changes.

2

Execute task-by-task

Implementation moves in small, reviewable steps rather than one large speculative rewrite, so every change stays easy to reason about.

3

Verify, don’t assume

Every change is checked against a real build and a real browser — a production build plus a manual pass through every affected page, theme, and breakpoint.

4

Record the learnings

Each pass is logged — what changed, why, and what’s next — so the following iteration starts from real context instead of guesswork.

Engineering log

What that looks like in practice.

2026-07-04Replaced a broken og:image reference with a generated, on-brand social preview card.
2026-07-04Fixed a body-text color that failed WCAG AA contrast (3.54:1 → 4.83:1).
2026-07-04Consolidated hand-duplicated buttons, headings, and labels into one shared design system.
2026-07-06Shipped full dark mode, pointer-driven 3D product cards, magnetic buttons — and this page.

Why this matters for you.

The products in this portfolio — MyAIHR, DevTiles, Rove Viewer, StreetGuide AI — are built the same way: specified, executed, verified, and logged. If this page convinced you the process holds up under scrutiny, that’s the point.