mcpField
F
figma-workflow-auditor

figma-workflow-auditor

github.com/sergekostenchukTesting & quality3252 installsUpdated 18w ago
Repository

About figma-workflow-auditor

figma-workflow-auditor is a skill for reviewing Figma-related workflows, claims, and evidence. It helps teams identify capability, privacy, routing, and implementation issues without changing Figma files.

Key features

  1. 01Capability and tool-availability audits
  2. 02Privacy and data-transfer checks
  3. 03Evidence checks for reads and writes
  4. 04Figma specialist routing review
  5. 05Figma skill draft review

Use cases

  1. 01Validate a Figma workflow before handoff
  2. 02Check evidence behind claimed file changes
  3. 03Review a plan for privacy gaps

MCP support

It audits claims about Figma MCP and tool availability, requiring session evidence for capability and mutation claims.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-workflow-auditor

After installing, type/figma-workflow-auditorin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
assets/
audit-report-template.md
evals/
evals.json

Details

From the project README

Figma Workflow Auditor

Use this skill as the quality gate for Figma-related workflows. It does not mutate Figma files.

Modes

  • capability-audit: verify claims against current Figma MCP/tool availability.
  • privacy-audit: check whether data transfer and permissions are acceptable.
  • evidence-audit: check whether claimed reads/writes/exports actually ran.
  • routing-audit: check whether the right Figma specialist was selected.
  • skill-audit: review a Figma skill draft or existing skill.

Workflow

  1. Identify the workflow under review: prompt, plan, skill, transcript, report, or file change.
  2. Check official/current sources when capability details may have changed.
  3. Verify tool evidence: tool response, metadata readback, screenshot/export, local diff, or report artifact.
  4. Flag overclaims separately from implementation bugs.
  5. Return findings ordered by severity, with concrete fixes.

Findings Format

Use assets/audit-report-template.md.

Audit Rules

  • A Figma MCP claim is weak if it lacks session tool availability and evidence.
  • A mutation claim is invalid without a target, scope, executed tool, and readback.
  • A privacy plan is weak if it omits what data is sent to Figma or another service.
  • A design-to-code plan is weak if it skips local component inspection and visual verification.
  • An effects plan is weak if it treats NOISE, TEXTURE, GLASS, or progressive blur as universally available without runtime checks.

Comments

Markdown supported