with one click
axios-retryer
axios-retryer contains 12 collected skills from sampleXbro, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when creating, refactoring, or reviewing axios-retryer plugins. Enforces the repo's single recommended plugin architecture: top-level orchestrator class, focused folders for types/configs/errors/utils, optional stateful managers or storage adapters, explicit event-driven boundaries, and test-first extraction when files grow.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, Rollup-first build tooling, API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, preserving published package contracts, configuring dual CJS/ESM output, or setting up release workflows.
Use when creating, refactoring, or reviewing axios-retryer plugins. Enforces the repo's single recommended plugin architecture: top-level orchestrator class, focused folders for types/configs/errors/utils, optional stateful managers or storage adapters, explicit event-driven boundaries, and test-first extraction when files grow.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, Rollup-first build tooling, API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, preserving published package contracts, configuring dual CJS/ESM output, or setting up release workflows.
Use when creating, refactoring, or reviewing axios-retryer plugins. Enforces the repo's single recommended plugin architecture: top-level orchestrator class, focused folders for types/configs/errors/utils, optional stateful managers or storage adapters, explicit event-driven boundaries, and test-first extraction when files grow.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, Rollup-first build tooling, API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, preserving published package contracts, configuring dual CJS/ESM output, or setting up release workflows.
Use when creating, refactoring, or reviewing axios-retryer plugins. Enforces the repo's single recommended plugin architecture: top-level orchestrator class, focused folders for types/configs/errors/utils, optional stateful managers or storage adapters, explicit event-driven boundaries, and test-first extraction when files grow.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, Rollup-first build tooling, API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, preserving published package contracts, configuring dual CJS/ESM output, or setting up release workflows.
Use when creating, refactoring, or reviewing axios-retryer plugins. Enforces the repo's single recommended plugin architecture: top-level orchestrator class, focused folders for types/configs/errors/utils, optional stateful managers or storage adapters, explicit event-driven boundaries, and test-first extraction when files grow.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, Rollup-first build tooling, API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, preserving published package contracts, configuring dual CJS/ESM output, or setting up release workflows.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, Rollup-first build tooling, API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, preserving published package contracts, configuring dual CJS/ESM output, or setting up release workflows.
Use when creating, refactoring, or reviewing axios-retryer plugins. Enforces the repo's single recommended plugin architecture: top-level orchestrator class, focused folders for types/configs/errors/utils, optional stateful managers or storage adapters, explicit event-driven boundaries, and test-first extraction when files grow.