web-admin-ui
Skill2 starsChanged 18 days agoMITView on GitHub
Use when driving a web admin UI or admin SPA to find, set, or verify a setting - mapping the real capability set from routes and source, driving settings through models, and verifying state where the human looks.
In this repository40 other files it gives its agents.
- android-debloatSkill
- arch-linux-cachyosSkill
- beansSkill
- chezmoi-workflowsSkill
- coding-rulesSkill
- communicationSkill
- context7Skill
- docker-compose-setupSkill
- domain-modelingSkill
- audioSkill
- deploymentSkill
- ecsSkill
- game-loopSkill
- inputSkill
- physicsSkill
- renderingSkill
- resourcesSkill
- ebitenSkill
- ebook-convertSkill
- email-inbox-triageSkill
- gitSkill
- go-browser-testsSkill
- go-devSkill
- go-htmx-frontendSkill
- go-setupSkill
- go-testsSkill
- grillingSkill
- interactive-browser-testingSkill
- keep-on-goingSkill
- mcpcSkill
- obsidian-vault-triageSkill
- pixellabSkill
- playwright-mcpSkill
- port-parity-testingSkill
- public-repo-maturitySkill
- researchSkill
- retroSkill
- shell-startup-filesSkill
- shell-trapsSkill
- skill-craftSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 31
Verify where the human looks: the live widget DOM plus a screenshot in context.
≈ “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.
Files
Web admin UI mapping
The menu is a VIEW, not the capability list: firmware hides routes the backend still serves, and a menu-driven inventory misses them.
Map first, click second
- Enumerate the route registry from the console namespace, not from the menu: the router table lists every view the build ships.
- Fetch the view HTML and the module source and grep both for the setting's name; a setting absent from source is absent from the firmware, while a setting absent from the menu may still work.
- Bind the widget to its model instance, and the model to its RPC data block: the chain names the exact call that changes state.
Drive and verify
- Drive settings through the model, with the server ACK as the dirty flag: a UI toggle without an ACK changed pixels, not state.
- Verify where the human looks: the live widget DOM plus a screenshot in context. A model reload is not a persistence check; re-read the served state after a fresh page load.
- Hidden-route negatives are unproven while routes stay intact: a hidden menu entry does not prove removal.
- An eyewitness observation (the widget really shows the value) outranks a negative dump from a route scan.
- An eval one-expression timeout is a lost value: stash long-lived
objects on
windowbefore the long call. - Bare thenables need
Promise.resolve()beforeawait-chaining with other promises, or the chain throws.
Reporting
Distinguish hidden-in-this-mode from removed-in-this-firmware: the first is a menu problem, the second a capability change, and the report that merges them sends the reader to fix the wrong layer.
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
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.

