agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/interface-craft-gate/SKILL.md

interface-craft-gate

Skill7 starsChanged 4 months agoMITView on GitHub

Make interface craft a required design-agent gate before and after UI changes.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this Note when UI work needs design craft, not only functional correctness.

    line 8
  2. Distinctive:

    If a running route or screenshot is available, audit that surface too:

    line 20
  3. Distinctive:

    Do not describe a UI as polished unless the handoff names:

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interface Craft Gate

Use this Note when UI work needs design craft, not only functional correctness.

Required local evidence

memi agent brief . --intent "Improve this interface" --json
memi diagnose .
memi ux audit . --json
memi craft audit . --json
memi tokens --from ./src --report

If a running route or screenshot is available, audit that surface too:

memi diagnose http://localhost:3000
memi ux audit http://localhost:3000 --json
memi craft audit http://localhost:3000 --json

Craft dimensions

Review these before patching:

  • focusing mechanism: what the user sees and does first
  • visual weight: contrast, density, and priority
  • typographic hierarchy: type scale, weight, line length, and scan order
  • spacing rhythm: repeated layout gaps and component padding
  • color intentionality: semantic color use, states, and token fit
  • component cohesion: variants, radius, strokes, icons, and shared anatomy
  • responsive resilience: breakpoints, overflow, touch context, and long content
  • user context care: stakes, confidence, recovery, and time pressure

Patch rule

Do not describe a UI as polished unless the handoff names:

  1. the evidence commands run,
  2. the craft dimensions that changed,
  3. the Atomic Design level touched,
  4. the shadcn/Tailwind primitives reused,
  5. the verification command that should run next.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free