A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.

MITAuto-check passedDevelopment

Install Source Maps

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill source-maps -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist source-maps --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source-maps .claude/skills/source-maps && rm -rf skills-src

Use ~/.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/

Facts

Skill name
source-maps
GitHub stars
74k
Token cost
~445 tokens
SKILL.md length
176 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.

  • Auditing slow page loads
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Rendering delays related to Provide source maps for production debugging

What it does

Source Maps is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

It sits in Development, covering Web performance and Debugging. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Auditing slow page loads
  • Rendering delays related to Provide source maps for production debugging

Example prompts

  • “/source-maps”

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. 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

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    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

Source Maps loads about 445 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 176 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~445
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

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 thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 176 words, ~445 tokens.

Download SKILL.mdSave it as .claude/skills/source-maps/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
source-maps
description
Use when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
metadata.category
performance
metadata.priority
medium
metadata.difficulty
intermediate
metadata.estimatedTime
10
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/performance/source-maps

Provide source maps for production debugging

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/rules/performance/source-maps

© thedaviddias, 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 1 other file (references) in skills/source-maps of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Source Maps 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.

Source Maps compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Source Maps this skillthedaviddias/Front-End-Checklist74k—~445Automated safety check: PassMIT
Electron DevTools Trace Analysiskeybase/client9.3k—~809Automated safety check: PassBSD-3-Clause
Renderdoc GPU Debugrudybear/renderdoc-skill211—~4kAutomated safety check: PassMIT
Runtime DebugOpenHikmah/openhikmah-web181—~618Automated safety check: PassGPL-3.0
Cx Telemetry Queryingcoralogix/cx-cli121—~2.6kAutomated safety check: PassApache-2.0
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0

Similar skills

  • Analyzes Chrome or Electron DevTools Performance trace exports with Python scripts to find where render time actually goes, without opening DevTools.

    9.3k GitHub stars~809 tokensUpdated today
    DevelopmentAuto-check passed
  • Renderdoc GPU Debug

    rudybear/renderdoc-skill

    GPU frame debugging with RenderDoc via rdc-cli. An agent skill from rudybear/renderdoc-skill.

    211 GitHub stars~4k tokensUpdated 7 mo ago
    DevelopmentAuto-check passed
  • Runtime Debug

    OpenHikmah/openhikmah-web

    Debug and verification workflow for runtime-bundle and module-resolution regressions.

    181 GitHub stars~618 tokensUpdated today
    DevelopmentAuto-check passed
  • Cx Telemetry Querying

    coralogix/cx-cli

    A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…

    121 GitHub stars~2.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated yesterday
    Auto-check passed
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated yesterday
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated yesterday
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated yesterday
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated yesterday
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Source Maps

What does Source Maps do?

A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging. Source Maps is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.

When should I use Source Maps?

Source Maps fits situations like: auditing slow page loads; rendering delays related to Provide source maps for production debugging.

How do I install Source Maps in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill source-maps -a claude-code`. Or copy the skill folder (skills/source-maps in thedaviddias/Front-End-Checklist) into .claude/skills/source-maps in your project. Claude Code loads it when a task matches its description.

How do I install Source Maps in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill source-maps -a codex`. Or copy the skill folder (skills/source-maps in thedaviddias/Front-End-Checklist) into .agents/skills/source-maps in your project. Codex loads it when a task matches its description.

Can I use Source Maps 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 thedaviddias/Front-End-Checklist --skill source-maps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/source-maps, .gemini/skills/source-maps, .github/skills/source-maps and .opencode/skills/source-maps in your project.

What does Source Maps need to run?

SKILL.md names no scripts, command-line tools or credentials: Source Maps is instructions for the agent only.

Does Source Maps access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Source Maps 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 Source Maps use?

Source Maps 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 Source Maps use?

About 445 tokens (SKILL.md is roughly 1.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 852 tokens, read only when the agent opens those files.

What are the alternatives to Source Maps?

Skills that share tags, products or a category with Source Maps: Electron DevTools Trace Analysis (keybase/client, 9.3k stars), Renderdoc GPU Debug (rudybear/renderdoc-skill, 211 stars), Runtime Debug (OpenHikmah/openhikmah-web, 181 stars) and Cx Telemetry Querying (coralogix/cx-cli, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Source Maps?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,388 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.