How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-workflow-auditorBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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
- Identify the workflow under review: prompt, plan, skill, transcript, report, or file change.
- Check official/current sources when capability details may have changed.
- Verify tool evidence: tool response, metadata readback, screenshot/export, local diff, or report artifact.
- Flag overclaims separately from implementation bugs.
- 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.
