Webpack Config Debugger skill for Claude and Codex
Finds what is wrong with a webpack config that fails, builds slowly, or ships the wrong output: each issue tied to the line and rule it breaks, with a…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a webpack build fails, rebuilds slowly, or ships wrong output and you need the config lines responsible and the corrected snippets. Do not use for explaining a config that works, or generating a fresh config for a new project. Related topics: coding, webpack.
What it will ask you for
- Config file (longer free text)
- Symptom (longer free text)
- Target environment (choose one: development, production, both)
- Focus area (choose any: entry, output, loaders, plugins, optimization, devServer, resolve)
- Webpack version (choose one: 5, 4, Not sure)
- Minimum severity to report (choose one: Critical only, Critical and warning, Everything including style)
- Verbose explanations (choose one: On, Off)
How it works
- Trace the symptom and error text back to the config line or rule responsible before auditing anything else.
- Audit each focus area for the common faults (unmatched loader tests, wrong chain order, missing extensions, publicPath, version-mismatched plugin options).
- For slow builds, check devtool choice, cache settings, and whether node_modules is being transpiled.
- Classify every finding by severity and drop those below the chosen threshold.
- Write each finding with its line, broken rule, explanation, and a corrected javascript snippet, or declare the config healthy.
What you get
A markdown document with Summary of critical issues, Detailed findings by focus area with severity, and Corrected snippets as javascript blocks, in that order.
What it watches out for
- Fixing the loader test regex without checking the loader order, so the build still fails one rule later.
- Reporting webpack 4 style plugin options as correct on a webpack 5 config where the option was renamed or removed.
- Recommending source-map for production without noting it publishes the original source to every visitor.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.