tanaab-javascript

Reconcile JavaScript and TypeScript tasks within the Tanaab coding structure.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/pirog/me --skill tanaab-javascript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tanaab-javascript
Source: https://github.com/pirog/me/tree/main/skills/tanaab-javascript
Command: npx skills add https://github.com/pirog/me --skill tanaab-javascript

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill helps engineers structure and implement JavaScript and TypeScript work within the Tanaab coding framework, including Bun migration, ESM conversion, packaging metadata, and JavaScript-backed CLIs or actions.

Core Features & Use Cases

  • Guided JS/TS implementation within the Tanaab hierarchy, ensuring consistency across projects.
  • Bun migration and ESM conversion guidance for modern runtimes and module systems.
  • CLI/action scaffolding support for JavaScript-based automation and tooling.

Quick Start

Describe your JavaScript/TypeScript task within the Tanaab framework and let this skill outline the plan.

Frequently Asked Questions about tanaab-javascript

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

FAQPage Schema
How do I migrate a JavaScript project to Bun and ESM modules?

This skill provides guided Bun migration and ESM conversion, updating your module system decisions, packaging metadata, and runtime wiring for modern JavaScript and TypeScript projects.

What is the best way to scaffold a JavaScript CLI or action code?

Scaffolding JavaScript CLIs or actions requires structured guidance for consistent coding practices across JS/TS surfaces, including packaging metadata and runtime wiring within your coding framework.

Do I need TypeScript and ESM to use structured JavaScript coding guidance?

Yes, using ESM and aligning with an active core coding workflow are prerequisites for reconciling JavaScript and TypeScript implementation tasks and ensuring consistent coding practices.

How does this approach handle module system decisions for TypeScript?

Module system decisions are reconciled by applying structured guidance to packaging metadata, runtime wiring, and ESM conversion, ensuring consistent coding practices across all JavaScript and TypeScript surfaces.

Can I use this for both JavaScript and TypeScript implementation tasks?

Yes, it reconciles both JavaScript and TypeScript implementation tasks within a structured coding hierarchy, applying consistent guidance across module systems, packaging metadata, and runtime wiring.

When should I not use ESM conversion for my JavaScript project?

If your project lacks clear documentation or cannot satisfy active core workflow alignment prerequisites, you should defer ESM conversion until those structured coding requirements are met.