agentleFS
petecurranpetecurran/sorted/static/CLAUDE.md

sorted / static

CLAUDE.md0 starsChanged 45 days agoMITView on GitHub

Two front ends in plain HTML, CSS and JavaScript, with no framework and no build step. server.py serves the files as they are.

The file

Files
CLAUDE.md

static/

Two front ends in plain HTML, CSS and JavaScript, with no framework and no build step. server.py serves the files as they are.

FolderWhat it is
public/The residents' site: the map, reporting a photo, "Is it still there?"
council/The officers' console: the triage queue and cards, plus the Routes, Return and Reduce tabs in views/
shared/api.js (fetch helper and the status words), brand.js (applies content/brand.json), tokens.css (colours and spacing), livereload.js
vendor/leaflet/Leaflet 1.9.4, third-party. Don't edit it.
  • Write the baseline brand. Pages say "Mersey Vale" and "MVCC-" and use the --brand colour variables from tokens.css. At load time, brand.js recolours the page and rewrites every visible name from /api/brand.js, so a rebrand never touches this folder. A colour written straight into a stylesheet won't follow a rebrand.
  • The public site is for remote callers. Phones reach only the paths server.py allows through the tunnel (TUNNEL_PREFIXES, TUNNEL_API and _tunnel_allowed). A new call from public/ has to be added there, and it must not expose anything from the council side.
  • Residents never see cost, or that an officer is involved. The public list carries only triage.decision, and statuses come from public_status. tests/smoke.py checks the API side of this; the pages must not work around it.
  • Edits show on reload. The server sends no-cache for everything here except vendor/. The ?v= numbers in the HTML are left over from the hackathon; there's no need to bump them.
  • Check a change on every page. scripts/brand_check.py opens 21 views at desktop and phone sizes and fails any view that shows a console error, is wider than the screen, has a broken logo, or has white text below 4.5:1 contrast on the brand colour. /screenshots refreshes the README's images.

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.