Provide source maps for production debugging
SkillMediaA skill for auditing slow page loads, heavy assets, or rendering delays related to source maps for production debugging. It guides an agent through verifying the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes, then checking that a project's build generates source maps and handles them correctly for production debugging.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a project with a build process that produces minified code for production.
Then ask your AI: use the Provide source maps for production debugging skill
What your AI can do with it
- Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending ch
- Check whether the build process generates source maps and links them correctly
- Advise uploading source maps to error tracking services such as Sentry instead of serving
- Review routes, assets, and loading behavior, flagging files, requests, or rendering steps
- Explain how source maps let developers debug original source code when only minified code
- Describe the measurement method used to confirm each flagged issue
Getting started
- Have a project with a build process that produces minified code for production.
- Add the skill to the agent's available skills.
- Ask the agent to audit page load performance or source map handling for the project.
- Provide access to DevTools, Lighthouse, or field data so the agent can verify the actual bottleneck before changes are recommended.
- Consult references/rule.md for full implementation details and framework-specific guidance.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/source-maps/SKILL.md and read by ahel’s review.
Source maps are essential for debugging production issues effectively without compromising the performance benefits of minification.
Quick Reference
- Generate source maps to map minified code back to original source
- Upload source maps to error tracking services (e.g., Sentry) instead of serving them publicly
- Ensure source maps are correctly linked in your build process
Check
Verify if the project's build process generates source maps and if they are being correctly handled for production debugging.
Fix
Update the build configuration to generate source maps and integrate with an error tracking service for secure production debugging.
Explain
Explain how source maps enable developers to debug original source code when only minified code is running in the browser.
Code Review
Review the routes, assets, and loading behavior that affect Provide source maps for production debugging. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/performance/source-maps
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What does this skill do?
- It guides an agent through auditing slow page loads, heavy assets, or rendering delays related to source maps, verifying the real bottleneck in DevTools, Lighthouse, or field data before recommending changes.
- Should source maps be served publicly?
- No. The skill recommends uploading source maps to error tracking services such as Sentry instead of serving them publicly, so debugging stays possible without exposing original source.
Advanced
- Item type
- skill
- Key
source-maps- Source
- github.com/thedaviddias/front-end-checklist