How ForgeKit
gets built.

Built a print-ready one-page brochure for local business outreach. Refreshed homepage product cards with real background images and customer stories. Softened copy across the site.

Trends page rebuilt from scratch — velocity, outcomes, what worked, what's next. Contact form replaced the repeated nav links. Resend wired up.

ShowUp parked. Leashline born. Full v0.1 scaffold in one session — database, seed data, Today's Route screen, Clients, Schedule, Clerk auth, deployed.

Built ForgeHome from scratch and extracted shared packages. The Rounds engine now has a template. A new app takes 15 minutes to scaffold.

Shipped ForgeHome to production. Built the /add-product skill mid-session when we recognized the pattern. The engine learned while we shipped.

Added Leashline to the public face of ForgeKit. Four products, two engines, one homepage. Mobile heroes fixed across all three product pages.

Full route UX overhaul · Sally's scenarios (5 edge cases) · First deploy to leashline.forgekits.build · Brand applied · Rail + Rounds engines named · Armory split into two catalogs

No features shipped. The engine got smarter. Session compiler, trends generator, Armory index, quick-ref summaries, core principle named. Every future session is cheaper because of this one.

About page sharpened · Armory catalog (18 files) · Product discovery → ShowUp named

Forge Phase 2 · ForgeKit website launched · PilotLight safety gate + 58 tests

Automations · Test suite · Brand identity system · Splash page · Settings

Full-stack CRM from zero · Pipeline kanban · Clerk auth · Neon Postgres · BOM hell

Narrative start page · Voice narration kit · Geolocation opt-in · Accessibility · Demo hardening

Game loop → full app · Chromagram scoring · Chromatic tuner · Feel Trainer · SoundCheck rebrand

Local history time-machine · AI research engine · Montville story · Map + slideshow