agentleFS
geoai-latamgeoai-latam/SKILL_JS5_ARCGIS/skills/arcgis-core-utilities/AGENTS.md

SKILL_JS5_ARCGIS / arcgis-core-utilities

AGENTS.md1 starsChanged 6 months agoMITView on GitHub

Quick-reference for the SDK core utilities. Read before wiring reactive/async logic. 1. Observe a property over time? → reactiveUtils.watch. 2. Run when a condition becomes true? → every time: reactiveUtils.when; once: whenOnce (or { once: true }). Callbacks are async and batched; { sync: true } for every change. 3. Async that can be superseded? → promiseUtils.debounce + isAbortError. 4. REST call? → esriRequest. 5. Observable array? → Collection<T>.

The file

Files
AGENTS.md

Agent Guide: arcgis-core-utilities

Quick-reference for the SDK core utilities. Read before wiring reactive/async logic.

Quick Decision Tree

  1. Observe a property over time? → reactiveUtils.watch.
  2. Run when a condition becomes true? → every time: reactiveUtils.when; once: whenOnce (or { once: true }). Callbacks are async and batched; { sync: true } for every change.
  3. Async that can be superseded? → promiseUtils.debounce + isAbortError.
  4. REST call? → esriRequest.
  5. Observable array? → Collection<T>.

Setup Checklist

  • Import utilities as namespaces (import * as reactiveUtils).
  • Store every watch/when handle and call handle.remove() on cleanup.
  • Wrap superseded async in try/catch and ignore abort errors.
  • Mutate Collections via add/removeAt, never index assignment.

Anti-patterns (one-liner reminders)

  • ❌ Never removing watch handles (memory leak).
  • ❌ Showing errors for abort errors.
  • ❌ collection[i] = x — use add/removeAt.
  • ❌ Preferring legacy instance.watch() over reactiveUtils.

Files in This Skill

  • SKILL.md / SKILL.es.md — full guides
  • references/api-detail.md — utility signatures
  • references/examples.md — watch / debounce / request examples
  • references/pitfalls.md — extended troubleshooting
  • scripts/snippet-reactive.ts, snippet-request.ts, snippet-collection.ts

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.