just-vibeVite · inspect by default
/vite-chunks
Investigate loading boundaries, duplicated modules, and chunks
Use to change lazy-loading/cache boundaries; vite-bundle first identifies heavy contributors.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select vite-chunks from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv vite-chunks, /just-vibe vite-chunks and /jv:vite-chunks in Claude. See shortcut setup and context examples.
/just-vibe:vite-chunks Find duplicated dependencies and loading-boundary issues in these build artifacts./just-vibe:vite-chunks Split a heavy dashboard while preserving direct deep links and shared vendor initialization./just-vibe:vite-chunks Plan chunks without network traces; report loading benefits as hypotheses.What the agent does
- Map entry points, dynamic imports and shared chunks to representative navigation waterfalls.
- Examine dependency duplication, circular dependencies and cache invalidation against initial-load cost, and propose focused splitting changes.
Inputs
- route/loading behavior, build artifacts, and chunk configuration.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Dynamic imports, shared chunks, duplicate modules, and loading boundaries.
- Writes
- Inspect/plan: inspect or propose; save requested artifacts only. Apply: edit the requested local implementation and perform relevant bounded checks while preserving unrelated work. Live data changes, remote actions and paid jobs require their resolved target and existing session authorization.
- Mode
- Inspect for analysis; apply for a requested split or loading-boundary change. Requires route/loading behavior, build artifacts, and chunk configuration.
- Prerequisites
- Project manifests, lockfile, Vite/framework/plugin versions, and existing build scripts. Verify current version-specific documentation when changing configuration. Requested isolated verification may generate disposable build/cache artifacts; inspect their scripts first and preserve product files.
Expected output
- Chunk and dependency map with the request waterfall, and an optimization plan or, in apply mode, a patch with loading evidence and navigation checks.
How the work is checked
- A split reduces the intended initial work; deep-link and lazy-load paths still resolve all required modules.
When to stop or clarify
- Avoid arbitrary manual chunk rules without evidence. Report missing network traces rather than inventing loading improvements.
Handling missing context
- Infer
- Read manifests, lockfile, installed Vite/plugins, entry points, aliases, modes and current build scripts.
- Assume
- Preserve existing tooling and base-path conventions; in apply mode, make a local focused change when the brief identifies the behavior, and otherwise propose it.
- Ask
- Ask if the intended serving subpath or deployment target cannot be inferred and would change generated URLs; do not ask for versions present in the lockfile.
Technical guidance
- Evidence
- Inspect dynamic imports, shared dependencies, manual chunk rules and module side effects.
- Method
- Split at meaningful usage boundaries and check initialization order and caching across releases.
- Pitfall
- A smaller entry chunk can add serial requests or cause a stale HTML document to reference a deleted old chunk.
- Check
- Test cold navigation, lazy routes and an older open page during deployment; define reload/recovery for missing chunks.
Situational decisions
When manual splitting changes execution order or creates a waterfall: Verify module side effects and route transitions before accepting byte reductions.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.