Design compliance work made easier with Cursor + Notion and Figmaβs MCPs
As a product designer, there are some types of work that are important⦠but honestly very heavy to go through manually. One of those, for me, is compliance-related work for specific countries.
At Remote, we are proud to say that we are legally compliant in every country where we operate, and we really care about that. As the designer responsible for the EOR product, part of my job is to go through huge Notion documents and tables, requirement by requirement, reading everything carefully and trying to piece the puzzle together in a way that leads to an intuitive UI for our customers in the end.
What needs to be introduced? What already exists in the current flow? What should be grouped differently? What copy needs to be improved? What should be simplified for users? What is missing? It is one of those tasks where a lot of the effort is not even the design itself, it is just organizing the chaos before the design work can really start. And that is exactly why I decided to test Cursor for this.
Instead of manually going through all the compliance requirements one by one, I wanted help with the heavy lifting of first understanding the new legal structure being proposed, so I could more easily start the design work of introducing the new compliance implications while also using that moment to improve the existing flow.
So I used Notion MCP and let it work through the legal and operations requirements that were already documented there. Honestly, this is where things started to feel really useful, because Cursor was able to read through the requirements in the Notion table and build a form page based on them.
A UI with the fields already translated into something much easier to review. Validations in place. The information grouped in a way that already made a lot more sense than reading everything inside a long document. I even tested further and asked it to group them in a logical order, but there is still room to improve there π
Then today, I saw posts from Cursor engineers and from Figma talking about the newer MCP capabilities, and obviously I had to test them immediately. What caught my attention was the idea that Figmaβs MCP server could bring Figma context into AI workflows, and that these newer workflows could even push rendered UI back into the canvas as editable frames, including in Cursor.
So one of my thoughts was: okay, if Cursor had already helped me structure this long compliance form, letβs see if it could now create that UI in Figma for me. And honestly, it worked really well. With one prompt, Cursor placed the UI I had created exactly where I wanted it in Figma.
...