Hi, I'm Aman, product designer at EdgeVerve Systems
For the last few years I've worked inside enterprise AI, and I kept seeing the same thing: the design system, accessibility and the AI workflow break together. So I design them together, and build them in working code with Cursor and Claude.
Led a 6-person UX team to unify 12 enterprise products under one 588-token design system with 3 live themes.
How EVDS was builtAudited 385 screens against WCAG 2.2, setting the company's first compliance baseline.
Inside the auditDesigned a 5-stage agentic workflow with a human approval gate before every hand-off.
See Solution StudioThree projects I'm proud of, and the problems that made them worth doing.
Enterprise teams wanted AI to move faster, but nobody wanted an agent shipping changes on its own. I designed a five-stage flow, from Discover to Test, where agents do the heavy lifting and a person approves every hand-off.
Twelve products had quietly drifted into twelve slightly different blues. I architected a four-layer token system and led a 6-person UX team through the migration, bringing everything back to one source with three live themes on top.
Nobody could say how accessible our platform really was, so I went and found out. Two passes, automated then manual, across seven capabilities. It became the company's first compliance baseline.
Things I'm trying on the side to see how AI changes the way I work. Unfinished on purpose.
I built the Solution Studio component library straight from tokens into working code, with Claude pairing on the implementation instead of a hand-off file.
Name tokens the way people talk about them, and the AI gets them right first time.
I handed an agent the WCAG 2.2 checklist and a set of real screens to see how much of a manual audit pass it could carry, and where it falls short.
Agents are quick at contrast and labels. Focus order and meaning still need a person.
I restructured token names, component docs and usage rules so a language model can read the system and generate UI that stays on-brand and accessible.
Docs written for machines turned out clearer for people too.
Bio data page
The most important map I ever ignored was the one telling me to stay in my lane.
In plain terms: more than six years across agencies and enterprise. I started in brand and art direction, moved into product, and since 2022 I've architected the design system and run the first accessibility audit for EdgeVerve's AI Next platform.
I'm happiest where design meets engineering. I prototype in code, write the token docs, and sit with developers until the component in production matches the one in Figma.
I'm most useful to teams working on design systems, accessibility or AI products at enterprise scale. Email is the easiest way to reach me.