figma-slop-check
Review the craft and technical precision of a requested Figma scope with project canon, measures and visual evidence; classify swap/snap/ask while respecting existing correction authorization.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- figma-slop-check
- license
- MIT
- metadata
- { "author": "Thiago Xikota", "version": "1.2.0" }
- description
- Review the craft and technical precision of a requested Figma scope with project canon, measures and visual evidence; classify swap/snap/ask while respecting existing correction authorization.
- compatibility
- Read-only. Checks are written for figma-console-mcp tools (figma_execute, figma_get_variables, figma_capture_screenshot) with the Desktop Bridge plugin running in Figma Desktop. The official Figma MCP server's use_figma also runs Plugin API JavaScript, but this skill was not validated there. Reads the figma-canon skill.
02 资源文件 3
- 参考文档references/checks.md11.8 KB
- 参考文档references/punch-list.md7.1 KB
- 参考文档references/slop-lens.md7.3 KB
03 SKILL.md 正文
Figma craft and precision
Audit the requested screen/scope with evidence. Use only the applicable design, copy and handoff criteria; a status reply or documentary typo does not trigger a full canvas audit. Review is read-only; corrections of your own work or an approved fix request use the current authorization, without a new per-item yes.
Applicable sources
- Project map/glossary/DS and current state govern expected values; project sample-data and locale rules override generic examples.
- slop-lens.md: overlap/density, process residue, visual excess, repetition, copy and communication criteria.
references/checks.md: 11 precision checks and bounded read-only extraction.references/punch-list.md: severity, swap/snap/ask and scoped decisions.figma-canonroutes API, state, naming, handoff or anomaly detail when this operation needs it. A numerical rubric can serve a requested scored audit; concrete blockers and evidence determine readiness, not an automatic 8/10 stamp.
Check the property/relationship in question: bindings, style/scale, component integrity, sizing, glossary and real pixels. Reuse valid collection, refresh when live changes/partial failure make it uncertain. Node ids can persist; validate file/target rather than asserting every id is session-specific.
For visual claims, inspect the affected frame/state and critical elements at a useful scale. A whole-section overview proves different things from a crop; no fixed screenshot count proves completeness. Record truncation, variable-mode limits, stale export risk and what was actually inspected.
Findings and action
Each finding carries source, node/path, found/expected, severity and action:
swap (identical equivalent), snap (signed measurable distance) or
ask (a new design decision). Approved snaps retain their distance in the
run’s fixes; intentional/debt decisions use .figma-slop-check/decisions.json
with scope and reason. Do not silently erase debt or invent canon.
A requested audit reports findings without applying them. An authorized fix can batch its approved scope, preserving lock/preflight and read-back. "Fix all" does not decide an unresolved product question. New evidence/regression justifies rechecking; no mandatory double pass, hidden checklist log or single-agent-versus-fanout ritual. Stop repeated failures for diagnosis.
Handoff adds its pertinent completeness criteria and can reuse this evidence. Report blockers, warnings and coverage honestly; do not send PR/Figma replies or publish a deliverable merely because a reviewer marked it ready. Runtime memory writes follow the runtime contract, not this review skill.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.