Succession.Media Operator Onboarding

Publishing System · for Hamid

Your Figma pages,
live in one line.

Design a landing page in Figma. Ship it as a real website on its own client subdomain. No code, no servers, no waiting.

Figma frame→ one command→ https://client.succession.media
00

How it works

You work entirely through your Claude Code. You tell it what to publish in plain language, it runs one command on the Succession server, and the page goes live with HTTPS. Figma stays your single source of truth: to change a page, edit the frame and publish again.

◆ Omar will send you one private file, hamid-deploy, over a secure channel. It is your key to the server. Keep it private, never paste it into chat. The setup below tells your Claude Code where to put it.
01

One-time setup

Do this once. Hand these blocks to your Claude Code and it will wire everything up.

i

Install your key

Save the hamid-deploy file Omar sent you to ~/.ssh/hamid-deploy, lock its permissions, and add the server to your SSH config.

chmod 600 ~/.ssh/hamid-deploy

# add this to ~/.ssh/config
Host succ-lp
    HostName 18.246.162.246
    User deploy
    IdentityFile ~/.ssh/hamid-deploy
    IdentitiesOnly yes
ii

Set your Figma token

In Figma: avatar, then Settings, then Security, then Personal access tokens. Generate a new token with scope File content: Read-only. Then register it on the server (it stays in your own account there, nobody else can read it):

$ ssh succ-lp 'succ-deploy set-token figd_your_token_here'

It prints your Figma account name on success. Re-run anytime to rotate.

iii

Test the connection

Confirm your Claude Code can reach the server.

$ ssh succ-lp 'echo connected'
02

Publish a landing page

The everyday flow. One client at a time, each on its own subdomain.

i

Copy the Figma frame link

In Figma, right-click the frame you want to publish, then choose Copy link to selection. The link must contain node-id.

ii

Tell your Claude Code to publish

Pick a short client name (lowercase, hyphens, no spaces). That becomes the subdomain.

$ ssh succ-lp 'succ-deploy acme-skincare "<figma-frame-link>"'

Result: https://acme-skincare.succession.media

iii

New client? Ask Omar for the subdomain once

The first time you use a new client name, message Omar:

◆ "Point acme-skincare.succession.media to the LP server." He adds one DNS record. After it resolves, run the publish command. HTTPS is issued automatically on that first publish. Re-publishing the same client never needs this step.
03

Editing and fixes

→

To change a page

Edit the frame in Figma, then run the exact same publish command again. It rebuilds and republishes.

→

If a page looks off

Add a render flag at the end. svg gives a pixel-perfect snapshot of the design, html forces the editable web build.

$ ssh succ-lp 'succ-deploy acme-skincare "<link>" --render=svg'
04

House rules

  • The only thing you run is the succ-deploy command. Never edit the server or other clients' files.
  • No em dashes or en dashes in any copy. Use commas, periods, or colons.
  • If a publish throws an error, send the full error text to Omar. Do not try to fix the server yourself.
  • Your key and your Figma token are yours. Keep them private.