es-toolkit

Enforce es-toolkit usage and module-scoped imports in JavaScript/TypeScript projects.

1|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/rodrigobranas/formacao_ia_arq_t1_4 --skill es-toolkit-rodrigobranas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: es-toolkit
Source: https://github.com/rodrigobranas/formacao_ia_arq_t1_4/tree/main/mastra-rag/.agents/skills/es-toolkit
Command: npx skills add https://github.com/rodrigobranas/formacao_ia_arq_t1_4 --skill es-toolkit-rodrigobranas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes utility usage across a codebase by enforcing es-toolkit usage instead of custom implementations.

Core Features & Use Cases

  • Provides modular utility modules (array, object, string, function, util) with clear import paths to enable tree-shaking.
  • Encourages import from specific es-toolkit modules (e.g., es-toolkit/array, es-toolkit/object) rather than from the root to optimize bundles.
  • Includes guidelines and best practices to migrate existing code to es-toolkit and maintain consistency across teams.

Quick Start

Replace any custom utilities with es-toolkit equivalents and import from specific modules (e.g., es-toolkit/array, es-toolkit/object).

Frequently Asked Questions about es-toolkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize JavaScript and TypeScript utility usage across a codebase?

You can standardize JavaScript and TypeScript utility usage by enforcing es-toolkit imports instead of custom implementations. This ensures consistent patterns for arrays, objects, strings, and function utilities across your entire project.

How do I optimize bundle size when importing utilities in TypeScript projects?

To optimize bundle size in TypeScript projects, import utilities from specific es-toolkit submodules like es-toolkit/array or es-toolkit/object rather than the root. This enables tree-shaking to remove unused code from your bundles.

What's the best way to migrate existing code to es-toolkit?

The best way to migrate existing code to es-toolkit is to replace custom utilities with es-toolkit equivalents. Import specific modules like es-toolkit/array and follow established guidelines to maintain consistency across teams during migration.

Does es-toolkit support tree-shaking for modular utility imports?

Yes, es-toolkit supports tree-shaking through modular utility modules with clear import paths. Importing from specific submodules like es-toolkit/object instead of the root package enables optimal bundle optimization.

Can I use es-toolkit to enforce coding standards for array and object manipulation?

Yes, you can use es-toolkit to enforce coding standards for array and object manipulation. It provides modular utility modules with consistent import patterns, codifying best practices for JavaScript and TypeScript projects.

Why should I use es-toolkit instead of custom utility implementations?

You should use es-toolkit instead of custom implementations to standardize utility usage across your codebase. It provides modular, tree-shakeable imports for arrays, objects, strings, and functions, ensuring consistency and reducing maintenance overhead.