blessed_moon@studio
studio: Blessed Moon Studio
founder: Benito Pedro Xavier · Solo studio
discipline: Strategy · Design · Engineering
stack: Next.js · Tailwind · WebGL
scene: ASCII moon · 5 keyframes
type: Space Grotesk / JetBrains Mono
accent: #ff6a1f
sound: muted
status: ready
B / S / MCASE_21 / 26

— Case study 21

Insta2Figma

Bring Instagram posts into a design canvas as organised image layers

All work
insta2figma.capture● verified
Real Insta2Figma plugin panel showing the mainnet.design profile preview, post count, carousel options, history and favourites tabs

project overview

A design workflow tool with a shared interface for Figma and Framer. It previews an Instagram profile, imports selected posts and carousel images through a queued backend, and places the images into the canvas.

shipped outcome

The repository includes both host adapters, asynchronous imports, history and favourites. The real plugin capture shows profile preview and import controls. Imported images are movable layers; text and graphics inside each post remain raster content.

Role
Plugin UI, backend and import pipeline
Timeline
2026 — Figma and Framer plugin codebase
Year
2026
Team
Solo
The problem01

Collecting social references by hand means downloading images, sorting carousels and arranging them again inside the design file. That repetitive preparation interrupts the design work.

The approach02

A shared plugin UI talks to the host through an adapter. NestJS manages previews, jobs and quotas; BullMQ workers fetch assets and store them in object storage. The Figma plugin groups assets by post and places image-filled rectangles in rows while preserving carousel order.

The result03

The repository includes both host adapters, asynchronous imports, history and favourites. The real plugin capture shows profile preview and import controls. Imported images are movable layers; text and graphics inside each post remain raster content.

— Interface evidence

The product, not a placeholder

These are the verified interface captures from the project build. Scroll inside taller frames to inspect each complete page.

The original plugin capture: import options beside a grid of profile images; no typography reconstruction is shown01 / 01
The original plugin capture: import options beside a grid of profile images; no typography reconstruction is shown

— Delivery process

From operating constraint to shipped system

The work is sequenced around risk. Domain rules and failure states come before interface polish; automation arrives before handoff.

01

Share the interface

Use one React UI and a PluginHost contract for Figma and Framer.

02

Preview before importing

Expose profile results, post ranges and carousel choices before starting a background job.

03

Fetch outside the plugin

The API queues the import while workers collect assets and prepare storage URLs.

04

Place ordered image layers

Group by post, sort carousel slots and place images at their original aspect ratios.

— System architecture

Clear boundaries, explicit responsibilities

Each layer has one job and a narrow contract. That keeps external services replaceable and product behavior testable.

TypeScriptReactFigma Plugin APIFramerNestJSBullMQ / RedisPostgreSQLS3 / MinIO
insta2figma.syssystem schematic

source / selected posts

preview → queue → assets

carousel order preserved

canvas / image layers

  1. shared plugin interface
  2. Figma + Framer adapters
  3. group images by post
  4. place at original ratio

post contents remain raster

Interface

Shared React plugin UI

Preview, import choices, history and favourites share a host-independent component package.

Host bridge

Figma and Framer adapters

Each adapter translates the shared contract into its host’s APIs.

Jobs

NestJS + BullMQ

The API owns job status and quotas; workers collect and upload media.

Assets

Object storage + canvas layers

Signed asset URLs feed image layers grouped by post and carousel position.

— What shipped

Product capabilities

01

Profile preview

Review the source profile and import options before sending work to the queue.

02

Carousel-aware placement

Image slots retain their order and are laid out together by post.

03

Reusable import history

History and favourites persist through the host storage adapter.

— Engineering pressure

Challenges resolved

01

Two hosts, one workflow

Keep plugin behaviour consistent while isolating Figma’s message bridge from Framer’s direct API calls.

02

Partial image failures

Bounded concurrent downloads and per-image error handling let other assets continue when one download fails.

03

Describe what remains editable

The plugin creates image layers, not reconstructed text or vector artwork inside an Instagram post.

verified project destinations

next case studyNetwork Monitor

next transmission

Need a system this deliberate?

Bring the operating problem. We will shape it into a clear product brief and a buildable next step.

Start a project