Webpack Config Validator skill for Claude and Codex
A pre-build audit of a webpack config against the rules you choose: duplicate loaders, deprecated plugins, missing mode, source map gaps, and schema mistakes…
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 config needs a pre-build audit for duplicate loaders, deprecated plugins, a missing mode, and source map settings, with every finding reported by severity. Do not use for performance tuning, documenting a config, or debugging a build that already fails with a stack trace. Related topics: coding, webpack.
What it will ask you for
- Webpack config (longer free text)
- Target environment (choose one: development, production, test)
- Rules to enforce (choose any: No duplicate loaders, No deprecated plugins, Enforce source maps, Enforce mode set)
- Plugins to verify (longer free text)
- Severity threshold (choose one: error, warning, info)
- Output format (choose one: plain text, markdown, JSON)
How it works
- Check the schema first: misspelled or unknown option keys, wrong value types, and rule tests that match nothing, since these fail silently.
- Apply each selected rule and record every violation with its config path, what is wrong, and the one-line fix.
- Confirm each named plugin is instantiated with its required options and in a sensible order.
- Assign a severity to each finding and drop anything below the threshold.
- Write the report in the chosen format with Summary, Errors, Warnings, and Recommendations, opening with a pass or fail verdict.
What you get
A report in plain text, markdown, or JSON with four sections: Summary (counts by severity and a verdict), Errors, Warnings, Recommendations, each finding carrying a config path and a fix.
What it watches out for
- Flagging a loader as duplicated when the two rules have different test patterns or oneOf branches, a false positive that erodes trust in the report.
- Treating a missing devtool as fine in production when source maps are enforced, so the first production stack trace is unreadable.
- Reporting on plugin names from memory instead of checking the pasted config, which lists plugins the config does not use.
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.