Figma Slop Check logo

Figma Slop Check

Community
thiagoxikota
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.

Overview

Publisherthiagoxikota
Repositoryfigma-maxxing
Skill namefigma-slop-check
Stars
11
Forks
1
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by thiagoxikota on GitHub. Read the source before you install it.

Installation

Install the Figma Slop Check AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/thiagoxikota/figma-maxxing/tree/main/skills/figma-slop-check
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/thiagoxikota/figma-maxxing.git /tmp/figma-maxxing
mkdir -p .claude/skills
cp -r /tmp/figma-maxxing/skills/figma-slop-check .claude/skills/figma-slop-check
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Figma Slop Check in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Figma Slop Check on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Figma Slop Check is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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-canon routes 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Figma Slop Check AI skill do?

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.

Why use Figma Slop Check on TypingMind?

Because you install it once and use it with any model. Figma Slop Check is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Figma Slop Check in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thiagoxikota/figma-maxxing/tree/main/skills/figma-slop-check. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Figma Slop Check?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Figma Slop Check?

As many as you like. As long as a model supports skills, you can use Figma Slop Check with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Figma Slop Check AI skill free?

Yes. It is published on GitHub by thiagoxikota under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇