Agent skill

Webpack Plugin Authoring

by pproenca in pproenca/dot-skills

Writing webpack 5 plugins — hook selection (compiler vs compilation, tap vs tapAsync, processAssets stages), the asset pipeline (emitAsset, source classes, info metadata, source maps), watch-mode…

MITAuto-check passedTesting & QA

Install Webpack Plugin Authoring

skills CLI
$ npx skills add pproenca/dot-skills --skill webpack-plugin-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pproenca/dot-skills webpack-plugin-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/webpack-plugin-authoring .claude/skills/webpack-plugin-authoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
webpack-plugin-authoring
GitHub stars
214
Token cost
~2.7k tokens
SKILL.md length
679 words
Files
49 (incl. references, assets)
Skills in repo
182
Repo updated
First seen
Licence
MIT

At a glance

Writing webpack 5 plugins — hook selection (compiler vs compilation, tap vs tapAsync, processAssets stages), the asset pipeline (emitAsset, source classes, info metadata, source maps), watch-mode…

  • Works in 8 steps: Hook Selection & Tap Patterns (CRITICAL) → Asset Pipeline (CRITICAL) → Caching & Watch Mode (HIGH) → …
  • Debugging webpack 5 plugins — even if the user doesnt explicitly mention best practices — anytime an apply(compiler) method is being written
  • SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Webpack Plugin Authoring is an agent skill from pproenca/dot-skills. Writing webpack 5 plugins — hook selection (compiler vs compilation, tap vs tapAsync, processAssets stages), the asset pipeline (emitAsset, source classes, info metadata, source maps), watch-mode and persistent caching (file/context/missing/buildDependencies), plugin lifecycle (constructor purity, multi-compiler isolation, shutdown cleanup), schema-utils validation, WebpackError reporting, jest-worker parallelism, and compatibility patterns (compiler.webpack namespace, peerDependencies, getCompilationHooks…

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 51 other files, including reference files and assets (for example `AGENTS.md`, `assets/templates/_template.md` and `metadata.json`).

It sits in Testing & QA, covering Game assets and audio, Caching and Unit testing. It works with webpack, Next.js and Jest. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.

When your agent uses it

  • Debugging webpack 5 plugins — even if the user doesnt explicitly mention best practices — anytime an apply(compiler) method is being written
  • Hooks are being tapped
  • A plugin imports from webpack-sources
  • The rules in this skill apply

Example prompts

  • “t explicitly mention”
  • “/webpack-plugin-authoring”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Hook Selection & Tap Patterns (CRITICAL)
  2. Asset Pipeline (CRITICAL)
  3. Caching & Watch Mode (HIGH)
  4. Plugin Lifecycle & State (HIGH)
  5. Schema & Options Validation (MEDIUM-HIGH)
  6. Errors, Warnings & Logging (MEDIUM-HIGH)
  7. Performance & Parallelism (MEDIUM)
  8. Compatibility & Packaging (LOW-MEDIUM)

What it can do on your machine

Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Webpack Plugin Authoring loads about 2.7k tokens when it runs, and up to ~41k if it reads all its reference files. Until then it costs about 246 tokens; SKILL.md has 679 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~246
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~41k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 679 words, ~2,669 tokens.

Download SKILL.mdSave it as .claude/skills/webpack-plugin-authoring/SKILL.md (or your agent's skills folder). This skill also uses 48 other files; get the full folder from GitHub.
name
webpack-plugin-authoring
description
Writing webpack 5 plugins — hook selection (compiler vs compilation, tap vs tapAsync, processAssets stages), the asset pipeline (emitAsset, source classes, info metadata, source maps), watch-mode and persistent caching (file/context/missing/buildDependencies), plugin lifecycle (constructor purity, multi-compiler isolation, shutdown cleanup), schema-utils validation, WebpackError reporting, jest-worker parallelism, and compatibility patterns (compiler.webpack namespace, peerDependencies, getCompilationHooks WeakMap). Patterns are drawn from production plugins like mini-css-extract-plugin, terser-webpack-plugin, compression-webpack-plugin, and Next.js's webpack plugins. Trigger when writing, reviewing, or debugging webpack 5 plugins — even if the user doesn't explicitly mention "best practices" — anytime an `apply(compiler)` method is being written, hooks are being tapped, or a plugin imports from `webpack-sources`, the rules in this skill apply.

dot-skills Webpack 5 Plugins Best Practices

Comprehensive guide for writing correct, performant webpack 5 plugins. Contains 44 rules across 8 categories (8 hook + 7 asset + 5 cache + 5 life + 4 schema + 5 diag + 5 perf + 5 compat = 44), ordered by the authoring lifecycle: hook choice is the foundation, then asset manipulation, then caching/watch-mode correctness, then lifecycle hygiene, then user-facing concerns (schema validation, error reporting), then performance, then packaging.

Patterns are derived from webpack/webpack, the webpack-contrib plugin suite (mini-css-extract, terser, compression, copy, css-minimizer), and Next.js's webpack integration in vercel/next.js.

When to Apply

Reference these rules whenever:

  • Writing a new plugin (defining apply(compiler), picking which hook to tap)
  • Reviewing existing plugin code for correctness or performance
  • Debugging "why isn't my plugin's output showing up" — usually a hook/stage mismatch
  • Adding asset manipulation logic (processAssets, emitAsset, updateAsset)
  • Fixing watch-mode staleness or persistent-cache poisoning
  • Migrating a plugin from webpack 4 to webpack 5 (or supporting both)
  • Publishing a plugin to npm (export shape, peerDependencies, schema)

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Hook Selection & Tap PatternsCRITICALhook-
2Asset PipelineCRITICALasset-
3Caching & Watch ModeHIGHcache-
4Plugin Lifecycle & StateHIGHlife-
5Schema & Options ValidationMEDIUM-HIGHschema-
6Errors, Warnings & LoggingMEDIUM-HIGHdiag-
7Performance & ParallelismMEDIUMperf-
8Compatibility & PackagingLOW-MEDIUMcompat-

Quick Reference

1. Hook Selection & Tap Patterns (CRITICAL)
2. Asset Pipeline (CRITICAL)
3. Caching & Watch Mode (HIGH)
Show full SKILL.md (294 more words)Show less
4. Plugin Lifecycle & State (HIGH)
5. Schema & Options Validation (MEDIUM-HIGH)
6. Errors, Warnings & Logging (MEDIUM-HIGH)
7. Performance & Parallelism (MEDIUM)
8. Compatibility & Packaging (LOW-MEDIUM)

How to Use

When writing or reviewing plugin code, scan AGENTS.md for the relevant category, then read the individual rule file for the full pattern and rationale.

Reference Files

FileDescription
references/_sections.mdCategory definitions, impact levels, descriptions
assets/templates/_template.mdTemplate for authoring new rules
metadata.jsonVersion, discipline, source references

© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 48 other files (references, assets) in skills/.experimental/webpack-plugin-authoring of pproenca/dot-skills.

  • SKILL.md
  • AGENTS.md
  • assets/templates/_template.md
  • metadata.json
  • references/_sections.md
  • references/asset-buffer-not-source-for-binary.md
  • references/asset-content-hash-via-output-options.md
  • references/asset-delete-then-emit-loses-info.md
  • references/asset-emit-asset-not-direct-assignment.md
  • references/asset-preserve-source-maps.md
  • references/asset-set-info-metadata.md
  • references/asset-source-from-compiler-webpack.md
  • references/cache-add-file-dependencies.md
  • references/cache-build-dependencies-for-persistent-cache.md
  • references/cache-context-dependencies-for-directories.md
  • references/cache-missing-dependencies-for-optional-files.md
  • references/cache-use-input-file-system.md
  • references/compat-custom-hooks-via-weakmap.md
  • … and 31 more

Open the folder on GitHubat commit cf93c57

Compare with similar skills

Webpack Plugin Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Webpack Plugin Authoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Webpack Plugin Authoring this skillpproenca/dot-skills214—~2.7kAutomated safety check: PassMIT
Menu Testing Ssrasmyshlyaev177/react-horizontal-scrolling-menu790—~3.5kAutomated safety check: PassMIT
Senior QAalirezarezvani/claude-skills28k1 repos~2.1kAutomated safety check: PassMIT
Tech Trend Watchmizchi/skills356—~1.8kAutomated safety check: PassNone
Senior QAborghei/Claude-Skills874—~1.6kAutomated safety check: PassMIT
Nextjs TestingHoangNguyen0403/agent-skills-standard570—~768Automated safety check: PassMIT

Similar skills

  • Menu Testing Ssr

    asmyshlyaev177/react-horizontal-scrolling-menu

    Server rendering and testing for react-horizontal-scrolling-menu: the library is client-only ('use client' required in React Server Components, else "createContext is not a function"), SSR first…

    790 GitHub stars~3.5k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Senior QA

    alirezarezvani/claude-skills

    Generates unit tests, integration tests, and E2E tests for React/Next.js applications.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed
  • Tech Trend Watch

    mizchi/skills

    Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority.

    356 GitHub stars~1.8k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Senior QA

    borghei/Claude-Skills

    Testing for React/Next.js with Jest, React Testing Library, and Playwright.

    874 GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Nextjs Testing

    HoangNguyen0403/agent-skills-standard

    Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects.

    570 GitHub stars~768 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Typescript Rules

    softspark/ai-toolkit

    TypeScript/JavaScript coding rules: style, patterns, security, testing.

    179 GitHub stars~2.7k tokensUpdated today
    Testing & QAAuto-check: notes

More from pproenca/dot-skills

All 182 skills in this repo
  • Audio Voice Recovery

    pproenca/dot-skills

    Audio forensics and voice recovery guidelines for CSI-level audio analysis.

    214 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Codemod React Pipeline

    pproenca/dot-skills

    Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.

    214 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Dev Rfc

    pproenca/dot-skills

    Create well-structured RFCs and technical proposals for software projects.

    214 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Dx Harness

    pproenca/dot-skills

    Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.

    214 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Language Spec Author

    pproenca/dot-skills

    Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…

    214 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Python Pep Author

    pproenca/dot-skills

    Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…

    214 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Webpack Plugin Authoring

What does Webpack Plugin Authoring do?

Writing webpack 5 plugins — hook selection (compiler vs compilation, tap vs tapAsync, processAssets stages), the asset pipeline (emitAsset, source classes, info metadata, source maps), watch-mode…. Webpack Plugin Authoring is an agent skill from pproenca/dot-skills.

When should I use Webpack Plugin Authoring?

Webpack Plugin Authoring fits situations like: debugging webpack 5 plugins — even if the user doesnt explicitly mention best practices — anytime an apply(compiler) method is being written; hooks are being tapped; A plugin imports from webpack-sources; the rules in this skill apply.

How do I install Webpack Plugin Authoring in Claude Code?

Run `npx skills add pproenca/dot-skills --skill webpack-plugin-authoring -a claude-code`. Or copy the skill folder (skills/.experimental/webpack-plugin-authoring in pproenca/dot-skills) into .claude/skills/webpack-plugin-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Webpack Plugin Authoring in Codex?

Run `npx skills add pproenca/dot-skills --skill webpack-plugin-authoring -a codex`. Or copy the skill folder (skills/.experimental/webpack-plugin-authoring in pproenca/dot-skills) into .agents/skills/webpack-plugin-authoring in your project. Codex loads it when a task matches its description.

Can I use Webpack Plugin Authoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill webpack-plugin-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/webpack-plugin-authoring, .gemini/skills/webpack-plugin-authoring, .github/skills/webpack-plugin-authoring and .opencode/skills/webpack-plugin-authoring in your project.

What does Webpack Plugin Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: Webpack Plugin Authoring is instructions for the agent only.

Does Webpack Plugin Authoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Webpack Plugin Authoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Webpack Plugin Authoring use?

Webpack Plugin Authoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Webpack Plugin Authoring use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 38k tokens, read only when the agent opens those files.

What are the alternatives to Webpack Plugin Authoring?

Skills that share tags, products or a category with Webpack Plugin Authoring: Menu Testing Ssr (asmyshlyaev177/react-horizontal-scrolling-menu, 790 stars), Senior QA (alirezarezvani/claude-skills, 28k stars), Tech Trend Watch (mizchi/skills, 356 stars) and Senior QA (borghei/Claude-Skills, 874 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Webpack Plugin Authoring?

pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.

Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.