AI Product Strategy · Agentic Systems · Enterprise UX

Turning complex ideas into useful products.

I help teams make AI, agentic systems and data-intensive products easier to understand, govern, and trust.

Jackie Curry
Select Experience
AI/ML Platform
AI/ML Fraud & Disputes
Clinical Systems
AI Product Design Program
Designing complex enterprise systems

Specialized expertise at the intersection of AI, human judgment, and enterprise systems.

Agentic Workflows

Designing agent builders, execution experiences, tool use, approvals, and autonomy controls.

Learn More →

AI Trust & Governance

Creating transparency, auditability, disclosure, confidence, and oversight across the AI lifecycle.

Learn More →

Enterprise AI Platforms

Building scalable, observable, and human-centered experiences for complex enterprise systems.

Learn More →

From prompt to pull request.

Understanding users, context, and the real problem worth solving still comes first — that part requires human judgment. But once you know what needs to exist and who it's for, this is how I use Claude Code, the Figma MCP, and agent-assisted iteration to move from design intent to reviewed PR. Accurate as of May 2026. AI tooling moves fast and this workflow will keep changing.

01
Groundwork

Open the local repo in your IDE. Connect your design system, project context, and Figma MCP so the agent has access to the actual codebase — not a blank slate.

02
Context before cursor

Ask the agent to read the relevant Figma file or frame. The goal is to understand the existing layout, components, spacing patterns, and design system rules before touching anything. You can also point to an existing file in the codebase instead.

03
Brief the agent

Give the agent a clear brief: what the feature should do, which file to update, where to write the design in Figma, and what should not change.

04
First draft

Let the agent create an initial design direction in Figma. This is a starting point — the value is speed to something reviewable, not perfection on the first output.

05
The Figma session

Review the generated design and make direct adjustments to spacing, hierarchy, layout, copy, and component usage. This is where design judgment comes back into the loop.

06
Closing the loop

Share the revised Figma frame with the agent. The MCP reads your actual design decisions — not just the original prompt — and updates the local codebase from there.

07
Ready to ship

Review locally for visual accuracy, responsiveness, token usage, and accessibility before handing to engineering. Then ask the agent to create a branch, commit the changes, and open a pull request.

Tip

Every file read, tool call, and diff becomes part of the agent's working context — that's not just a prompting habit, it's the cost of operating inside a real codebase. Figma stays in the loop because visual iteration is often faster than another paragraph of instructions.

"Trust is not a feeling. It is a functional state."

I write about what it actually takes to design for AI systems that humans can rely on — accountability, legibility, and the unglamorous work of making complex behavior comprehensible.

Read the Thinking →

Open to the right engagement.

Available for fractional, contract, advisory, and senior IC design work in AI product strategy, agentic UX, and enterprise platform design.

Get in Touch →