babel-config
Generates Babel configuration for JavaScript transpilation in tests. Creates babel.config.js file.
Best use case
babel-config is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generates Babel configuration for JavaScript transpilation in tests. Creates babel.config.js file.
Teams using babel-config should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/babel-config/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How babel-config Compares
| Feature / Agent | babel-config | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates Babel configuration for JavaScript transpilation in tests. Creates babel.config.js file.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Babel Config Skill ## Purpose Generate a Babel configuration file for transpilation in tests. ## 🔍 BEFORE GENERATING - RESEARCH CURRENT STANDARDS **⚠️ CRITICAL: Always verify current standards before generating. This skill may reference outdated conventions.** 1. **Check latest Babel documentation**: https://babeljs.io/docs/configuration 2. **Verify current config file format**: Run `npm view @babel/core version` to check latest Babel version 3. **Verify current preset package names**: Check if `@babel/preset-env`, `@babel/preset-typescript` are still current 4. **Check for deprecation warnings**: Review latest Babel release notes for breaking changes 5. **If standards have changed**: Use NEW standards from official docs, NOT the examples below ## 🚨 MANDATORY FILE COUNT **Total Required: 1 file** - Babel config file (1 file) - extension may be `.cjs`, `.mjs`, `.js`, or `.json` depending on current standards **If this file is not created, test transpilation will FAIL.** ## Requirements (Dynamic - Verify Current Standards) - Check current Babel best practices before generating - Use latest recommended presets from official Babel documentation - Use current standard file extension for Babel configs - Verify package names exist in npm registry before adding: `npm view <package> version` - If `@babel/preset-env` is deprecated, use its successor - If `.cjs` extension is outdated, use current standard ## Output Create a Babel configuration file with the currently recommended format ## Example Configuration (As of December 2025 - May be outdated) ⚠️ **VERIFY these packages and conventions are still current before using:** ### Example File: `babel.config.cjs` - **Extension**: `.cjs` (CommonJS format - verify this is still standard) - **Presets**: - `@babel/preset-env` (for ES6+ transpilation - check if deprecated) - `@babel/preset-typescript` (for TypeScript - check if deprecated) - **Plugins**: - `@babel/plugin-transform-runtime` (check if still recommended) **If any of these are deprecated or outdated:** - Check: https://babeljs.io/docs/ for current replacements - Check: `npm view @babel/core@latest` for latest version info - Check: Babel migration guides for breaking changes ## Execution Checklist Use this checklist to ensure the file is created: - [ ] **FIRST**: Research current Babel standards (see "BEFORE GENERATING" section) - [ ] Create Babel config file at project root (verify correct extension) - [ ] File includes current standard presets for ES6+ and TypeScript - [ ] File includes current standard plugins (if any) - [ ] Verify packages exist in npm: `npm view <package> version` - [ ] Verify file exists: `ls babel.config.*` ## 🛑 BLOCKING VALIDATION CHECKPOINT **STOP AND VERIFY before proceeding to the next skill:** ### Automated Verification (Flexible for any extension) Run this command to verify the file exists: ```bash # Check for babel config file (any valid extension) if [ ! -f babel.config.cjs ] && [ ! -f babel.config.mjs ] && [ ! -f babel.config.js ] && [ ! -f babel.config.json ]; then echo "❌ MISSING: babel config file (expected: .cjs, .mjs, .js, or .json)" exit 1 fi echo "✅ Babel config file present" ``` ### Manual Verification 1. ✓ Babel config file exists at project root (any current standard extension) 2. ✓ File contains current standard presets for ES6+ transpilation and TypeScript 3. ✓ File contains current standard plugins (if required) 4. ✓ All package names verified to exist: `npm view <package> version` 5. ✓ Configuration follows latest Babel documentation standards ### If Validation Fails **DO NOT PROCEED** to the next skill. Create the missing file immediately. ## Notes - Babel configuration for test environment transpilation (Jest/Vitest with Babel) - Transpiles modern JavaScript for Node test environment - File format depends on current Babel standards (check docs) - Presets automatically determine necessary transformations - Enables use of modern syntax in test files - Required for test frameworks to process ES modules and modern JavaScript features - **Always verify current standards** - Babel ecosystem evolves over time
Related Skills
azure-appconfiguration-ts
Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o...
aspnet-configuration
Guide for ASP.NET Core configuration with appsettings.json, environment-specific settings, and the options pattern
appconfig-system
Expert guidance for working with the AppConfig runtime configuration system in squareone. Use this skill when implementing configuration loading, working with YAML config files, setting up new pages that need configuration, troubleshooting config hydration issues, or migrating from next/config patterns. Covers server-side loadAppConfig(), client-side useAppConfig(), MDX content loading, Sentry configuration injection, and Kubernetes ConfigMap patterns.
api-gateway-configurator
Configure and manage API gateways including Kong, Tyk, AWS API Gateway, and Apigee. Activates when users need help setting up API gateways, rate limiting, authentication, request transformation, or API management.
anyway-config-coder
Implement type-safe configuration with anyway_config gem. Use when creating configuration classes, replacing ENV access, or managing application settings. Triggers on configuration, environment variables, settings, secrets, or ENV patterns.
ameba-configuration
Use when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
akka-net-aspire-configuration
Configure Akka.NET with .NET Aspire for local development and production deployments. Covers actor system setup, clustering, persistence, Akka.Management integration, and Aspire orchestration patterns.
add-config-field
Guide adding a new config field across types, defaults, config.yaml, and optional state/env wiring.
add-app-config
Use when adding configuration for a new application to the dotfiles, setting up a new tool's config, or when user says "add config for X"
a2a-server-config
Agent-to-Agent (A2A) server configuration patterns for HTTP, STDIO, SSE, and WebSocket transports. Use when building A2A servers, configuring MCP transports, setting up server endpoints, or when user mentions A2A configuration, server transport, MCP server setup, or agent communication protocols.
configure-downstream
Configure Konflux for new Submariner version - creates overlays, tenant config, and RPAs for Y-stream releases.
aerospace-config
Complete AeroSpace tiling window manager configuration assistant for macOS. Use for any AeroSpace configuration task including keybindings, workspace management, window rules, layouts (BSP, columns, rows, accordion), focus behavior, gaps, floating windows, app-specific settings, exec commands, or any window management customization. Also use for debugging and troubleshooting AeroSpace issues including log inspection, window state analysis, and diagnosing layout problems. This skill fetches fresh documentation for each request to ensure accurate, up-to-date guidance.