Results for “mappings”

Route active project/repo memory requests into one honest packet: memory-layer choice, load-context, search-context, store-conclusions, setup-integration, or repo-packer route-out. Use when agents need searchable decisions, manifests, stable links, handoff notes, and small “read this first” packets across sessions. Route long-lived markdown knowledge bases to `llm-wiki`, structural graph memory to `graphify`, human-authored vault organization to note/vault skills, and one-shot repo packing to tools like Repomix, Gitingest, or Code2Prompt.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Plans a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on the issue tracker, resolved one at a time. Use when the user has a large ambiguous goal and wants the route charted.

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

Map a complex topic by placing factors on hexagonal tiles where adjacency signals a claimed relationship. Use when students need to surface hidden connections in a system before analysis or action.

Expert en cartes et géolocalisation avancé (OpenStreetMap, Nominatim, OSRM, geocoding, routing, timezones, GIS)

Use an independently assigned `review-agent` for post-authoring review of changed rd-skills routing registries, fixtures, mappings, or owner conflicts without repair. Skip product work and in-task global rerouting.

Manage Heroku Connect sync operations between Salesforce and Heroku Postgres. Use when the agent needs to provision Heroku Connect, install or inspect the Heroku Connect CLI plugin, review mappings, import or export config, diagnose sync failures, or reason about Heroku Connect API limits and operational guardrails.