What are you trying to do? (please be as specific as possible and include relevant screenshots, code snippets, and reproduction steps)
What have you tried so far? (please link relevant docs and other forum posts)
Relevant links:
https://studio.plasmic.app/projects/3zksFc5MTESFcbaSe2C3mD/-/Homepage?arena_type=page&arena=nqbpmNAItrYb
As a valued customer who is keenly interested in your products, I must express my deep frustration. I have been attempting to register my style tokens from my IDE following your provided documentation, but to no avail. The Cursor AI with the Sonnet 3.5 agent, the Replit agent using full stack JavaScript, Bolt.new with StackBlitz, and V0.dev with Vercel all failed to accomplish this task. These are robust tools that I utilised specifically in accordance with your published guidelines.
I have successfully exported my Figma design styles, tokens, colours, etc., using the “Design Tokens” plugin, and saved them as a JSON file as instructed. However, despite confirming my authentication, project ID, and project API, none of these tools are able to register under the style tokens tab. I have also included a summary from Cursor that I generated for your reference.
I kindly request your assistance in resolving this matter at your earliest convenience. Thank you. I tried to attach the JSON file too but it would not let me upload.
"Here’s a detailed summary of everything we tried and what went wrong:
First Attempt - Style Dictionary For
{
“props”: {
“font-family-amatic”: {
“type”: “string”,
“value”: “Amatic SC”,
“category”: “fontFamily”
}
}
}
Used the Style Dictionary format with props structure
Issue: Tokens didn’t appear in Plasmic Studio
Configuration used “scheme”: “theo”
Second Attempt - Theo Format
{
“global”: {
“type”: “typography”,
“category”: “typography”,
“typography”: {
“title”: {
“value”: {
“fontFamily”: “Amatic SC”
}
}
}
}
}
Tried using Theo format with nested typography structure
Issue: Still no tokens appearing in Plasmic Studio
Configuration remained with “scheme”: “theo”
Third Attempt - Project-Specific Configuration
Created plasmic/website/plasmic.tokens.json
Created plasmic/website/plasmic.config.json
Tried to scope tokens to the Website project
Issue: CLI sync errors and tokens still not appearing
Fourth Attempt - Simplified Structure
{
“black”: {
“value”: “#000000”,
“type”: “color”
}
}
- Tried using Plasmic’s API format
Attempted direct API upload
Issue: Got CSRF token errors
Technical Issues Encountered:
CLI Problems:
Version compatibility issues
Cannot read properties of undefined (reading ‘forEach’)
Migration errors with plasmic.json
Permission Issues:
npm cache permission problems
Global installation permission errors
Required multiple sudo attempts
Configuration Issues:
Multiple competing token file locations
Confusion between global and project-specific token configurations
Schema version mismatches
API Issues:
CSRF token errors when trying direct API upload
Authentication problems with API endpoints
File Location Attempts:
- Root directory: plasmic-tokens.theo.json
Project directory: plasmic/website/tokens.json - Root directory: tokens.json
- Root directory: design-tokens.json
Configuration Changes:
Started with:
“tokens”: {
“scheme”: “theo”,
“tokensFilePath”: “plasmic-tokens.theo.json”
}
Changed to:
“tokens”: {
“scheme”: “style-dictionary”,
“tokensFilePath”: “tokens.json”
}
Finally tried:
“tokens”: {
“scheme”: “plasmic-api”,
“tokensFilePath”: “design-tokens.json”
}
Root Causes:
Unclear documentation about the exact token format required
CLI tool instability
Permission issues with npm global installations
Possible version mismatches between CLI and Plasmic Studio
Confusion between different token schemes (Theo vs Style Dictionary vs API)