Webpack Config Documenter skill for Claude and Codex
A readable reference for an existing webpack config: what each entry, output setting, loader, and plugin does and why it is there, pitched at the reader you…
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 an existing webpack.config.js needs a plain-language reference doc for new team members or DevOps covering entry points, output, loaders, and plugins. Do not use for writing a new config, fixing a broken build, or tuning bundle size. Related topics: coding, webpack.
What it will ask you for
- The config (longer free text)
- Config file location (free text, e.g. "./webpack.config.js")
- Audience (choose one: Front-end developer, DevOps engineer, New team member)
- Detail level (choose one: Brief, Detailed)
- Include plugins overview (choose one: Yes, No)
- Include loaders overview (choose one: Yes, No)
- Output format (choose one: Markdown, HTML)
How it works
- Read the whole config and state in one sentence what the build produces, which becomes the Overview.
- Describe each entry point and the output settings, including hashing and public path, so a reader knows where every bundle lands.
- Document each loader rule by the files it matches and the transformation it applies, in the order webpack runs them.
- Explain each plugin's job and the non-default options that matter, leaving out defaults.
- Add a Notes section for environment variables, development versus production differences, and unusual settings with their likely reason.
- Trim or expand every section to the chosen detail level and return it in the requested format with nothing else.
What you get
A document in Markdown or HTML with sections Overview, Entry points, Output, Plugins and Loaders when requested, and Notes, each sized to the chosen detail level.
What it watches out for
- Restating option names as prose ('devtool is set to source-map') instead of saying what the setting means for the reader.
- Listing loaders in file order and missing that chained loaders run right to left, which misdescribes the pipeline.
- Documenting default values alongside real choices, which buries the three settings the team actually changed.
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.