Decide placement of new helper functions between @ethernauta/utils and package-local colocation.
npx skills add https://github.com/niconiahi/ethernauta --skill utils-niconiahi
Please help me install this Agent Skill. Skill: utils Source: https://github.com/niconiahi/ethernauta/tree/main/skills/utils Command: npx skills add https://github.com/niconiahi/ethernauta --skill utils-niconiahi
This Skill prevents helper-function sprawl by making it clear where new utilities belong, so your codebase stays pure, dependency-light, and reusable.
@ethernauta/utils remains pure and dependency-free, with no I/O, no DOM, no wallet/chains side effects, and minimal module-scope behavior.@ethernauta/utils or colocate next to the caller (e.g., domain-specific logic, stateful dependencies, or single-use helpers).Use the skills/utils guidance to decide where a new helper should live, then add it to @ethernauta/utils only if it satisfies the pure, dependency-free, domain-agnostic, multi-package criteria.
High-intent search queries and answers about installing and using this skill.
To place a utility function in a TypeScript monorepo, use a decision rubric checking if the helper is pure, side-effect-free, and domain-agnostic. If it meets these criteria, add it to the shared utilities package; otherwise, colocate it locally with the caller.
Shared utility packages must stay dependency-free by enforcing no I/O, no DOM access, no wallet or RPC side effects, and minimal module-scope behavior. This ensures utilities remain reusable and avoid dependency creep across the monorepo.
Colocate helper functions instead of adding them to a shared package when the logic is domain-specific, requires stateful dependencies, is single-use, or couples to a particular domain. Shared packages should only contain pure, domain-agnostic utilities.
No, you should not add UI-specific formatting functions to a general utilities package. The package must stay domain-agnostic and side-effect-free, meaning UI formatting should be colocated next to the caller rather than centralized in shared utilities.
Pure helper functions that belong in a shared utils package include hex and byte conversions, units calculations, time utilities, RLP encoding, assertions, and string case conversion. These must be side-effect-free with no external dependencies.
Monorepo helper-function sprawl and dependency creep occur when utilities are added to shared packages without enforcing purity boundaries, introducing I/O, DOM access, or domain coupling. Applying a strict catalog and decision rubric prevents this by ensuring proper colocation.
mouayadakelDetect duplicate code segments and suggest refactoring into parameterized functions.
PatternsDevEliminate dead code from JavaScript bundles using ES module imports.
huseyindenizDetect architectural boundary and dependency violations across core, domain, and composition-root contexts.
gileckStandardize client-server API communication with centralized endpoint patterns and React Query.