agentleFS
carverautocarverauto/serviceradar/.agents/skills/fieldsurvey-local-web-ng/SKILL.md

fieldsurvey-local-web-ng

Skill934 starsChanged 2 days agoApache-2.0View on GitHub

Run ServiceRadar web-ng locally against the Kubernetes demo namespace FieldSurvey data, including CNPG NodePort access, NATS Object Store artifact access, authenticated browser checks, and Playwright screenshots for dashboard and FieldSurvey review iteration.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when iterating on elixir/web-ng FieldSurvey dashboard, spatial review, heatmap, raster, floorplan, or artifact rendering and …

    line 8
  2. Distinctive:

    Start local web-ng from the repo root:

    line 12
  3. Distinctive:

    If Chromium is missing, run:

    line 34
  4. Distinctive:

    Run the repeatable smoke check for the dashboard card, settings preview, and FieldSurvey review page:

    line 55
  5. Very specific:

    Prefer the CNPG NodePort over kubectl port-forward for Postgres.

    line 65
  6. Distinctive:

    Use the NATS port-forward only for Object Store artifacts.

    line 66
  7. Very specific:

    Keep screenshots under .playwright-cli/.

    line 68

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

FieldSurvey Local Web-NG

Use this skill when iterating on elixir/web-ng FieldSurvey dashboard, spatial review, heatmap, raster, floorplan, or artifact rendering and you need fast local feedback against real demo data.

Workflow

  1. Start local web-ng from the repo root:

    .agents/skills/fieldsurvey-local-web-ng/scripts/start-local-web-ng.sh

    The script:

    • reads current demo CNPG credentials from serviceradar-db-credentials;
    • discovers a reachable Kubernetes node for cnpg-local-dev NodePort;
    • extracts demo NATS creds/certs into tmp/fieldsurvey-local/;
    • starts a local NATS port-forward for Object Store artifact reads;
    • runs mix phx.server in elixir/web-ng with SERVICERADAR_LOCAL_LOG_LEVEL=info.
  2. Open and log in with Playwright:

    playwright-cli open http://localhost:4000/dashboard
    playwright-cli fill <email-ref> root@localhost
    playwright-cli fill <password-ref> 'serviceradar2026!'
    playwright-cli click <sign-in-ref>

    If Chromium is missing, run:

    playwright-cli install-browser chromium
  3. Capture the dashboard and review pages:

    playwright-cli resize 2048 1400
    playwright-cli screenshot --filename=.playwright-cli/fieldsurvey-dashboard-local.png
    playwright-cli goto http://localhost:4000/spatial/field-surveys
    playwright-cli screenshot --filename=.playwright-cli/fieldsurvey-review-local.png
  4. Inspect the dashboard FieldSurvey card:

    playwright-cli --raw eval "JSON.stringify(Array.from(document.querySelectorAll('[data-testid=fieldsurvey-heatmap]')).map(el => { const r = el.getBoundingClientRect(); return {width:r.width, height:r.height, style:el.getAttribute('style'), floorplan:el.querySelectorAll('line').length, circles:el.querySelectorAll('circle').length, images:el.querySelectorAll('image').length}; }))"
  5. Run the repeatable smoke check for the dashboard card, settings preview, and FieldSurvey review page:

    .agents/skills/fieldsurvey-local-web-ng/scripts/field-survey-smoke.sh

    This saves screenshots under .playwright-cli/ and fails if the dashboard card has no floorplan, the settings SRQL preview cannot resolve a persisted raster, or the review page does not load sessions.

Notes

  • Prefer the CNPG NodePort over kubectl port-forward for Postgres. The port-forward is too fragile under web-ng startup connection churn.
  • Use the NATS port-forward only for Object Store artifacts; it is lighter and stable enough for floorplan/point-cloud fetches.
  • Re-read Kubernetes secrets each run. Demo DB credentials can change after rollouts.
  • Keep screenshots under .playwright-cli/; do not commit them.
  • The local log-level guard prevents debug logs from printing NATS JWT/NKEY material.

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.