The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
detect, correlate, then decide..
this is the whole philosophy behind REEF Threat Scoring System (v2.0.0).
we dont do simple labeling here. we use weighted bayesian fusion to analyze signals across multiple hypotheses—from drones to simple wifi interference.
the logic is straight...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Spent the weekend building a fun flow for the Paper x Contra challenge. ☀️
I take photos on my walks all the time, but they mostly just sit in my camera roll.
I wanted a way to make something out of them, preferably something I'll be inclined to come back to. I’ve always liked scrapbooks, just never did them digitally.
So, I text photos and a caption to a Telegram bot. An agent picks it up, reads the mood, chooses a layout, adapts it, and uses Paper’s MCP to generate a page. It places the images, adds different stickers and sets a quote!
It then sends it back to me as a finished spread, so I can view it right away.
Currently feeling much more excited about font walks, color walks and daily park walks.
Building small collections as I go! :)
Such a cool build Sara! Great storytelling here too🙌
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
Nice!
What if your team could design, iterate, and deploy entire products without ever leaving a Slack thread?
👉 That's Paper Builder.
It follows your team's conversation, generates the product you're envisioning on Paper, and deploys it on Vercel. Directly in the Slack channel.
From single pages to entire flows, by using your design system.
Just tag Paper Builder in the thread.
Under the hood, a Python server orchestrates three flows:
1. 🔍 The Intent Detection Flow: Claude CLI
- Agent 1 reads the Slack thread and classifies the request as design or deploy.
2. 🎨 The Design Flow: Claude CLI → Paper MCP
- The server checks if a design system folder exists in the project.
- Agent 2 checks if a design system exists on the Paper canvas.
- Agent 3 uses the Paper MCP to build or refine the UI, applying the design system tokens
📝 Paper MCP tools used:
+ get_guide: To load design-specific instructions.
+ get_basic_info: To understand the current canvas state.
+ write_html & update_styles: To create and edit visual elements.
+ get_screenshot: To capture the design for Slack review.
+ finish_working_on_nodes: To finalise the session on Paper.
3. ⚒️ The Deploy Flow: Claude CLI (→ Paper MCP) → React/Vite → Vercel
- Agent 4 exports the artboards as React components and image assets.
- Agent 5 wires the navigation between screens and prepares the app for deployment.
📝 Paper MCP tools used:
+ get_jsx: To transform canvas components into React components.
+ get_computed_styles: To extract exact CSS tokens from the artboards.
+ get_fill_image: To download icons and images for the local bundle.
It's open source, run it yourself and share your feedback:
https://github.com/valeeff/paper_builder_on_slack
Trending
Runway
AI video generation is exploding. What are you dreaming up in Runway?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
portfolioreview
The best portfolios tell a story, not just show a grid. Share yours for feedback.
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?