unjs-development

Select and apply UnJS packages for JavaScript and TypeScript projects.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/lonewolfyx/skills --skill unjs-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unjs-development
Source: https://github.com/lonewolfyx/skills/tree/main/skills/unjs-development
Command: npx skills add https://github.com/lonewolfyx/skills --skill unjs-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically selecting and applying the right UnJS package stacks for JavaScript/TypeScript projects based on deliverable, runtime boundaries, and architectural constraints.

Core Features & Use Cases

  • Anchor-delivery mapping for CLI, configuration, HTTP APIs, universal server runtimes, libraries, plugins, and cross-runtime SDKs.
  • Runtime-boundary awareness distinguishing build-time vs runtime dependencies.
  • Scenario-guided composition using the UnJS scenario playbooks and package catalog to justify package choices.

Quick Start

Provide a concise project description (for example, a CLI tool or HTTP API) and the Skill will propose the UnJS package composition.

Frequently Asked Questions about unjs-development

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

FAQPage Schema
How do I choose the right UnJS packages for my JavaScript project?

To choose the right UnJS packages, map your project deliverables to specific package families using scenario-driven composition, enforcing anchor-package selection and runtime boundaries to ensure deterministic, maintainable integrations.

What is the best way to scaffold a CLI tool using UnJS ecosystem packages?

The best way to scaffold a CLI tool using UnJS packages is to provide a concise project description, allowing the system to propose an optimal package composition that aligns with your architectural constraints and runtime boundaries.

How do UnJS configuration systems handle layered resolution for TypeScript projects?

UnJS configuration systems handle layered resolution by distinguishing build-time versus runtime dependencies, ensuring that scenario-guided composition maps your TypeScript deliverables to the correct package families deterministically.

Can I use UnJS packages for both HTTP APIs and universal server runtimes?

Yes, you can use UnJS packages for HTTP APIs and universal server runtimes by applying anchor-delivery mapping, which guides the selection of optimal package families based on your specific server runtime boundaries.

When should I not use certain UnJS packages in my JavaScript architecture?

You should not use certain UnJS packages when they violate runtime boundaries or architectural constraints, as deterministic integrations require strict anchor-package selection and scenario-driven composition to maintain maintainability.

Do I need to manually select UnJS plugins and libraries for cross-runtime SDKs?

No, you do not need to manually select UnJS plugins and libraries for cross-runtime SDKs, because the system automatically maps deliverables to optimal package families using scenario playbooks and package catalogs.