AI Toolkit Site
An enablement program is only as good as the thing people actually open. This one is maintained like a product.
Context
Training decks get forgotten. A living toolkit site, maintained like a product instead of a one-time deliverable, is the difference between “we ran a workshop once” and “here’s where you go when you’re stuck.”
What I built
An Astro-built site with a token-based design system, maintained in Cursor. Home base for the AI Foundations program: prompt library access, learning and development curriculum, agent references, and the AI Alphabet.
Structure includes /learning-development with six lesson pages (Step 0 and Prompting, Context, Iteration, Verification, Judgment, plus a queued “What’s Next” routing section) and /alphabet for the 26-entry heritage site. Design system rules: no hardcoded hex values, no box-shadow for elevation, display serif restricted to hero H1 only.
How it worked
I ran a structured UX audit against Nielsen, Shneiderman, Gestalt, Norman, and Tognazzini heuristics. That produced a master revision doc with P1, P2, and P3 prioritization. We resolved P1 homepage issues first. The Foundations page became the internal exemplar, the page other pages get rebuilt to match.
Standing rule: resolve two medium-priority QA issues before starting new curriculum build-out.
Outcome
A builder signal for hiring managers and peers. Design system discipline, heuristic review, and a site that iterates on evidence rather than vibes. Proof that the program has a real front door, not just a deck archive.
What I’d do next
Ship the Agent Building curriculum track queued at /learning-development/agent-building. Capture before/after homepage P1 fixes as portfolio visuals once screenshots are cleared.