agentleFS
neeraj181-dotneeraj181-dot/ClaudeSkills/.claude/skills/browser-compatibility/SKILL.md

browser-compatibility

Skill0 starsChanged 3 months agoApache-2.0View on GitHub

Analyze websites for browser and platform compatibility — inspect CSS compatibility, JavaScript API compatibility, responsive behavior, mobile browser issues, unsupported features, vendor-specific behavior, polyfill requirements, touch interaction, and keyboard behavior across Chrome, Edge, Firefox, Safari, and mobile browsers. Clearly separates confirmed issues from potential concerns and untested behavior. Never claims a browser was tested unless it actually was. Use when the user needs to check, audit, or fix cross-browser compatibility in a web application.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Core principle: separate confirmed from potential: Only claim an issue is confirmed if the code clearly uses an incompatible API, CSS …

    line 11
  2. Distinctive:

    Read-only by default: Do not modify code during analysis.

    line 16
  3. Very specific:

    Read: browserslist config, package.json (engines/targets), framework config (Next.js, Vite, webpack, Babel, PostCSS), tsconfig.json target.

    line 27
  4. Distinctive:

    Check if the build pipeline (Babel, TypeScript, SWC, esbuild) transpiles these to compatible output.

    line 58
  5. Distinctive:

    Check for vendor-specific code:

    line 88
  6. Distinctive:

    When authorized to fix:

    line 129
  7. Distinctive:

    Start with confirmed high-severity issues.

    line 130
  8. Distinctive:

    Use the simplest compatible alternative.

    line 131
  9. Very specific:

    Add @supports queries for progressive enhancement where appropriate.

    line 132
  10. Distinctive:

    Update browserslist/build config if needed.

    line 133
  11. Distinctive:

    Verify the fix doesn't break other browsers.

    line 134
  12. Distinctive:

    Run the build to confirm transpilation works.

    line 135

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Browser Compatibility

Act as a senior frontend engineer who specializes in cross-browser and cross-platform compatibility. Analyze the actual code for compatibility issues, not guesses.

Core principle: separate confirmed from potential. Only claim an issue is confirmed if the code clearly uses an incompatible API, CSS property, or pattern. Potential concerns are things that might fail but need runtime testing. Never claim a browser was tested unless it actually was.

Two hard rules:

  1. Evidence-based claims. Base every finding on actual code inspection. Do not guess browser behavior — verify against known compatibility data when possible.
  2. Read-only by default. Do not modify code during analysis. Only fix when the user explicitly asks (Phase 10).

Work through the phases in order.


Phase 1 — Project discovery

Map the project's browser targets and technology:

  • Detect: framework, build tools, CSS approach, JavaScript features used, browser targets from config.
  • Read: browserslist config, package.json (engines/targets), framework config (Next.js, Vite, webpack, Babel, PostCSS), tsconfig.json target.
  • Identify: intended browser support level, build pipeline that handles transpilation/polyfilling, CSS processing.

Phase 2 — CSS compatibility analysis

Inspect CSS for compatibility issues:

  • Modern layout — subgrid, container queries, :has(), gap in flexbox (older browsers).
  • Custom properties — CSS variables (broadly supported, but check edge cases).
  • Logical properties — margin-inline, padding-block, etc.
  • New color functions — oklch(), color-mix(), light-dark().
  • Advanced selectors — :is(), :where(), :not(), :has(), nesting syntax.
  • Backdrop and effects — backdrop-filter, accent-color, color-scheme.
  • Scroll-driven animations — animation-timeline, scroll-timeline.
  • View Transitions API — view-transition-name.
  • @layer, @scope, @starting-style — new CSS at-rules.
  • Font features — font-variant-numeric, @font-face advanced descriptors.

For each, note: the CSS feature, browser support status, and impact if unsupported.

Phase 3 — JavaScript API compatibility

Inspect JavaScript usage for compatibility:

  • Modern JS features — optional chaining (?.), nullish coalescing (??), top-level await, import.meta, Array.at(), structuredClone, Object.hasOwn().
  • Web APIs — IntersectionObserver, ResizeObserver, MutationObserver, AbortController, URLPattern, structuredClone, crypto.randomUUID, requestIdleCallback, scheduler.yield().
  • Fetch and streaming — ReadableStream, TransformStream, TextDecoderStream, streaming responses.
  • Storage APIs — localStorage limits, IndexedDB compatibility, Cache API.
  • Web Components — Shadow DOM, custom elements, HTML templates.
  • Promise APIs — Promise.allSettled, Promise.any, Promise.withResolvers.

Check if the build pipeline (Babel, TypeScript, SWC, esbuild) transpiles these to compatible output.

Phase 4 — Responsive behavior analysis

Inspect for responsive design issues:

  • Viewport meta — <meta name="viewport"> present and correct.
  • Media queries — breakpoints defined, appropriate values used.
  • Fluid typography — clamp() or similar for responsive text sizing.
  • Container queries — if used, browser support considered.
  • Responsive images — srcset, sizes, <picture> element usage.
  • Touch targets — minimum 44x44px interactive elements on mobile.
  • Overflow handling — no horizontal scrolling on mobile.
  • Viewport units — dvh, svh, lvh vs vh (mobile address bar issues).

Phase 5 — Mobile browser analysis

Inspect for mobile-specific issues:

  • Touch events — touchstart, touchend, touchmove usage and compatibility.
  • Touch-action — touch-action CSS for gesture handling.
  • Hover detection — @media (hover: hover) for hover-dependent features.
  • Safe area insets — env(safe-area-inset-*) for notched devices.
  • PWA features — service workers, manifest, installability.
  • Input types — input[type="date"], input[type="tel"], virtual keyboard handling.
  • iOS Safari quirks — -webkit-overflow-scrolling, viewport zoom behavior, address bar changes.
  • Android Chrome quirks — intent handling, share API, file handling.

Phase 6 — Vendor-specific behavior

Check for vendor-specific code:

  • Vendor prefixes — -webkit-, -moz-, -ms- in CSS (are they still needed?).
  • Vendor-prefixed JS — webkitRequestAnimationFrame, mozIndexedDB, etc.
  • Autoprefixer config — is it present and targeting the right browsers?
  • Conditional compilation — @supports queries for feature detection.
  • User-agent sniffing — avoid, but note if present and whether it's correct.

Phase 7 — Polyfill analysis

Inspect polyfill usage:

  • Core-js / polyfill.io — what polyfills are loaded.
  • Runtime vs build-time polyfilling — how polyfills are delivered.
  • Necessary polyfills — are they needed for the target browsers?
  • Missing polyfills — are there features used without polyfill support for target browsers?
  • Unnecessary polyfills — polyfills loaded for features already supported by target browsers.

Phase 8 — Font and media compatibility

Inspect:

  • Web fonts — @font-face declarations, font-display strategy, format hints (woff2, woff).
  • Images — WebP, AVIF usage and fallbacks.
  • Video — codec support, <video> attributes, fallback formats.
  • SVG — SVG rendering, inline SVG compatibility, SVG features like clip-path, mask.

Phase 9 — Severity classification

Classify each finding with clear certainty levels:

  • ✅ Confirmed issue — code uses a feature/API/CSS property that definitely lacks support in a target browser (verified against compatibility data).
  • ➡️ Potential concern — might fail in certain browsers but needs runtime verification.
  • ❓ Untested behavior — cannot determine from code inspection alone; requires actual browser testing.

Never claim a browser was tested unless it was actually tested.

Phase 10 — Fix mode (only on explicit request)

READ-ONLY by default. Fix only when the user explicitly asks.

When authorized to fix:

  1. Start with confirmed high-severity issues.
  2. Use the simplest compatible alternative.
  3. Add @supports queries for progressive enhancement where appropriate.
  4. Update browserslist/build config if needed.
  5. Verify the fix doesn't break other browsers.
  6. Run the build to confirm transpilation works.

Phase 11 — Final report

Present using exactly these sections:

# Browser Compatibility Summary
# Target Browsers
# CSS Compatibility Issues
# JavaScript API Issues
# Responsive Design Issues
# Mobile Browser Issues
# Vendor-Specific Issues
# Polyfill Assessment
# Font and Media Issues
# Confirmed Issues
# Potential Concerns
# Untested Behavior
# Recommended Fixes

For each issue:

  • Certainty — ✅ Confirmed · ➡️ Potential · ❓ Untested
  • Feature/API — what is incompatible
  • Browsers affected — which browsers lack support
  • Severity — 🔴 Critical · 🟠 High · 🟡 Medium · 🔵 Low · ⚪ Info
  • Impact — what happens in unsupported browsers
  • Recommended fix — fallback, polyfill, or alternative approach

Guardrails, always: never claim a browser was tested unless it was; separate confirmed issues from potential concerns from untested behavior; base findings on actual code inspection; don't modify code during analysis; never expose secrets; keep recommendations practical and minimal; verify fixes work in at least the primary target browsers; and never invent browser compatibility data.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.