agentleFS
e-dule-dul/opencl-lab/.claude/skills/ux-review/SKILL.md

ux-review

Skill0 starsChanged 8 months agoMITView on GitHub

Procedure for simulating a user walkthrough of a module.

26 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Gather Context: Read the specified README.md and the associated code files in the module directory.

    line 9
  2. Distinctive:

    Verify that all necessary files exist in the exact paths specified.

    line 12
  3. Distinctive:

    Verify that the cognitive leap between previous modules and this one is fair.

    line 13
  4. Distinctive:

    Do NOT focus on C++ best practices (that is the reviewer's job).

    line 15

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “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

User Experience & Gap Analysis Skill

Instructions

  1. Gather Context: Read the specified README.md and the associated code files in the module directory.
  2. Simulate Execution:
    • Mentally step through every bash command and instruction in the README.
    • Verify that all necessary files exist in the exact paths specified.
    • Verify that the cognitive leap between previous modules and this one is fair.
  3. Report Output:
    • Do NOT focus on C++ best practices (that is the reviewer's job).
    • Output a list titled "Pedagogical Gaps & UX Friction".
    • Highlight any missing prerequisites, unclear instructions, or jumps in logic.

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.