React Best Practices
ryokun6/ryos
React performance optimization guidelines from Vercel Engineering (vercel-labs/agent-skills).
A skill your agent uses whenever you face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets, forbidden architectural…
Install Webpack Plugin Recipes
$ npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills webpack-plugin-recipes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-recipes .claude/skills/webpack-plugin-recipes && rm -rf skills-srcUse ~/.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/
Install the "webpack-plugin-recipes" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipes into .claude/skills/webpack-plugin-recipes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webpack-plugin-recipes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills webpack-plugin-recipes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/webpack-plugin-recipes .agents/skills/webpack-plugin-recipes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "webpack-plugin-recipes" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipes into .agents/skills/webpack-plugin-recipes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webpack-plugin-recipes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills webpack-plugin-recipes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/webpack-plugin-recipes .cursor/skills/webpack-plugin-recipes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "webpack-plugin-recipes" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipes into .cursor/skills/webpack-plugin-recipes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webpack-plugin-recipes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/webpack-plugin-recipes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills webpack-plugin-recipes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/webpack-plugin-recipes .gemini/skills/webpack-plugin-recipes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "webpack-plugin-recipes" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipes into .gemini/skills/webpack-plugin-recipes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webpack-plugin-recipes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills webpack-plugin-recipesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/webpack-plugin-recipes .github/skills/webpack-plugin-recipes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "webpack-plugin-recipes" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipes into .github/skills/webpack-plugin-recipes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webpack-plugin-recipes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills webpack-plugin-recipes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/webpack-plugin-recipes .opencode/skills/webpack-plugin-recipes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "webpack-plugin-recipes" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/webpack-plugin-recipes into .opencode/skills/webpack-plugin-recipes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webpack-plugin-recipes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
webpack-plugin-recipes- GitHub stars
- 214
- Token cost
- ~2k tokens
- SKILL.md length
- 620 words
- Files
- 31 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses whenever you face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets, forbidden architectural…
- Works in 6 steps: Build-time Guardrails (CRITICAL) → Build Metadata & Manifests (HIGH) → Virtual Modules & Codegen (HIGH) → …
- You face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets
- SKILL.md covers When to Apply, Recipe 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 Recipes is an agent skill from pproenca/dot-skills. Use whenever you face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets, forbidden architectural imports, env-var validation, secret-leak prevention, build-info injection, asset manifests, license walking, SRI hashes, virtual modules (Vite-style), filesystem routing (Next.js-style), generated barrels, runtime-driven TS types, library replacement (react→preact), debug-stripping, conditional polyfills, dynamic banners, feature flags…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 33 other files, including reference files and assets (for example `AGENTS.md`, `assets/templates/_template.md` and `metadata.json`).
It sits in Frontend & Design, covering Web performance. It works with webpack, Next.js, Storybook and Vite. 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
- You face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets
- Forbidden architectural imports
- Env-var validation
- Secret-leak prevention
Example prompts
- “/webpack-plugin-recipes”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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 Recipes loads about 2k tokens when it runs, and up to ~55k if it reads all its reference files. Until then it costs about 250 tokens; SKILL.md has 620 words of instructions outside code blocks.
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). 620 words, ~1,953 tokens.
Download SKILL.mdSave it as
.claude/skills/webpack-plugin-recipes/SKILL.md (or your agent's skills folder). This skill also uses 30 other files; get the full folder from GitHub.- name
- webpack-plugin-recipes
- description
- Use whenever you face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets, forbidden architectural imports, env-var validation, secret-leak prevention, build-info injection, asset manifests, license walking, SRI hashes, virtual modules (Vite-style), filesystem routing (Next.js-style), generated barrels, runtime-driven TS types, library replacement (react→preact), debug-stripping, conditional polyfills, dynamic banners, feature flags, build-duration regression tracking, desktop/Slack notifications, changed-chunks diffing, browser auto-open, gzip/brotli pre-compression, image optimization, type-based dist layout, empty-chunk cleanup, cache-busting query strings. Each recipe is a complete working plugin drawn from production patterns at Next.js, Storybook, webpack-contrib. Trigger when the user asks how to do X with webpack or whether a plugin exists for X. Companion to webpack-plugin-authoring.
dot-skills Webpack 5 Plugins Best Practices
Cookbook of 26 production-shaped webpack 5 plugins, organized by the problem they solve. Each recipe starts with a clearly defined problem statement ("here's what hurts without this"), shows the naive non-plugin approach, then provides a complete working plugin (60-150 lines) with explanation, variations, and "when NOT to use" guidance.
Companion to webpack-plugin-authoring — authoring teaches how to write any plugin correctly; recipes teach which plugin to write for a specific pain point. Recipes cross-reference the authoring rules they apply.
When to Apply
Reference these recipes whenever:
- A team has a recurring build-time problem that "feels like it should be a plugin" (architecture rules, secret leak prevention, asset organization)
- You need to integrate webpack output with downstream systems (SSR servers, CDNs, monitoring)
- You're considering whether to write your own plugin OR adopt an existing one — these recipes show the underlying pattern so you can judge fit
- Migrating from another bundler and need to recreate framework-style features (filesystem routing, virtual modules)
- Onboarding new engineers to webpack plugin authoring — recipes give realistic, end-to-end examples
Recipe Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Build-time Guardrails | CRITICAL | guard- |
| 2 | Build Metadata & Manifests | HIGH | meta- |
| 3 | Virtual Modules & Codegen | HIGH | virtual- |
| 4 | Code Transformation | MEDIUM-HIGH | transform- |
| 5 | Developer Experience | MEDIUM | dx- |
| 6 | Asset Pipeline | MEDIUM | assets- |
Quick Reference
1. Build-time Guardrails (CRITICAL)
guard-bundle-budget— Fail builds when initial JS exceeds a per-entry gzipped budgetguard-forbidden-imports— Fail builds when forbidden imports cross architectural boundariesguard-required-env-vars— Fail builds when required environment variables are missingguard-no-secrets-bundled— Fail builds when secret-shaped strings leak into client bundles
2. Build Metadata & Manifests (HIGH)
meta-inject-build-info— Inject__COMMIT__/__BUILD_TIME__into source via DefinePlugin + emitbuild-info.jsonmeta-asset-manifest— Emit chunk-grouped manifest mapping logical names → hashed filenamesmeta-license-notice— GenerateLICENSES.txtby walking the module graph (notnode_modules/)meta-sri-manifest— Compute SHA-384 SRI hashes per asset for CSP compliance
3. Virtual Modules & Codegen (HIGH)
virtual-module-from-memory— Resolvevirtual:Ximports to in-memory strings (Vite-style)virtual-routes-from-filesystem— Generate route map frompages/directory (Next.js-style)virtual-barrel-from-directory— Auto-generate barrel re-exports from a directoryvirtual-types-from-runtime— Emit.d.tsfrom runtime data (config files, JSON schemas)
4. Code Transformation (MEDIUM-HIGH)
transform-replace-library— Replacereactwithpreact/compatat resolve (with subpath handling)transform-strip-debug-helpers— StripdevAssert()/devLog()calls + dev-only imports from productiontransform-conditional-polyfill— Inject only the polyfills target browsers actually need (browserslist + core-js-compat)transform-banner-with-dynamic-content— Per-chunk banners with current year, version, git committransform-define-from-config— DriveDefinePluginsubstitutions from aflags/staging.json-style file
Show full SKILL.md (228 more words)Show less
5. Developer Experience (MEDIUM)
dx-build-duration-report— Persist build durations, warn when current build is >30% slower than mediandx-notify-on-done— Desktop notification (local) + Slack webhook (CI) on build completedx-diff-changed-chunks— Print only the chunks that actually changed between rebuildsdx-open-browser-on-first-build— Open the dev-server URL AFTER first successful build (not before)
6. Asset Pipeline (MEDIUM)
assets-pre-compress-gzip-brotli— Emit.gz/.brsiblings for CDN-served pre-compressionassets-optimize-images— Optimize PNG/JPEG with imagemin + cache reuse across rebuildsassets-route-by-type— Organize emitted assets intojs//css//img//fonts/subdirectoriesassets-skip-empty-chunks— Delete the 0-byte chunks webpack/splitChunks/mini-css emit unnecessarilyassets-add-cache-busting-query— Append?v=<hash>to references of fixed-name assets (manifest.json, sw.js)
How to Use
When the user describes a webpack problem (or asks for a plugin):
- Identify the problem category (guardrail? metadata? codegen? transformation? dx? asset?)
- Open the matching recipe file — read the Problem section first to confirm it's the right recipe
- Use the Plugin section as a working starting point — adapt to the project's specifics
- Read How it works for the WHY behind each design choice (cross-references the authoring rules)
- Check Variations for common adaptations and When NOT to use to confirm the fit
For learning plugin authoring patterns more broadly, pair with the webpack-plugin-authoring skill — its 44 rules teach the underlying APIs every recipe in this skill applies.
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and impact levels |
| assets/templates/_template.md | Template for authoring new recipes |
| metadata.json | Version and 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 30 other files (references, assets) in skills/.experimental/webpack-plugin-recipes of pproenca/dot-skills.
- SKILL.md
- AGENTS.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/assets-add-cache-busting-query.md
- references/assets-optimize-images.md
- references/assets-pre-compress-gzip-brotli.md
- references/assets-route-by-type.md
- references/assets-skip-empty-chunks.md
- references/dx-build-duration-report.md
- references/dx-diff-changed-chunks.md
- references/dx-notify-on-done.md
- references/dx-open-browser-on-first-build.md
- references/guard-bundle-budget.md
- references/guard-forbidden-imports.md
- references/guard-no-secrets-bundled.md
- references/guard-required-env-vars.md
- … and 13 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Webpack Plugin Recipes 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Webpack Plugin Recipes this skillpproenca/dot-skills | 214 | — | ~2k | Automated safety check: Pass | MIT | |
| React Best Practicesryokun6/ryos | 1.3k | — | ~2k | Automated safety check: Pass | MIT | |
| Senior Frontendalirezarezvani/claude-skills | 28k | 5 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Frontend Engineer Workflownanocoai/nanoclaw | 31k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Igniteui Wc Optimize Bundle SizeIgniteUI/igniteui-webcomponents | 170 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Senior Frontendborghei/Claude-Skills | 874 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Senior Frontend
alirezarezvani/claude-skills
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications.
Frontend Engineer Workflow
nanocoai/nanoclaw
Sets a build, test and verify routine for web projects: write typed, accessible code and never call work done until it is checked in a real browser with screenshots.
Igniteui Wc Optimize Bundle Size
IgniteUI/igniteui-webcomponents
Reduce application bundle size with Ignite UI Web Components by registering only needed components via named imports from the package root with defineComponents instead of defineAllComponents…
Senior Frontend
borghei/Claude-Skills
Frontend development for React, Next.js, TypeScript, and Tailwind CSS.
Phy Bundle Size Audit
LeoYeAI/openclaw-master-skills
JavaScript bundle size auditor and budget enforcer. An agent skill from LeoYeAI/openclaw-master-skills.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
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…
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…
Related
Categories
Questions about Webpack Plugin Recipes
What does Webpack Plugin Recipes do?
A skill your agent uses whenever you face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets, forbidden architectural…. Webpack Plugin Recipes is an agent skill from pproenca/dot-skills.
When should I use Webpack Plugin Recipes?
Webpack Plugin Recipes fits situations like: you face a webpack-build problem that ends with needing to write a plugin — 26 production-shaped recipes covering bundle-size budgets; forbidden architectural imports; env-var validation; secret-leak prevention.
How do I install Webpack Plugin Recipes in Claude Code?
Run `npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a claude-code`. Or copy the skill folder (skills/.experimental/webpack-plugin-recipes in pproenca/dot-skills) into .claude/skills/webpack-plugin-recipes in your project. Claude Code loads it when a task matches its description.
How do I install Webpack Plugin Recipes in Codex?
Run `npx skills add pproenca/dot-skills --skill webpack-plugin-recipes -a codex`. Or copy the skill folder (skills/.experimental/webpack-plugin-recipes in pproenca/dot-skills) into .agents/skills/webpack-plugin-recipes in your project. Codex loads it when a task matches its description.
Can I use Webpack Plugin Recipes 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-recipes -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-recipes, .gemini/skills/webpack-plugin-recipes, .github/skills/webpack-plugin-recipes and .opencode/skills/webpack-plugin-recipes in your project.
What does Webpack Plugin Recipes need to run?
SKILL.md names no scripts, command-line tools or credentials: Webpack Plugin Recipes is instructions for the agent only.
Does Webpack Plugin Recipes 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 Recipes 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 Recipes use?
Webpack Plugin Recipes 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 Recipes use?
About 2k tokens (SKILL.md is roughly 7.8k 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 53k tokens, read only when the agent opens those files.
What are the alternatives to Webpack Plugin Recipes?
Skills that share tags, products or a category with Webpack Plugin Recipes: React Best Practices (ryokun6/ryos, 1.3k stars), Senior Frontend (alirezarezvani/claude-skills, 28k stars), Frontend Engineer Workflow (nanocoai/nanoclaw, 31k stars) and Igniteui Wc Optimize Bundle Size (IgniteUI/igniteui-webcomponents, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Webpack Plugin Recipes?
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.