Skip to main content
skill CX Codex

frontend-testing-debugging · fcakyon — Claude Code skill: debug rendered UI

frontend-testing-debugging guides an agent through visual debugging: reproduce the interaction, inspect console and layout, fix the root rule, rerun the journey that broke.

Apache-2.0 ★ 1,216 updated 2026-11-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install frontend-design-skills@claude-settings
Open on GitHub

What frontend-testing-debugging does

The skill runs the visual diagnosis loop. It makes the agent pin down the entry route, the user action and the visible result, and read repo scripts and running servers before asking you for a URL. Any existing journey covering the change runs first.

Execution reuses project infrastructure. With the QA plugin and its project config in place, runs go through qa:run-qa, which covers session recovery, telemetry isolation and cleanup; qa:setup builds coverage where none exists. Without that, the agent uses the repo's browser or e2e workflow, or a throwaway diagnostic script kept out of committed source. Rendered checks defer to the ui-regression skill when installed.

Reference screenshots are compared at the same state and viewport, desktop and mobile, after media loads. Text that shifts between locales gets traced through translation, formatting, Unicode normalization, casing and CSS, and the fix lands in the owning transformation, not in single characters. A green build says nothing about whether the interaction works: the failing step is repeated and the affected journeys rerun. The agent closes only the tabs and preview servers it opened.

What it helps with

  • debug a layout regression after a component change
  • compare a page against a reference screenshot at the same viewport
  • check console errors and framework overlays before blaming the CSS
  • trace why copy breaks between locales
  • rerun the failing QA journey after a fix

Example prompts for the agent

  • Debug this UI: the cart badge disappears after I remove the last item.
  • Verify the rendered change on mobile and desktop and compare both with the reference screenshots.
  • Run the existing QA journey for checkout and show me where it fails.

How to install frontend-testing-debugging

1Plugin marketplace

/plugin marketplace add fcakyon/claude-codex-settings
/plugin install frontend-design-skills@claude-settings

This installs the whole frontend-design-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add fcakyon/claude-codex-settings --skill frontend-testing-debugging -a claude-code

3Manually: put the files in place

~/.claude/skills/frontend-testing-debugging/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/frontend-testing-debugging/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about frontend-testing-debugging

How do I install frontend-testing-debugging in Claude Code?

Add the marketplace with /plugin marketplace add fcakyon/claude-codex-settings, then install the plugin that ships the skill: /plugin install frontend-design-skills@claude-settings.

What does frontend-testing-debugging do?

It walks the agent through diagnosing a rendered interface: locate the entry route, repeat the broken interaction, read console and layout, make the smallest edit and check the result again on the same steps.

Does it need the QA plugin?

No. The skill works on its own; qa:run-qa and qa:setup come into play only when the QA plugin is installed and the project carries its configuration.

Source text

SKILL.md · Apache-2.0
---
name: frontend-testing-debugging
description: This skill should be used when user asks to "debug this UI", "verify a rendered frontend change", or "check responsive layouts". Diagnose visual and interaction problems, compare reference screenshots, and reuse project QA journeys when available.
---

# Frontend testing and debugging

Own the visual diagnosis and fix loop. Reuse project testing infrastructure for repeatable execution, sessions and reports. This skill works independently of the QA plugin.

## Choose the flow and execution path

1. Identify the entry route, user action and expected visible result. Inspect repository scripts and running servers before asking for a missing URL. Keep the requested host exact.
2. Read project testing guidance and look for an existing journey covering the change. Run that journey first. When the QA plugin and project configuration are available, follow the project's QA skill and use `qa:run-qa` for execution, session recovery, telemetry isolation and cleanup.
3. Without project QA journeys, use the repository's existing browser or e2e workflow. For interactive investigation, choose an available browser tool and read its current instructions. Do not assume a particular plugin or API exists. Respect the user's browser preference and avoid taking focus during background work.
4. If no suitable workflow exists, use a temporary diagnostic script outside committed source. Add dependencies only when required by the task and permitted by the user. Report unavailable access or runtime support as a specific limitation.

Interactive inspection is useful for new visual issues and failed journeys. It does not replace a failing regression with an easier smoke check. Before visiting production, use the project's analytics isolation and test-account rules. If those are absent, prefer a local or staging target for diagnostic traffic.

## Inspect, fix and verify

Confirm the intended URL and meaningful rendered content. Check relevant console errors and framework overlays before diagnosing layout. Exercise the target interaction and observe its result through visible state, navigation or persisted application behavior.

For rendered validation, use the installed `ui-regression` skill when available. It owns state coverage, input contrast, asset density, screenshot inspection and the separate functional, rendered-quality and runtime verdicts. Keep investigation here and reuse the project runner for executable checks.

Without that skill, inspect desktop/mobile screenshots after media loads, exercise typed and cleared inputs, check contrast and asset sharpness at the target display density, and verify the intended surrounding layout across search results and empty states. Keep reference comparisons at matching state and viewport. Mark uninspected visuals as unverified.

When text changes unexpectedly between locales or screens, trace the source value through translation, formatting, Unicode normalization, JavaScript casing and CSS to the rendered result. Inspect inherited `lang`, text direction, font coverage and clipping where relevant. Distinguish translated interface copy from names, titles and identifiers whose spelling must survive presentation. Fix the owning transformation or layout rule instead of replacing individual characters, stripping accents, or forcing the whole page to one language. Use the actual content language for intentional transformations and locale formatting.

Make the smallest relevant edit, reload or rebuild as needed, and repeat the original failing interaction. Rerun affected project journeys. A passing build or root-page screenshot does not prove the interaction works.

Move repeatable discoveries into the existing tracked QA or e2e suite, with assertions on user-visible outcomes. Reuse its helpers instead of adding a second browser/session runner. When the QA plugin is available but the project has no suite, use `qa:setup` if creating repeatable coverage is within the task. Keep one-off diagnostic scripts and generated evidence outside Git.

## Evidence and cleanup

Report findings or verified behavior, the target URL and viewports, evidence supporting the result, and remaining gaps. Include screenshots when they prove visual changes. Distinguish automated journey results from interactive observations. Scale the response to the change rather than filling a fixed report template.

Close only task-created tabs and sessions, stop task-owned preview servers, and reset viewport overrides. Preserve unrelated tabs and saved authentication. Follow the project's evidence storage rules and do not create standalone reports unless requested.

## Related skills

Use `product-ui-design` for product UX, design rules and the desktop, mobile and supported-theme visual handoff. This skill owns browser execution and verification.

Use `openai-frontend-design` for design creation or fidelity to an accepted concept. Use the installed React best-practices skill for relevant React/Next.js changes. Image generation is only needed when the task calls for new or revised visual assets.

© fcakyon · Apache-2.0 · fcakyon/claude-codex-settings

Similar skills

All skills for Testing and QA →

frontend-testing-debugging by other authors comes first.

frontend-testing-debugging official OpenAI frontend-testing-debugging is a Codex skill for testing rendered frontend apps and debugging UI issues. It runs during local app checks, interaction fixes, and visual QA. CX Codex GP ChatGPT +1 159installs dark-mode-testing spencerpauly dark-mode-testing toggles light and dark mode in the browser, screenshots both states, and points out hardcoded colors, invisible text and contrast failures. CX Codex +1 478installs webapp-testing davila7 webapp-testing — a Claude Code command that drives Playwright to test local web applications in a real browser. Covers form interactions, element checks, screenshots, and console log capture. CX Codex +1 259installs frontend-testing-best-practices sergiodxa frontend-testing-best-practices — a set of 6 testing guidelines that prioritizes Playwright E2E workflows over isolated React component tests and heavy mocking. CX Codex +1 2,300installs testing Rudolf S. testing — a skill for writing effective tests: layer-specific mocking rules, failure debugging, flaky test management. CX Codex +1 ★ 587repo stars playwright-visual-testing bradtaylorsf playwright-visual-testing — a skill providing Playwright visual regression testing patterns. Helps agents configure screenshot assertions, mask dynamic elements, and handle responsive snapshots in CI. CX Codex +1 1installs design-taste-frontend Leonxlnx The design-taste-frontend Claude Code skill sets design rules and checks for websites. It activates for new pages, redesigns, and requests to fix a generic-looking site. CX Codex +1 802,600installs

From the same set113

The whole set →
schema A skill for Claude Code and Codex reviews and fixes JSON-LD structured data. It helps choose schema types and trace why a page is not getting a rich result. CX Codex +1 ★ 1,216repo stars python-guidelines python-guidelines — a skill that enforces rules for writing and reviewing Python code: fitting new code into existing patterns, blocking premature abstractions, and standardizing docstrings. CX Codex +1 ★ 1,216repo stars simplify simplify runs four parallel agents to inspect and clean up recent diffs across reuse, complexity, and performance before committing. CX Codex +1 ★ 1,216repo stars navigation-native-navigators navigation-native-navigators is a Claude Code rule that steers React Native navigation toward native components. It covers stacks, tabs, and screen headers. CX Codex +1 ★ 1,216repo stars programmatic-seo programmatic-seo plans scalable template-driven page generation from data sets and protects your project from thin-content deindexing penalties. CX Codex +1 ★ 1,216repo stars ultralytics-platform ultralytics-platform is a Claude Code skill for managing Ultralytics Platform resources, model training, and hosted inference. It activates on requests to upload datasets or models, train in the cloud, or deploy an endpoint. CX Codex +1 ★ 1,216repo stars ultralytics-branding ultralytics-branding loads Ultralytics brand rules: colors, typography, logo specs and tone for PDFs, slides, documents, marketing emails and social posts. CX Codex +1 ★ 1,216repo stars email-design email-design — a skill for Claude Code and Codex that handles transactional email layout. Styles account confirmations, password resets and billing receipts to match your application branding. CX Codex +1 ★ 1,216repo stars

Project sponsors

Companies that keep this analytics open