skills.rest
Aradotso
AradotsoOFFICIAL
Explore all skills by this author →
Website𝕏@aradotsoGitHub

figma-make-local-runner

Resolve figma:asset imports and normalize version-suffixed packages for local Vite builds.

3|Updated May 16, 2026
Search Tags:#vite#figma make#react typescript#local runner#asset resolution#import troubleshooting#single html build
One-click install
npx skills add https://github.com/Aradotso/design-skills --skill figma-make-local-runner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-make-local-runner
Source: https://github.com/Aradotso/design-skills/tree/main/skills/figma-make-local-runner
Command: npx skills add https://github.com/Aradotso/design-skills --skill figma-make-local-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Figma Make exports often fail or break when you try to run them outside the original environment due to version-suffixed imports and figma asset paths that don’t resolve locally.

Core Features & Use Cases

  • Automatic version specifier removal so imports like @[email protected] can be resolved as a normal package install
  • Custom figma:asset/ resolution that maps figma:asset imports to your local src/assets files
  • Local dev and production builds, including a standalone single-HTML output for sharing or embedding

Quick Start

Tell the AI: “I exported a Figma Make project and want to run it locally with figma:asset imports working—what setup steps should I follow using figma-make-local-runner?”

Frequently Asked Questions about figma-make-local-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Figma Make export locally without asset import errors?▼

To run a Figma Make export locally, you need a setup that maps figma:asset imports to your src/assets directory and strips version specifiers from package imports so Vite can resolve them normally.

Why does Vite fail to resolve @[email protected] imports in Figma Make exports?▼

Vite fails on version-suffixed imports like @[email protected] because they are not standard package specifiers. You must strip the version specifiers during local setup so the imports resolve as normal package installations.

Can I build a Figma Make React TypeScript project into a single HTML file?▼

Yes, you can produce a standalone single HTML file from a Figma Make React TypeScript project by using a Vite-based build workflow that supports the build:single command for sharing or embedding.

What is the best way to fix figma:asset resolution failures in a local development server?▼

The best way to fix figma:asset resolution failures is to configure your local environment to map figma:asset paths directly to your local src/assets files, ensuring the Vite development server starts without import errors.

Do I need to manually modify React TypeScript code exported from Figma Make to run it locally?▼

You do not need to manually modify the exported React TypeScript code. A proper local setup automatically normalizes version-suffixed package imports and resolves figma:asset paths, allowing the Vite dev and build workflows to run unmodified.

Related Skills

Explore More Software Engineering Skills→
kmshihab7878kmshihab7878
6

web-artifacts-builder

Bundle React and TypeScript projects into a single self-contained HTML file.

Community
Advanced
wukangcheng2944wukangcheng2944

artifacts-builder

Bundle React and Vite frontend artifacts into a single inlined HTML file.

Community
Intermediate
futureteafuturetea

Vite Configuration

Generate typed Vite configs for React and TypeScript projects.

Community
Advanced
b33eepb33eep
57

standards-typescript

Enforce TypeScript coding standards across .ts, .tsx, and .jsx files.

Community
Basic