AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Figma Context Reader

skill-sergekostenchuk-ui-ux-agent-skill-system-figma-context-reader · by sergekostenchuk

Read and summarize Figma design context for UI/UX implementation, audit, and design-system work. Use this skill when the user provides a Figma URL, selected Figma node, frame, component, Dev Mode context, variables, library, or screenshot and wants structured facts about hierarchy, layout, tokens, components, assets, variants, interaction notes, or implementation constraints without mutating the…

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-sergekostenchuk-ui-ux-agent-skill-system-figma-context-reader

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-sergekostenchuk-ui-ux-agent-skill-system-figma-context-reader)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Figma Context Reader? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Figma Context Reader

Use this skill to turn Figma context into an evidence-backed design brief. This is a read-only skill; route mutations to figma-canvas-editor or figma-design-system-sync.

Modes

  • frame-brief: summarize a selected frame or page.
  • component-brief: summarize components, variants, props, and constraints.
  • token-brief: summarize variables, styles, color roles, spacing, radius, typography, and effects.
  • audit-input: collect enough Figma evidence for ux-audit-skill or design-critic-skill.
  • handoff: prepare context for implementation specialists.

Workflow

  1. Confirm the input type: Figma URL, selected node, file key, screenshot/export, or connected MCP selection.
  2. Apply ../../shared/privacy-policy.md.
  3. If a use_figma call is needed, first invoke the installed figma:figma-use skill.
  4. Read only the needed nodes, variables, components, styles, and assets. Avoid broad file scans unless the user asks for library/system work.
  5. Produce a structured context brief with evidence labels. Distinguish direct Figma metadata from visual inference.
  6. If MCP access is unavailable, ask for an export, screenshot, node metadata, or manual Figma details as fallback.

Output Shape

Use [assets/context-brief-template.md](assets/context-brief-template.md).

Evidence Rules

  • Figma metadata: node names, type, layout fields, variables, styles, component names, asset references.
  • Visual inference: hierarchy, attention, density, likely intent, visual polish.
  • Missing: anything not available from the current Figma context.

Do not claim DOM, runtime behavior, accessibility scan, or implementation evidence from Figma context alone.

Validation And Eval

  • Check that the final brief names the evidence source and privacy mode.
  • Check that every implementation claim is traceable to Figma metadata, visual inference, or an explicit missing-context note.
  • Use evals/evals.json for forward tests that distinguish connected Figma context from screenshot-only input.

Resources

  • Read $CODEX_SKILLS_DIR/senior-figma-orchestrator/references/figma-mcp-compatibility.md when tool availability is unclear.
  • Use [assets/context-brief-template.md](assets/context-brief-template.md) for reports.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.