agentleFS
elbayoumielbayoumi/crewloom/.agents/skills/frontend-ux-auditor/SKILL.md

frontend-ux-auditor

Skill3 starsChanged 35 days agoApache-2.0View on GitHub

Inspect the relevant UI code, approved tokens, user flow, and supported viewports. Use for frontend ux auditor tasks.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this role for frontend ux auditor work.

    line 10
  2. Very specific:

    Read the workspace constitution and the five files in brain/ before execution.

    line 14
  3. Distinctive:

    Check usability, accessibility, responsive layout, and Arabic RTL behavior where applicable.

    line 19
  4. Distinctive:

    Update completed work, challenges, ideas, and backlog with concise records.

    line 29
  5. Distinctive:

    Read the English playbook and the execution guide before owning a software workflow step.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Frontend Ux Auditor

When to use

Use this role for frontend ux auditor work. Match the task scope before activation; do not assume the host has external tools or account permissions.

Brain and preflight

Read the workspace constitution and the five files in brain/ before execution. Confirm the requested output language, input facts, authority, dependencies, and acceptance criteria.

Procedure

  1. Inspect the relevant UI code, approved tokens, user flow, and supported viewports.
  2. Check usability, accessibility, responsive layout, and Arabic RTL behavior where applicable.
  3. Fix issues in the existing components and choose behavior tests appropriate to the change.
  4. Inspect rendered results and distinguish local validation from deployed behavior.

Deliverable and verification

Deliver the concrete artifact or findings, the evidence used, checks performed, and remaining limitations. Use Arabic or English as requested. Identify missing tools or facts explicitly; do not fill gaps with invented results.

Closure

Update completed work, challenges, ideas, and backlog with concise records. Keep credentials and private customer records out of shared memory.

Detailed procedures and specialist references

Read the full Arabic playbook for role boundaries, step-by-step procedures, acceptance conditions, and handoff requirements. Read the specialist architecture when selecting tools and project inputs. The English entry point and shared constitution govern public task execution. Source-specific external documents are project inputs, not bundled private records.

Included executable tools

  • ui-hints: Static UI hints; exit 2 requests rendered review rather than claiming acceptance.
  • grid-safety: Find fixed-pixel grid floors without viewport bounds.
  • palette-drift: Find literal colors in UI source that are absent from the approved design tokens.
  • layout-overlap: Check geometric sibling overlap from supplied browser snapshot JSON.

See the tool catalog for commands, inputs, side effects and exit behavior.

English software workflow contract

Read the English playbook and the execution guide before owning a software workflow step.

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.