Your API server has no business touching uploaded file bytes. Presigned URLs let the browser PUT

Your API server has no business touching uploaded file bytes. Presigned URLs let the browser PUTYour API server has no business touching uploaded file bytes. Presigned URLs let the browser PUT

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

Dusko Licanin

pro

• Jun 25

Your API server has no business touching uploaded file bytes.

Presigned URLs let the browser PUT straight to S3; the server only signs the request. Files pass through three buckets (raw, scanned, clean) so ClamAV clears them before download, and each tenant gets its own prefix.

Step-by-step in the post: https://www.duskolicanin.com/blog/saas-file-upload-direct-s3-presigned-2026

Next.js TypeScript

Pedro AGB

pro

• Jun 21

Working on an AI content calendar SaaS concept.

Less planning. More publishing.

Which direction do you prefer? 👇

Framer Website Design Framer

20 voted

56%

16 voted

44%

36 votes

Closed

Sajid Ali

• Jun 21

Split layout for me.

In SaaS landing page design, users often decide within seconds whether a product is relevant. Showing part of the product experience alongside the value proposition helps communicate functionality, usability, and credibility much faster.

Natalia Trusova

• Jun 21

Title: I built a design system generator inside Figma Make. Here's the workflow.

The problem I kept running into: every new client project meant re-explaining the brand to every AI tool from scratch. Figma Make didn't know the colors. Cursor didn't know the tokens. Claude didn't know the rules. I was the shared memory — and I kept losing things.

So I built Design System Gen. Entirely inside Figma Make. Powered by Claude API.

The workflow:

Upload brand references → Claude API analyzes them across 8 dimensions (palette, mood, typography, composition, lighting, texture, motion, UI DNA) → structured data, not vibes → generates 11 files, each formatted for a specific tool in your stack.

figma-make.md → paste once, Figma Make knows your entire design system design-system.css → all tokens as CSS custom properties tokens.json → W3C format, imports directly into Figma Variables starter.tsx → React starter with tokens already bound .cursorrules → Cursor knows your system from root Claude.md → Claude reads it automatically every session + 5 more for docs, LLMs, prompts, components

Every tool gets its own context file. All consistent with each other.

The part I'm most proud of: I'm a designer. I don't write code. The entire tool — UI, API integration, file generation logic — was built and shipped inside Figma Make. No external hosting. No separate codebase.

Live at: vibecodingdsgen.figma.site

Add your Claude API key and try it with your own moodboard.

#FigmaMake #DesignSystem #VibeCoding #AI #Claude #UXUI #DesignSystems #ConfigMakeathon

UX Design AI Engineer Claude Figma

Rada Hnedova

• Jun 22

As someone who constantly jumps between Figma, Claude, ChatGPT, Cursor, Lovable, and other AI tools, this problem feels very familiar 😅

The tools are getting smarter, but keeping context consistent is still surprisingly manual. Love seeing people tackle that gap.

Alex Prokhorov

max

• Jun 20

Still can't believe this is fully native. With the Framer 3.0 update I rebuilt this viral landing page using Opus 4.8. The result is insane. Edit every layer on the canvas or just ask Claude Check it live https://lumio.framer.media/

Framer Claude Web Design