Webpack Config Analyzer skill for Claude and Codex
Explains an existing webpack configuration in plain terms: what each entry builds, where output goes, which loader handles which files, what every plugin…
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 you inherited a webpack config and need to understand what each entry, loader, plugin, and optimization setting actually does. Do not use for writing a new webpack config from scratch or diagnosing a build that fails or runs slowly. Related topics: coding, webpack.
What it will ask you for
- Config source (longer free text)
- Config file path (free text, e.g. "build/webpack.prod.js")
- Target environment (choose one: development, production, test)
- Explain source maps (choose one: Yes, No)
- Sections to cover (choose any: entry, output, loaders, plugins, resolve, optimization, devServer)
- Depth (choose one: Overview, Standard, Every option)
How it works
- Resolve the effective config for the chosen environment by evaluating function forms, merges, and webpack defaults.
- Describe each requested section in build order: what each entry produces, the resolved output names, each loader rule with run order, each plugin's effect.
- Explain the chunks that optimization and splitChunks create and what devServer proxies or hot-reloads.
- Flag surprises such as missing minification in production, leaking source maps, or rules that never match.
- Fill the summary table and keep each section at the chosen depth.
What you get
A markdown document with a summary table, one heading per requested section with bullet points, and a closing Watch Out list.
What it watches out for
- Describing the config file as written instead of the effective config, missing defaults and merged overrides that change the build.
- Listing loaders in a rule in the order they appear, when webpack runs them last to first.
- Explaining what a plugin is in general rather than what its options do in this build.
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.