sergekostenchuk/ui-ux-agent-skill-system

figma-workflow-auditor

Audit Figma MCP, design-to-code, code-to-canvas, canvas-editing, and design-system workflows for correctness, freshness, privacy, evidence, and routing quality.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-workflow-auditor

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

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.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
sergekostenchuk
Community

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

installazioni
1
GitHub Stars
32
Aggiornato
13 set
sergekostenchuk
Community

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

installazioni
1
GitHub Stars
32
Aggiornato
13 set
sergekostenchuk
Community

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

installazioni
1
GitHub Stars
32
Aggiornato
13 set
sergekostenchuk
Community

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

installazioni
1
GitHub Stars
32
Aggiornato
13 set