Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Figma configuration per environment v1.0.0

Use this resource to isolate Figma access between development, staging and production

New

  • 518 downloads
  • 133 likes
  • 237 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install figma-environment-token-isolation

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent defines an environment strategy with least-privilege tokens, separate files and environment file templates. It adds guards so a development operation cannot touch production files. You get a documented secret management setup.

Mostly picked by

Updated November 2, 2026

Card for the “Figma configuration per environment” skill

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: environment strategy and rights table per environment
  • references/environment-guards.md: checks that block operations outside their environment

Good fit for

  • Your team uses the same Figma token everywhere
  • You have a test Figma file separate from the production file

Not for

    Tags

    • figma
    • environments
    • secrets
    • configuration

    About

    You say

    “Separate the Figma tokens for development and production, and add a guard in the code.”

    Card for the “Figma configuration per environment” skill

    Skill published by Jeremy Longshore <jeremy@intentsolutions.io> under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to isolate Figma access between development, staging and production
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1.1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • references/configuration-by-environment.md1.5 KB
    • references/environment-files.md0.8 KB
    • references/environment-guards.md1.2 KB
    • references/errors.md0.7 KB
    • references/secret-management.md0.8 KB
    • SKILL.md6.3 KB

    Origin and licence

    Listed unmodified

    Author
    Jeremy Longshore <jeremy@intentsolutions.io>
    Source
    github.com/jeremylongshore/tons-of-skills-marketplace/tree/ab85a061f7bcc039dac13ee193de7a4cd4388571/skills/.curated/figma-multi-env-setup
    Licence
    MIT

    Notice

    « figma-multi-env-setup » (Jeremy Longshore <jeremy@intentsolutions.io>, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.