What I built, and where.

• 5,000+agents onboardedthrough the onboarding front end I led
• 1,000+annotation agents on auto-savethe system I built for the annotation canvas
• 100SEO audit score on the marketing siteabout a 50% improvement

1. 01Advanced AI Trainer to Software Intern to Software EngineerLed the agent-facing onboarding front end, 5,000+ agents onboarded; built the auto-save system used by 1,000+ annotation agents; started the Storybook component library; raised the marketing site's SEO audit score to 100.buildReactTanStackFastAPINeo4jStorybookOnboarding.Auto-save.Components.the onboarding front end I led · the auto-save system I built · the Storybook library I startedRead the case study →

• 1,100+tests behind the interactive tutorialeternalquestoflegends.com
• 8bot personalities to play againstcowtastrophe.com
• 2iterations of the Gamefound campaign pagedesigned in Figma

1. 01Eternal Quest of LegendsAn 8-act interactive tutorial and card gallery at eternalquestoflegends.com, with 1,100+ tests behind it, plus the Gamefound campaign page, the convention handouts and the art direction.design + buildFigma4faction colorways of one convention handout templateRead the case study →
2. 02CowtastropheA browser version at cowtastrophe.com with a rules engine, 8 bot personalities and online rooms.design + buildCowtastropheno shippable art yet, so type stands inRead the case study →

Box and card illustration by commissioned artists, credited by name on each card. Layout, type and art direction: Wesley.

• 2builds of the same siteNext.js in 2023, Storyblok in 2026
• Weeklybulletin I designfor the same church

1. 01Design and build; I also design the weekly bulletinA 2023 Next.js redesign with custom Bible reading plans, then a 2026 rebuild on Storyblok so staff edit content themselves. Live on Netlify at carlislecofc.com. I also design the weekly bulletin.design + buildNext.jsStoryblokNetlifyRead the case study →

Page two of the weekly bulletin: a diagonal split, a numbered plan with hand arrows, script headings with wavy underlines.

• 3accessible React design systems113-130 components each, WCAG AA checked in CI
• 82automated checks behind a 10-stage merge gatethe engineering standard I wrote
• 3front ends for ChurchVuea church admin app, a member app and a Bible-learning app

1. 01ChurchVueA church software platform for acapella churches of Christ. I designed and built its front ends: a church admin app, a 10-screen mobile member app and a 13-game Bible-learning app.design + buildTypeScripttRPCPostgres10screens in the mobile member appAdmin.Member.Games.1 admin app · 10-screen member app · 13-game Bible-learning appRead the case study →
2. 02Three design systemsThree accessible React design systems, 113-130 components each, with design tokens layered Style, then Brand, then Theme; light and dark; WCAG AA contrast checked in CI; Storybook; published as private npm packages.design + buildReactTypeScriptdesign tokensStorybook113-130components in each systemRead the case study →
3. 03The engineering standardAgent-operated delivery behind a written standard of 20 rules and 82 automated checks, with every check carrying a fixture that proves it still fires. I am the only manual gate.buildLinearGitHub ActionsClaude Code20rules in the engineering standardA gate's worth is the cost of what it catches, not the count.20 rules · 82 checks · 10 stagesRead the case study →