Packages Runtime

Enforce coding standards for packages runtime configuration and dependency handling.

7|Updated Dec 15, 2025

Search Tags:#performance #build #runtime #packages #bundling #dependency-management

Ready to run

npx skills add https://github.com/leaderiop/hex-di --skill packages-runtime

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Packages Runtime
Source: https://github.com/leaderiop/hex-di/tree/main/.claude/skills/packages-runtime
Command: npx skills add https://github.com/leaderiop/hex-di --skill packages-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Claude Code apply best practices for managing runtime aspects of packages, such as runtime dependencies, tree-shaking, and production build considerations.

Core Features & Use Cases

Runtime dependencies: Clear separation and proper versions for runtime vs dev dependencies.
Build performance: Guidance on packaging for efficient runtime behavior.
Use Case: When optimizing a package's runtime footprint, apply the standard to minimize bundle size.

Quick Start

Ask Claude to evaluate runtime dependencies and suggest optimizations for a given package setup.

Frequently Asked Questions about Packages Runtime

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

FAQPage Schema

How do I separate runtime and dev dependencies in my package?▼

Runtime dependencies are packages needed when your code runs in production; dev dependencies are only for build and testing. Separate them in your package configuration to reduce bundle size and ensure production environments have only essential packages installed.

What's the best way to optimize bundle size for runtime performance?▼

Optimize runtime performance by removing unused code through tree-shaking, minimizing runtime dependencies, and configuring your build to exclude dev-only packages. This reduces the final bundle size and improves startup and execution speed in production.

How do I handle dependency versions to ensure runtime stability?▼

Use explicit versioning for runtime dependencies to prevent unexpected behavior in production. Pin critical dependencies, test version upgrades before deploying, and maintain clear separation between stable runtime versions and development dependency versions.

Can I use tree-shaking to reduce my package's production footprint?▼

Tree-shaking removes dead code during the build process, significantly shrinking your runtime package. It works by identifying and eliminating unused exports, which is especially effective when combined with proper dependency management and build configuration.

Why does my package include unnecessary dependencies at runtime?▼

Unnecessary runtime dependencies often result from dev tools being marked as runtime dependencies or transitive dependencies pulled in by other packages. Audit your dependency tree, move dev tools to devDependencies, and use dependency analysis tools to identify and remove unused packages.

What packaging configuration matters most for runtime efficiency?▼

Runtime efficiency depends on entry point configuration, module format selection, and build output settings. Configure your package to export optimized code paths, use appropriate module formats for your target environment, and minimize the compiled output size.