agentleFS
Sign inStart free
MCamnerMCamner/mq-image-analyze/skills/web-ui-maintainer/SKILL.md

web-ui-maintainer

Skill1 starsChanged 22 days agoMITView on GitHub

Use when changing mq-image-analyze web UI, FastAPI web server, packaged web assets, serve command, local ports, upload flow, or browser review workflow.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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. Very specific:

    Use this skill for mq-image serve and browser-based image analysis.

    line 8
  2. Distinctive:

    Keep local server bind/port behavior explicit.

    line 44
  3. Distinctive:

    Do not add analytics or external uploads without explicit user request.

    line 45
  4. Distinctive:

    Keep file upload handling scoped and temporary.

    line 46
  5. Distinctive:

    Update package data if new static assets are introduced.

    line 47
  6. Distinctive:

    Add tests when packaging or route behavior changes.

    line 48

≈ “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

Web UI Maintainer

Use this skill for mq-image serve and browser-based image analysis.

Evals

Should trigger

  • "fix the web upload flow"
  • "the serve command port handling is wrong"
  • "improve the browser review workflow"
  • "the packaged web assets are stale"

Should not trigger

  • "change the CLI" → use cli-maintainer
  • "change MCP tools" → use mcp-tools-maintainer
  • "update web docs only" → use docs-maintainer

Core Files

  • mq_image_analyze/cli/serve.py
  • mq_image_analyze/web/server.py
  • mq_image_analyze/web/index.html
  • tests/test_web_package.py
  • docs/cli.md
  • README.md

UI Contract

  • The web UI should expose image upload/analysis clearly.
  • Web assets live only in the package, under mq_image_analyze/web/.
  • mq-image serve --port 8000 should be documented and testable.
  • Browser output should reflect the same JSON contracts as CLI/MCP where applicable.

Change Rules

  • Keep local server bind/port behavior explicit.
  • Do not add analytics or external uploads without explicit user request.
  • Keep file upload handling scoped and temporary.
  • Update package data if new static assets are introduced.
  • Add tests when packaging or route behavior changes.

Verification

python -m pytest tests/test_web_package.py -q
mq-image serve --help

Manual check:

mq-image serve --port 8000

Then open http://127.0.0.1:8000.

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