Agent skill

Swc Plugin Compatibility

by platformplatform in platformplatform/PlatformPlatform

Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes.

MITAuto-check passed

Install Swc Plugin Compatibility

skills CLI

$ npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install platformplatform/PlatformPlatform swc-plugin-compatibility --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/platformplatform/PlatformPlatform.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/swc-plugin-compatibility .claude/skills/swc-plugin-compatibility && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "swc-plugin-compatibility" agent skill from https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility into .claude/skills/swc-plugin-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swc-plugin-compatibility", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install platformplatform/PlatformPlatform swc-plugin-compatibility --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platformplatform/PlatformPlatform.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/swc-plugin-compatibility .agents/skills/swc-plugin-compatibility && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "swc-plugin-compatibility" agent skill from https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility into .agents/skills/swc-plugin-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swc-plugin-compatibility", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install platformplatform/PlatformPlatform swc-plugin-compatibility --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platformplatform/PlatformPlatform.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/swc-plugin-compatibility .cursor/skills/swc-plugin-compatibility && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "swc-plugin-compatibility" agent skill from https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility into .cursor/skills/swc-plugin-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swc-plugin-compatibility", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/platformplatform/PlatformPlatform.git --path .claude/skills/swc-plugin-compatibility

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install platformplatform/PlatformPlatform swc-plugin-compatibility --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platformplatform/PlatformPlatform.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/swc-plugin-compatibility .gemini/skills/swc-plugin-compatibility && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "swc-plugin-compatibility" agent skill from https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility into .gemini/skills/swc-plugin-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swc-plugin-compatibility", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install platformplatform/PlatformPlatform swc-plugin-compatibility

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/platformplatform/PlatformPlatform.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/swc-plugin-compatibility .github/skills/swc-plugin-compatibility && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "swc-plugin-compatibility" agent skill from https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility into .github/skills/swc-plugin-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swc-plugin-compatibility", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install platformplatform/PlatformPlatform swc-plugin-compatibility --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platformplatform/PlatformPlatform.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/swc-plugin-compatibility .opencode/skills/swc-plugin-compatibility && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "swc-plugin-compatibility" agent skill from https://github.com/platformplatform/PlatformPlatform/tree/main/.claude/skills/swc-plugin-compatibility into .opencode/skills/swc-plugin-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swc-plugin-compatibility", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: swc-plugin-compatibility
GitHub stars: 440
Token cost: ~873 tokens
SKILL.md length: 330 words
Files: 1
Skills in repo: 18
Repo updated: Sep 24, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes.

Works in 3 steps: Check the Compatibility Table → Use the Plugin Compatibility Site → Pin Your Versions
Seeing errors like failed to invoke plugin
SKILL.md covers Why This Happens, How to Fix, Version Compatibility Quick… and Rules to Avoid Build Breakage, plus 4 more sections
Reaches json.schemastore.org

What it does

Swc Plugin Compatibility is an agent skill from platformplatform/PlatformPlatform. Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes. Use when seeing errors like "failed to invoke plugin", "failed to run Wasm plugin transform", "out of bounds memory access", or "LayoutError" during builds with @lingui/swc-plugin.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Next.js and WebAssembly. The repository describes itself as: A platform designed for building enterprise-grade, multi-tenant products using Azure, .NET, React, TypeScript, Infrastructure as Code, etc. The licence is MIT.

When your agent uses it

Seeing errors like failed to invoke plugin
Failed to run Wasm plugin transform
Out of bounds memory access
LayoutError during builds with @lingui/swc-plugin

Example prompts

“failed to invoke plugin”
“failed to run Wasm plugin transform”
“out of bounds memory access”
“/swc-plugin-compatibility”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Check the Compatibility Table
Use the Plugin Compatibility Site
Pin Your Versions

What it can do on your machine

Read from SKILL.md and the folder at commit 269de1c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- json.schemastore.org
Also links to:
- github.com
- plugins.swc.rs
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Swc Plugin Compatibility loads about 873 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 330 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~77
When it runs · the whole SKILL.md, loaded when a task matches: ~873

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from platformplatform/PlatformPlatform at commit 269de1c, republished under its MIT licence (© platformplatform). 330 words, ~873 tokens.

Download SKILL.mdSave it as .claude/skills/swc-plugin-compatibility/SKILL.md (or your agent's skills folder).

name: swc-plugin-compatibility
description: Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes. Use when seeing errors like "failed to invoke plugin", "failed to run Wasm plugin transform", "out of bounds memory access", or "LayoutError" during builds with @lingui/swc-plugin.

SWC Plugin Compatibility

If you see errors like these during your build:

failed to invoke plugin on 'Some("/app/src/file.ts")'
failed to run Wasm plugin transform
RuntimeError: out of bounds memory access
LayoutError called Result::unwrap()

This is NOT a bug. You're using an incompatible version of @lingui/swc-plugin with your SWC runtime.

Why This Happens

SWC plugin support is experimental. The plugin API does not follow semantic versioning.

SWC uses Rkyv to transfer the AST between the core and plugins. Both must agree on the exact memory layout of the AST. If the layout changes (e.g., new ECMAScript features), older plugins cannot read the data correctly.

This layout cannot be negotiated at runtime - it must match at compile time.

How to Fix

Step 1: Check the Compatibility Table

Go to the compatibility table and find the plugin version that matches your runtime.

Step 2: Use the Plugin Compatibility Site

For precise matching, use https://plugins.swc.rs/:

Select your runtime (e.g., next)
Select your runtime version (e.g., next@15.0.1)
Find a compatible @lingui/swc-plugin version

Step 3: Pin Your Versions

json

{
  "devDependencies": {
    "@lingui/swc-plugin": "5.10.0"
  }
}

Use an exact version (no ^ or ~) to prevent accidental upgrades.

Version Compatibility Quick Reference

Plugin Version	@lingui/core	Notes
`5.*`	`@lingui/core@5.*`	Current
`4.*`	`@lingui/core@4.*`	Legacy

Important: @lingui/swc-plugin does not need to match other @lingui/* package versions exactly. It follows its own versioning scheme.

Rules to Avoid Build Breakage

Pin an exact plugin version compatible with your runtime
Don't auto-bump @lingui/swc-plugin - check release notes first
Don't auto-bump your runtime (Next.js, Rspack, etc.) - runtimes may bump swc-core in minor/patch releases
Check compatibility after any upgrade that touches SWC or the plugin

Understanding Runtimes

By "runtime" we mean the tool executing SWC: Next.js, Rspack, or @swc/core.

Some runtimes (like Next.js) embed SWC directly and don't use @swc/core from npm. This means:

You cannot control swc-core version via package.json
Plugin compatibility depends on the runtime's embedded SWC version

Example: Next.js Configuration

// next.config.js
/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    swcPlugins: [
      ['@lingui/swc-plugin', {
        // Plugin options
      }],
    ],
  },
};

module.exports = nextConfig;

Example: .swcrc Configuration

json

{
  "$schema": "https://json.schemastore.org/swcrc",
  "jsc": {
    "experimental": {
      "plugins": [
        ["@lingui/swc-plugin", {}]
      ]
    }
  }
}

What If No Compatible Version Exists?

If your runtime uses a newer swc-core that no plugin version supports yet:

Check for recent plugin releases
Open an issue or PR at https://github.com/lingui/swc-plugin

Files

Just SKILL.md in .claude/skills/swc-plugin-compatibility of platformplatform/PlatformPlatform.

Open the folder on GitHubat commit 269de1c

Compare with similar skills

Swc Plugin Compatibility next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Swc Plugin Compatibility compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Swc Plugin Compatibility this skillplatformplatform/PlatformPlatform	440	—	~873	Automated safety check: Pass	MIT	13 days ago
Dotlottie WebLottieFiles/dotlottie-web	892	—	~3.5k	Automated safety check: Pass	MIT	yesterday
Swc Plugin CompatibilityB0und/WikiSpeedrun	133	—	~2.3k	Automated safety check: Pass	MIT	17 days ago
Vercel Optimize Auditvercel-labs/agent-skills	32k	8 repos	~4.3k	Automated safety check: Pass	None	1 mo ago
AI SDKvercel-labs/ai-facts	168	21 repos	~1.2k	Automated safety check: Pass	None	5 mo ago
Supabase Development and Debuggingsupabase/agent-skills	2.7k	3 repos	~3.6k	Automated safety check: Pass	MIT	5 days ago

Similar skills

Dotlottie Web
LottieFiles/dotlottie-web
Implement Lottie animations using dotLottie runtimes (@lottiefiles/dotlottie-web and @lottiefiles/dotlottie-react).
892 GitHub stars~3.5k tokensUpdated yesterday
Media & CreativeAuto-check passed
Swc Plugin Compatibility
B0und/WikiSpeedrun
Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Vite, Rspack, or other SWC runtimes.
133 GitHub stars~2.3k tokensUpdated 17 days ago
Frontend & DesignAuto-check passed
Vercel Optimize Audit
vercel-labs/agent-skills
Official
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
32k GitHub starsUsed in 8 repos~4.3k tokens
DevOps & CloudAuto-check passed
AI SDK
vercel-labs/ai-facts
Official
Answer questions about the AI SDK and help build AI-powered features.
168 GitHub starsUsed in 21 repos~1.2k tokens
AI & LLM EngineeringAuto-check passed
Supabase Development and Debugging
supabase/agent-skills
Official
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
2.7k GitHub starsUsed in 3 repos~3.6k tokens
Backend & APIsAuto-check passed
Chakra UI v3 Builder
chakra-ui/chakra-ui
Builds responsive, accessible Chakra UI v3 components and layouts, sets up Chakra in new or existing projects, and designs themes with tokens, semantic tokens and recipes.
41k GitHub stars~3.1k tokensUpdated yesterday
Frontend & DesignAuto-check passed

Questions about Swc Plugin Compatibility

What does Swc Plugin Compatibility do?

Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes. Swc Plugin Compatibility is an agent skill from platformplatform/PlatformPlatform.js, Rspack, or other SWC runtimes.

When should I use Swc Plugin Compatibility?

Swc Plugin Compatibility fits situations like: seeing errors like failed to invoke plugin; failed to run Wasm plugin transform; out of bounds memory access; layoutError during builds with @lingui/swc-plugin.

How do I install Swc Plugin Compatibility in Claude Code?

Run `npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a claude-code`. Or copy the skill folder (.claude/skills/swc-plugin-compatibility in platformplatform/PlatformPlatform) into .claude/skills/swc-plugin-compatibility in your project. Claude Code loads it when a task matches its description.

How do I install Swc Plugin Compatibility in Codex?

Run `npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a codex`. Or copy the skill folder (.claude/skills/swc-plugin-compatibility in platformplatform/PlatformPlatform) into .agents/skills/swc-plugin-compatibility in your project. Codex loads it when a task matches its description.

Can I use Swc Plugin Compatibility in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add platformplatform/PlatformPlatform --skill swc-plugin-compatibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swc-plugin-compatibility, .gemini/skills/swc-plugin-compatibility, .github/skills/swc-plugin-compatibility and .opencode/skills/swc-plugin-compatibility in your project.

What does Swc Plugin Compatibility need to run?

SKILL.md names no scripts, command-line tools or credentials: Swc Plugin Compatibility is instructions for the agent only.

Does Swc Plugin Compatibility access the network?

SKILL.md names 3 domains. In commands or code: json.schemastore.org; the agent is likely to contact it when it follows the instructions. As links in the text: github.com and plugins.swc.rs. This is read from the text; nothing was executed.

Is Swc Plugin Compatibility safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Swc Plugin Compatibility use?

Swc Plugin Compatibility is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Swc Plugin Compatibility use?

About 873 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Swc Plugin Compatibility?

Skills that share tags, products or a category with Swc Plugin Compatibility: Dotlottie Web (LottieFiles/dotlottie-web, 892 stars), Swc Plugin Compatibility (B0und/WikiSpeedrun, 133 stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and AI SDK (vercel-labs/ai-facts, 168 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Swc Plugin Compatibility?

platformplatform (a GitHub organization) maintains it in platformplatform/PlatformPlatform, which has 440 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on September 24, 2026.

Source: platformplatform/PlatformPlatform on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Swc Plugin Compatibility

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SWC Plugin Compatibility

Why This Happens

How to Fix

Step 1: Check the Compatibility Table

Step 2: Use the Plugin Compatibility Site

Step 3: Pin Your Versions

Version Compatibility Quick Reference

Rules to Avoid Build Breakage

Understanding Runtimes

Example: Next.js Configuration

Example: .swcrc Configuration

What If No Compatible Version Exists?

Files

Compare with similar skills

Similar skills

More from platformplatform/PlatformPlatform

Related

Questions about Swc Plugin Compatibility