2 mins read
Every time I handed off a component to a developer, the same question came up. "What are the props for this?" I'd write it in Notion, in comments, in Slack. Never in the one place they were already looking: Figma.
That gap bugged me long enough that I decided to fix it.
PropTable is a Figma plugin that documents component properties right where your components live. No external docs, no copy-pasting. The properties are there, readable, shareable, inside the file.
I had the idea for a while but kept pushing it back. Plugin development felt like a detour from design work. What changed was using AI as a coding partner throughout the build.
I'd describe what I needed. Claude would generate the Figma Plugin API calls. I'd review, tweak, and iterate. The loop was fast. I wasn't writing code from scratch, I was directing it. That's a different skill set and honestly a more natural one for a designer.
The hardest part wasn't the code. It was figuring out exactly what the plugin should and shouldn't do. Scope creep is real even when you're building for yourself.
Shipping a Figma plugin as a designer is very possible in 2025. You don't need to be an engineer. You need a clear problem, a tight scope, and AI tools that let you move fast without getting lost in syntax.
PropTable is live on the Figma Community. If you're tired of writing component docs in three different places, give it a try.