logosdx

name

logosdx

description

Implements LogosDX patterns for DOM manipulation, HTTP clients, lifecycle hooks, events, state machines, storage adapters, i18n/localization, and React context hooks. Use when tasks involve LogosDX libraries or code that imports from any logosdx scoped package. Trigger on any mention of HookEngine, FetchEngine, ObserverEngine, ObserverRelay, StateMachine, StateHub, StorageAdapter, LocaleManager, DomCollection, or the $() DOM selector. Also use when the user works with attempt/attemptSync error tuples, event queues, request deduplication/caching/rate-limiting, ICU pluralization, or any LogosDX pattern — even if they don't name the package explicitly.

LogosDX Skill

Use this skill for LogosDX setup and integration. Read only the reference file(s) needed for the task.

Quick Start

1. Identify package scope (dom, fetch, hooks, localize, observer, state-machine, storage, react, utils).
2. Open the matching file from references/.
3. Implement with strict typing and lifecycle cleanup.
4. Run project checks (typecheck/tests) before finishing.

Critical Rules

• Define type shapes first (headers, params, state, events, storage schema, locale shape).
• Use attempt()/attemptSync() for all I/O and error-prone operations — storage, fetch, invoke sources, queue processors, DOM mutations. Never use try-catch. The error tuple is the only sanctioned error handling pattern (see references/utils.md).
• Never hand-roll HTTP resilience around FetchEngine. Retry, request deduplication, response caching (TTL + stale-while-revalidate), token-bucket rate limiting, and per-route rules are built-in config keys (retry, dedupePolicy, cachePolicy, rateLimitPolicy). Do not write retry loops, in-flight promise maps, response caches, or throttles — and do not add p-retry/p-queue/lru-cache — before checking references/fetch.md § Built-in Resilience Policies. Different limits per endpoint means rules on one engine (each rule gets its own bucket), never a second FetchEngine instance.
• Always clean up resources (cleanup(), off(), destroy()).
• Keep React hook methods at component top level only.

Task Routing

Task	Reference
DOM manipulation, CSS, attributes, events, behaviors, viewport	references/dom.md
Lifecycle hooks, middleware, plugins, priority chains	references/hooks.md
HTTP client, retry, cache, dedupe, rate-limit, lifecycle events	references/fetch.md
i18n, translations, ICU pluralization, Intl formatting, locale switching	references/localize.md
Typed events, async generators, queues, observation, relay	references/observer.md
Finite state machines, guards, async invoke, StateHub coordination	references/state-machine.md
Storage CRUD, key scoping, events, custom drivers	references/storage.md
React factories, hooks, provider composition, API hooks	references/react.md
Error tuples, flow control, memoization, typed helpers, unit conversion	references/utils.md
Cross-package design (start here, then open package-specific files)	references/REFERENCE.md