Frontend platforms / design systems / AI-assisted development
Connor Dibble
Senior Software Engineer / Digital Experience Platform Lead
Frontend architecture / design systems / technical direction
Prototype → platform
A prototype is only the first proof.
The rest is contract, review, checks, release, adoption, and feedback. Select a stage to see what makes an idea dependable.
01 / Prototype
Make the idea tangible.
A working demo makes the question visible. It is a starting point, not a promise.
CAPABILITY PROPOSAL
One useful behavior
Evidence from DesignRail, the SFDS developer platform, and the convention feedback pilot.
Selected work
Platform work, design systems, and developer tools.
Platform lead
SFDS Developer Platform
State Farm, closed source
- Tokens
- Components
- Release
Developer platform for component contracts, documentation, migration guidance, release policy, and delivery to 1000+ engineers and designers.
- Web Components
- TypeScript
- Design Tokens
- npm + CDN
Selected work
DesignRail
Open source
- Intent
- Review
- Export
Review step for design-to-code workflows. It maps component intent, surfaces findings, and requires a decision before export.
- Developer Tools
- React
- TypeScript
Selected work
dibble
Open source
- Trust
- Guide
- Verify
11 portable plugins for carrying shared engineering rules between Claude and GPT, with deterministic checks in hooks, CLI, and CI.
- Agent Skills
- CLI
- Codex
Experience
Senior Software Engineer, Digital Experience Platform Lead
State Farm / Mar 2026 – Present
Internal title: Senior Technology Engineer
Set frontend direction across 8 product teams and 50+ engineers. Lead platform work across statefarm.com and build AI-assisted development tools with live docs, deterministic checks, and human review.
Lead Software Engineer I → II, State Farm Design System (SFDS)
State Farm / May 2023 – Mar 2026
Built sf-ui, a Lit and Web Components platform with 70+ accessible primitives used by 1000+ engineers and designers. Owned documentation, delivery, release policy, and adoption.
Software Engineer, Drive Safe & Save Telematics
State Farm / May 2020 – May 2023
Built Node.js Lambda APIs and Java services for Drive Safe & Save enrollment. Led frontend direction across React apps and micro-frontends.
Success Was the Incident
June 2026 · 10 min read
Adoption turned a five-minute browser cache into a budget problem. Splitting it into three caches with three owners, hashing dependencies behind stable component files, and a finops partnership cut request volume to a third of its peak.
From Snippets to Shadow DOM
June 2026 · 13 min read
Why a jQuery-era design system splintered into forks and customized local versions, how Shadow DOM moved governance into the component boundary, and what it took to earn adoption from a thousand engineers.
Teaching AI Agents to Use a Design System
May 2026 · 9 min read
A practical look at constraining AI-generated frontend code with design-system primitives, agent instructions, and repeatable validation.
About
At State Farm, I set frontend direction across 8 product teams and 50+ engineers. SFDS is the shared platform for 100+ product teams and 1,000+ engineers and designers.
I build the tools and standards other teams inherit: components, documentation, release checks, and AI-assisted workflows. Open source and Proceris keep me close to product discovery and implementation.
Tools
- Frontend
- TypeScript · React · Lit / Web Components · Microfrontends · Accessibility
- AI + tooling
- Developer platforms · Agent skills · MCP · Deterministic checks · Figma-to-code
- APIs + delivery
- Node.js · Java · GraphQL · AWS · CI/CD
- Systems
- Design systems · Design tokens · Documentation · Release governance · Observability