This Figma Plugin Changed How I Read API Docs

I noticed something that kept happening, over and over again. It made me curious... so I built a solution. After spending nearly a decade as a Software Engineer, I observed two major — and often overlooked — challenges in modern product teams: 1. The endless back-and-forth between frontend and backend developers "Which API endpoint powers this screen?" That question alone can create hours of confusion. It only gets worse as the number of endpoints grows, and even worse when new team members come on board. 2. Backend developers have no visual representation of their work Designers have prototypes. Frontend devs have interfaces. But backend engineers? We're stuck with Swagger docs — hundreds of endpoints, technical jargon, and very little context for the rest of the team. I saw this pain firsthand while working at several organizations. On one project, we had over 300 endpoints and multiple frontend engineers trying to collaborate in real-time. One weekend at Learngual, I decided to do something about it. I built a Google Sheet that mapped screenshots of Figma screens to their respective API endpoints. It worked. It saved time. It made collaboration effortless. That sparked a question: What if there were a native tool that did this — elegantly and at scale? And that’s how Skeema was born.

Apr 24, 2025 - 10:39

This Figma Plugin Changed How I Read API Docs

I noticed something that kept happening, over and over again.

It made me curious... so I built a solution.

After spending nearly a decade as a Software Engineer, I observed two major — and often overlooked — challenges in modern product teams:

1. The endless back-and-forth between frontend and backend developers

"Which API endpoint powers this screen?"

That question alone can create hours of confusion.

It only gets worse as the number of endpoints grows, and even worse when new team members come on board.

2. Backend developers have no visual representation of their work

Designers have prototypes.

Frontend devs have interfaces.

But backend engineers? We're stuck with Swagger docs — hundreds of endpoints, technical jargon, and very little context for the rest of the team.

I saw this pain firsthand while working at several organizations.

On one project, we had over 300 endpoints and multiple frontend engineers trying to collaborate in real-time.

One weekend at Learngual, I decided to do something about it.

I built a Google Sheet that mapped screenshots of Figma screens to their respective API endpoints.

It worked.

It saved time.

It made collaboration effortless.

That sparked a question:

What if there were a native tool that did this — elegantly and at scale?

And that’s how Skeema was born.