What problem does it solve? Built frontend artifacts often hide routes, API endpoints, and feature flags inside minified bundles, chunk registries, and source maps, making it hard to understand what code actually executes at runtime. This Skill provides a structured workflow to map the served artifact set, trace loader flow, and recover hidden functionality from emitted assets during CTF sandbox engagements. ## Core Features & Use Cases - Served Artifact Mapping: Records entry HTML, script tags, build manifests, chunk registries, and source map URLs while keeping filenames, hash suffixes, and route ownership tied together. - Runtime Structure Reconstruction: Follows bootstrap code, chunk loaders, module registries, and string decoders to recover route names, API calls, feature flags, and hidden panels. - Decisive Path Reduction: Compresses findings into the smallest asset-to-runtime sequence proving which bundle path executes, separating served artifact truth from repository source. - Use Case: During a CTF web challenge, use this Skill to trace an obfuscated webpack loader, recover a hidden admin route from a lazy chunk, and prove the exact bundle path that triggers it. ## Quick Start Ask the agent to reconstruct the runtime structure of the served JavaScript bundles and recover any hidden routes or API endpoints from the source maps and chunk manifests.
