Skill

interop

Use when the task involves Rust/TS type sharing, WASM/TS bridges, Tauri boundaries, generated contracts, or TypeScript-facing cross-language ownership questions.

Install

npx claudepluginhub joysusy/violet-plugin-place --plugin typescript-coding-engine

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This bridge skill routes TypeScript work into the canonical interop lane.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

MCP Integration

6 files

Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.

plugin-dev

83.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

TypeScript Interop

Purpose

This bridge skill routes TypeScript work into the canonical interop lane.

Use it when the task is about:

Rust-generated or Rust-owned contracts consumed in TS

Tauri frontend↔Rust core IPC boundaries

WASM or generated binding consumption from TypeScript

contract drift, generated artifact alignment, or boundary ownership

deciding whether the real owner is TypeScript interop, Rust interop, or runtime validation

Reading Path

Read ../../SKILL.md for the engine boundary.

Read ../../references/interop/INDEX.md.

Read ../../references/interop/boundary-activation-model.md.

Read ../../references/interop/rust-typescript-contract-boundaries.md.

If the bridge is desktop or Tauri-facing, also read ../../references/interop/tauri-frontend-rust-bridge.md.

If the contract source is clearly Rust-owned, inspect the Rust-side doctrine next only after ownership is explicit.

Use ../../agents/interop-reviewer.md only when bounded review adds leverage.

Pressure Classification

Classify the interop pressure first:

contract ownership

generated artifact drift

Tauri or IPC boundary

WASM consumer boundary

TS-side runtime validation at the interop edge

build/import alignment

Output Contract

Return:

primary interop lane

structural truth owner

main contract or boundary risk

whether TS-side runtime validation is also needed

the next exact doctrine file to read

Core Rule

Interop is a contract-discipline problem, not just a packaging problem. Keep TypeScript-side convenience aligned with backend or bridge truth, and resolve ownership before implementation moves begin.

TypeScript Interop

Purpose

This bridge skill routes TypeScript work into the canonical interop lane.

Use it when the task is about:

Rust-generated or Rust-owned contracts consumed in TS
Tauri frontend↔Rust core IPC boundaries
WASM or generated binding consumption from TypeScript
contract drift, generated artifact alignment, or boundary ownership
deciding whether the real owner is TypeScript interop, Rust interop, or runtime validation

Reading Path

Read ../../SKILL.md for the engine boundary.
Read ../../references/interop/INDEX.md.
Read ../../references/interop/boundary-activation-model.md.
Read ../../references/interop/rust-typescript-contract-boundaries.md.
If the bridge is desktop or Tauri-facing, also read ../../references/interop/tauri-frontend-rust-bridge.md.
If the contract source is clearly Rust-owned, inspect the Rust-side doctrine next only after ownership is explicit.
Use ../../agents/interop-reviewer.md only when bounded review adds leverage.

Pressure Classification

Classify the interop pressure first:

contract ownership
generated artifact drift
Tauri or IPC boundary
WASM consumer boundary
TS-side runtime validation at the interop edge
build/import alignment

Output Contract

Return:

primary interop lane
structural truth owner
main contract or boundary risk
whether TS-side runtime validation is also needed
the next exact doctrine file to read

Core Rule

Interop is a contract-discipline problem, not just a packaging problem. Keep TypeScript-side convenience aligned with backend or bridge truth, and resolve ownership before implementation moves begin.