The Claude Code Engineer's Playbook: Remote Control, Scheduled Tasks, and Figma

Step 1: Log in if you have not already

Step 2: Set workspace trust

Step 3: Start a Remote Control session

Step 4: Connect from your phone

Step 5 (optional): Enable Remote Control for every session automatically

One remote connection per session.

**Terminal must stay open. **

**Laptop must stay on. **

Network timeout.

**You cannot start new sessions remotely. **

**Do not share your session URL or QR code with anyone while the session is active. **

**Your session makes outbound HTTPS requests only. **

Workflow 1: Live Signal to Outreach Intelligence

Workflow 2: Parallel Account Research

Workflow 3: Daily Market Brief on a Schedule

What Stays Available Remotely

Daily Inbox Organisation

Instructions to paste:

"Scan the Inbox folder. Move every file into the relevant document folder based on content type. Create a Markdown report in the Reports folder listing every file moved, where it went, and why."

Frequency: Daily

Daily AI Trend Report

Instructions to paste:

"Search the web and X for the latest news about AI productivity from the past 24 hours relevant to our business. Create a written report with the top findings saved to the Reports folder."

Frequency: Daily

The Team Use Case

The Team Use Case

The Key Principle

The more context Claude has in the folder, the better every scheduled task performs. A CLAUDE.md file with your business, your team, your ICP, and your processes means every task runs with the full picture every single time.

What you need installed first

1. Claude Code CLI - run claude in any project folder. If you see a welcome message it's working
2. Figma MCP server - run the install command. It'll tell you if it's already installed
3. Claude Code plugin for Figma - copy the install command from the plugin page and run it once

Flow 1: Claude Code → Figma

Use when you've built something in code and want it in a design file.

1. Build your file in Claude Code (HTML or React both work)
2. Open your Figma file and clear the canvas
3. Copy the file link with Command L
4. Paste the link into Claude Code and tell it to send the design to Figma
5. Claude pushes it directly - layout appears in Figma with auto layout applied

Output comes through with sidebar, cards, and layout blocks in auto layout. Not fully responsive out of the box but structurally clean and editable.

Flow 2: Figma → Claude Code

Use when you've made visual edits in Figma and want them reflected in live code.

1. Make your changes in Figma (move elements, adjust padding, restructure)
2. Go back to Claude Code and type: "implement the changes I've done here to the live code"
3. Claude screenshots the Figma file, reads the diff, updates the code

Most changes apply correctly. Complex repositioning (icons, nested elements) can occasionally misalign - just ask Claude to fix specific elements if anything breaks.

Flow 3: Generate components directly in Figma

Use when you want Figma components without touching code first.

1. Open the Claude design assistant plugin inside Figma
2. Add your Anthropic API key in the plugin settings
3. Tell Claude what to build: "create a primary button with small, medium, and large size variants"

One prompt, everything at once. Ask for all variants in a single message rather than one at a time - iterating one by one produces duplicate components.

One tip worth noting

Run Claude Code with --dangerously-skip-permissions when working in a trusted local environment to skip permission prompts mid-session.