agentleFS
m4r1km4r1k/Eneru/.claude/skills/dashboard-preview/SKILL.md

dashboard-preview

Skill152 starsChanged 31 days agoMITView on GitHub

Visually verify Eneru browser-dashboard changes against a live daemon or audit an exact deployment. Use whenever web assets change and you need to see the result rendered on real telemetry. Preview serves working-tree assets over a live API; deployed audit inventories and screenshots the assets a running instance actually serves.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. langchain-ai/open-swe★ 11ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Before pushing a PR that touches the dashboard — capture light + dark and read the PNGs to confirm there are no console errors and the …

    line 24
  2. Distinctive:

    After deploying a dashboard build — audit every visible tab and its safe, read-only submenus at the real URL.

    line 26
  3. Very specific:

    Read the PNGs and report.json.

    line 73
  4. Distinctive:

    Use preview before deployment and deployed audit after deployment.

    line 123

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

Dashboard preview

The browser dashboard is static assets (src/eneru/web/) that talk to the daemon's JSON API. String-only or fixture-based tests miss layout, theming, and chart-rendering regressions. This skill supports two related checks:

  1. dashboard-preview.py renders working-tree assets against a live daemon so an uncommitted change can be verified by eye.
  2. dashboard-audit.py visits a deployed daemon directly so the screenshots prove what that installation actually serves.

ELI5: a one-way mirror in front of the running daemon — you see your brand-new UI code, but every data question is passed through to the real daemon and the real answer comes back. Tomorrow's dashboard on today's live data.

When to use

  • Any change under src/eneru/web/ (app.js, style.css, index.html).
  • Before pushing a PR that touches the dashboard — capture light + dark and read the PNGs to confirm there are no console errors and the affected tab renders.
  • After deploying a dashboard build — audit every visible tab and its safe, read-only submenus at the real URL.

Prerequisites

  1. A running Eneru daemon with the API enabled (default http://127.0.0.1:9191). Confirm: curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:9191/api/v1/ups should print 200.
  2. The dev environment with Playwright + Chromium (per AGENTS.md the venv must be a uv venv; never the system Python):
    uv venv /tmp/eneru-venv && source /tmp/eneru-venv/bin/activate
    uv pip install -e ".[dev]"
    playwright install chromium

Run it

Preview working-tree assets

python tools/dashboard-preview.py                       # all tabs, light+dark
python tools/dashboard-preview.py --themes light        # light only
python tools/dashboard-preview.py \
    --daemon http://127.0.0.1:9191 \
    --out /tmp/eneru-preview \
    --tabs overview,battery

Then Read the PNGs (<out>/dash-[<theme>-]<tab>.png) to actually look at the result. The script also prints any browser console errors/warnings and exits non-zero if it saw any — treat those as failures.

Audit an exact deployment

/tmp/eneru-venv/bin/python tools/dashboard-audit.py \
    --url http://eneru-host:9191 \
    --out /tmp/eneru-dashboard-audit \
    --capture-scopes

# Include the authenticated Control tab. The password is prompted securely.
/tmp/eneru-venv/bin/python tools/dashboard-audit.py \
    --url https://eneru.example.test \
    --username admin

Read the PNGs and report.json. The audit covers every visible tab in light and dark themes, UPS detail dialogs, Event type filters, the sanitized Config tree, a mobile viewport, and optional per-UPS scopes. It records console warnings/errors, failed or HTTP-error requests, select options, and visible controls without accessible names. It exits non-zero when those checks find an issue.

The deployed audit is read-only. It never clicks UPS commands, self-tests, variable writes, event deletion, config reload, or shutdown actions. Do not add one of those actions to the tool merely to broaden coverage; hardware-changing tests belong in a purpose-built, disposable environment.

Options

Working-tree preview

FlagDefaultMeaning
--web-dirsrc/eneru/webworking-tree assets to serve
--daemonhttp://127.0.0.1:9191live daemon API to proxy to
--port9232local preview-server port
--out/tmp/eneru-previewscreenshot output directory
--tabsall 7comma-separated tabs to capture
--themeslight,darkcomma-separated themes
--settle-ms2500wait for first refresh + charts to settle

Deployed audit

FlagDefaultMeaning
--urlhttp://127.0.0.1:9191deployed dashboard URL
--out/tmp/eneru-dashboard-auditPNG and JSON output directory
--tabsevery visible tabcomma-separated tabs to capture
--themeslight,darkcomma-separated themes
--usernamenonesign in to expose authenticated read-only UI; password is prompted
--settle-ms1200wait after initial load before inspection
--tab-settle-ms650wait after each tab or scope change
--capture-scopesoffcapture Overview once per individual UPS
--mobile-width390mobile Overview width; 0 disables it

Notes

  • The preview server proxies everything that is not /, /app.js, or /style.css straight to the daemon, so auth, history, energy, battery-health, and event endpoints all return real data.
  • For endpoints a given daemon can't serve (e.g. a feature still in the working tree), point --daemon at a daemon that can, or stub the route in a local fork of the harness.
  • This is the project's standard dashboard-verification loop — prefer it over trusting unit tests for any visual change.
  • Use preview before deployment and deployed audit after deployment. Together, they distinguish a source-code regression from stale or incorrectly packaged static assets.

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.