mix
Skill4 starsChanged 5 months agoMITView on GitHub
Maintain legacy Laravel Mix asset pipelines (webpack.mix.js) — kept only for existing configs. New Laravel apps use Vite; prefer laravel/vite for any new or migrating frontend build. Use when the user must maintain or debug an existing webpack.mix.js Laravel Mix asset pipeline that has not been migrated to Vite; the user needs to fix or explain the `mix()` Blade helper and the mix-manifest.json it reads in a legacy project; the user needs to edit webpack.mix.js chained calls such as mix.js, mix.sass, or mix.version in a legacy build. Keywords: mix, webpack, assets, legacy, laravel.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- btwld/mixtheir own version, first seen Oct 9, 2026
- Prawal-Bhuyan/claude-skillstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- btwld/mix★ 803same name
- Prawal-Bhuyan/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository119 other files it gives its agents.
- strategy-bitrix-d7-incrementalSkill
- strategy-explicit-over-magicSkill
- strategy-framework-conventionsSkill
- strategy-legacy-safe-editsSkill
- strategy-minimal-diffSkill
- strategy-no-untested-refactorSkill
- strategy-preserve-public-apiSkill
- strategy-readonly-immutabilitySkill
- strategy-security-firstSkill
- strategy-test-drivenSkill
- openapiSkill
- paginationSkill
- rest-designSkill
- versioningSkill
- cqrsSkill
- dependency-inversionSkill
- hexagonalSkill
- repository-patternSkill
- service-layerSkill
- bitrixSkill
- findings-reportSkill
- laravelSkill
- performanceSkill
- phpSkill
- project-analysisSkill
- refactoringSkill
- roi-prioritizationSkill
- securitySkill
- stack-detectionSkill
- cache-layersSkill
- component-engineSkill
- d7-eventsSkill
- d7-loaderSkill
- d7-orm-queriesSkill
- iblock-elementsSkill
- kernel-main-moduleSkill
- localizationSkill
- controllersSkill
- ormSkill
- validationSkill
- controllersSkill
- query-builderSkill
- routingSkill
- autoload-psr4Skill
- dependency-managementSkill
- scriptsSkill
- connection-poolingSkill
- mysql-indexingSkill
- redisSkill
- transactionsSkill
- ci-github-actionsSkill
- deployment-strategiesSkill
- docker-phpSkill
- env-configSkill
- associationsSkill
- entities-mappingSkill
- orm-basicsSkill
- entity-apiSkill
- module-developmentSkill
- routing-controllersSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 70
Do not use this skill to design the target Vite setup when migrating away from Mix.
- Distinctive: line 71
Do not use this skill for a new Laravel app or a fresh asset pipeline.
- Very specific: line 89
Run npm run dev for an unminified build while developing and npm run prod for a minified, versioned build on deploy.
- Distinctive: line 103
Not applicable — no I/O, auth, or untrusted input.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- generated: do not edit — source: knowledge/atoms/laravel/mix/ --><!-- schema: atomVersion=3 skillVersion=2 graphVersion=1 --><!-- compile: @php-skills/compiler v1.0.0 (deterministic build) -->Laravel Mix
⚠ Deprecated — superseded by laravel/vite. Laravel Mix is no longer the default; use Vite for asset bundling. Removal planned: 2028-01-15.
When to use
- The user must maintain or debug an existing webpack.mix.js Laravel Mix asset pipeline that has not been migrated to Vite.
- The user needs to fix or explain the
mix()Blade helper and the mix-manifest.json it reads in a legacy project. - The user needs to edit webpack.mix.js chained calls such as mix.js, mix.sass, or mix.version in a legacy build.
When NOT to use
- Do not use this skill to design the target Vite setup when migrating away from Mix; use laravel/vite for the destination pipeline.
- Do not use this skill for a new Laravel app or a fresh asset pipeline; use laravel/vite instead.
Core guidance
- Chain mix.version for cache-busted output — Chain
.version()inwebpack.mix.jsso Mix appends a content hash and writesmix-manifest.json; resolve the file in Blade with themix()helper.
Quick recipe
- In
webpack.mix.js, keep the compile chain (for examplemix.js('resources/js/app.js', 'public/js')andmix.sass(...)) and chain.version()so output is hashed. (verify:npm run prodregeneratespublic/jsandmix-manifest.json) - In the Blade layout, load the compiled assets with
{{ mix('js/app.js') }}and{{ mix('css/app.css') }}so the current hashed paths are resolved. (verify: The rendered page links the hashed files listed in mix-manifest.json)
Best practices
- In Blade, reference compiled assets with
{{ mix('js/app.js') }}so the current hashed path is read frommix-manifest.jsonrather than hardcoding the filename - Run
npm run devfor an unminified build while developing andnpm run prodfor a minified, versioned build on deploy; both invoke Mix via the package scripts
Common mistakes
- mix() throws when the manifest is missing — Calling
mix()before running a build (or without.version()) throws becausemix-manifest.jsondoes not exist. Fix: Runnpm run prod(with.version()chained) so the manifest is generated before the view renders. - Newer Node versions break the aging webpack toolchain — Laravel Mix pins an older webpack stack, so a recent Node.js can fail the build with OpenSSL or loader errors. Fix: Pin a Node version known to work (or set NODE_OPTIONS=--openssl-legacy-provider) for the legacy build, and plan the migration to laravel/vite.
Version notes
- Mix is in maintenance mode from Laravel 9 — From Laravel 9 onward Vite is the scaffolded default and Laravel Mix is in maintenance mode; Laravel 8 shipped Mix by default.
Security
- Not applicable — no I/O, auth, or untrusted input.
Testing
- Activation and decision behavior are verified in
eval/scenarios/laravel/mix.yaml.
Additional resources
- references/core.md
- references/pitfalls.md
- references/recipes.md
- references/version-differences.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

