code-connect-write

A guide for creating a Figma Code Connect file, which links designs in Figma to their Vue component code. It maps design variants and content areas to component props and children.

In plain words
What is it for?
Use it after creating a component when the project has the Figma Code Connect package installed and the component needs a Figma-to-code mapping.
Why use it?
It removes the need to manually explain how a Figma design corresponds to the implementation. The mapping can also provide the code example shown in Figma's developer view.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/aziontech/webkit/code-connect-write
Any agent
npx skills add aziontech/webkit --skill code-connect-write
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 851 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.00851
Opus 5 $0.00016 $0.00426
Sonnet 5 $0.00006 $0.00170
Haiku 4.5 $0.00003 $0.00085

Measured yesterday against content hash 68d87e7b07c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-connect-write scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/code-connect-write/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: code-connect-write

Purpose

Map Figma variants (kind / size / state) → Vue props, Figma slots → Vue children, and emit the snippet Dev Mode shows in the Figma file. The file lives next to the .vue at packages/webkit/src/components/webkit/<category>/<name>/<name>.figma.ts.

When to invoke

  • Step 6 of /component-create, after the scaffolder and storybook-write succeeded.

Inputs

  • The full text of .specs/<name>.md (Props, Events, Slots, States).
  • The spec's figma.node_id (frontmatter).
  • The orchestrator's confirmation that @figma/code-connect is installed (check packages/webkit/package.json).

Workflow

  1. Pre-flight. If @figma/code-connect is not in packages/webkit/package.json devDependencies, emit SKIPPED: @figma/code-connect not installed and exit. The orchestrator records this as a pending item.

  2. Load prerequisite skill. Invoke figma:figma-code-connect (mandatory before any Code Connect tool call).

  3. Write <name>.figma.ts using this skeleton (substitute spec values):

    import { figma } from '@figma/code-connect'
    import <PascalName> from './<name>.vue'
    
    figma.connect(<PascalName>, '<figma.url>', {
      props: {
        kind: figma.enum('kind', {
          primary: 'primary',
          secondary: 'secondary',
          outlined: 'outlined',
          text: 'text'
        }),
        size: figma.enum('size', {
          small: 'small',
          medium: 'medium',
          large: 'large'
        }),
        disabled: figma.boolean('disabled'),
        label: figma.children('label')
      },
      example: (props) => /* html */ `
        <${'<PascalName>'} :kind="${'${props.kind}'}" :size="${'${props.size}'}" :disabled="${'${props.disabled}'}">
          ${'${props.label}'}
        </${'<PascalName>'}>
      `
    })
    
  4. Stop. Do not call add_code_connect_map, do not call send_code_connect_mappings, do not publish anything. Publishing requires FIGMA_ACCESS_TOKEN and is the user's call.

Outputs

Read the full file on GitHub · 83 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 83 lines · 32 tokens per session scan A 68d87e7b07c6

Subscribe to this mod's changes

code-connect-write is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 851 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

monorepo-management

Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.

soulcodex/agentic · 63 tokens

bazel-monorepo-expert

Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.

kinhluan/rules-quarkus-skills · 43 tokens

pnpm

Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.

pledgeandgrow/pledge-skills · 31 tokens

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens

port-sacred-terminal-ui-to-typescript-cli

Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.

internet-development/www-sacred · 0 tokens

port-sacred-terminal-ui-to-react-using-same-conventions

Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…

internet-development/www-sacred · 0 tokens