Since I have been using the challenges to learn, things sometimes working on submission get really messy Which this submission did become a hot mess for me. Probably pushed Fuser in a way that will be unexpected for the Fuser team lol. Of course, I learned a lot from this challenge and as I move forward.

So, for my first submission, I was aiming to create a start up ramp up system, to quickly iterate on product mock ups and promotional material. So a little bit of branding, product mock up, and ad campaign all in one. I did this using a fictional startup concept I created based on how food cooking videos on social media make me feel after watching them. Product mock ups being the websites and apps possible design concepts.

I still need to work on my prompting skills because I was burning through the credits more than I liked. 😂 On top of the fact that I am someone who likes to rerun things until I like what I see. So I eventually nipped things in the bud at a certain point to try a new concept with the remaining credits, to see if I can do the next one better.

Link: Find My Cravings https://app.fuser.studio/view/c997774f-034f-403e-aff0-aa33ab8bbd3b

I love the mindset of using challenges as a way of learning new tools!

One Shot Campaign Emails using Paper and Resend

I've been building websites and digital products for years. And one thing that never got easier? Creating email templates.

Here's what the old process looked like:

→ Design in Figma (or wherever) → Export every image manually → Upload to S3/R2/wherever — remembering the folder structure, the naming conventions → Copy public URLs back into code → Write the HTML by hand, or fight an email builder → Load Google Fonts correctly (or watch them break in Outlook) → Test it. Fix it. Test it again. Cry. → See your therapist. Cry. → Finally get it into your ESP

That's not a workflow. That's a tax on creativity.

So I built something different using Paper's connected canvas.

The new flow:

1. Design the email inside Paper — layout, content, images, all of it

2. Cursor reads the design through the Paper MCP

3. Images are automatically pushed to a Cloudflare R2 bucket via the Cloudflare MCP

4. The Resend template is created via the Resend MCP — Google Fonts loaded, inline styles correct, pixel-perfect to the design

5. Done.

One canvas. Three MCPs. Zero manual handoffs.

This is what I think "agentic design" actually means — not AI generating something from a vague prompt, but a connected canvas where your tools talk to each other and the heavy lifting just... disappears.

Huge thanks to the Paper team for building the infrastructure that makes this possible. Excited to see where this goes.

Full walkthrough in the video below. Twitter Post LinkedIn Post