Testing
Test user-facing UI with TDD, component tests, a11y checks, and critical-path coverage. Use when writing or fixing UI tests, verifying loading/error/empty states, or when the user mentions test/TDD/coverage/regresi — including natural language, not only /test-ui.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill testinggit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/testing ~/.claude/skills/testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Frontend Testing ## Overview Prove UI behavior with a lean pyramid: mostly unit/component tests, some integration, few E2E. Prefer Testing Library queries that mirror how users interact. Include accessibility checks for interactive UI. ## When to Use - `/test-ui` or explicit test requests - After `/ui` when the user wants TDD or coverage for a component - Fixing a UI bug (regression test first) ## Workflow 1. **Choose level** - Unit/component (~80%): render, props, states (loading/error/empty) - Integration (~15%): user flows across a few components - E2E (~5%): critical paths only (Playwright/Cypress) 2. **TDD when changing behavior** - Red → Green → Refactor - One behavior per test; name by user-visible outcome 3. **Query priority (Testing Library)** - Prefer: role, label, text - Avoid: test IDs unless no accessible name exists 4. **Must cover for interactive UI** - Default render - Loading / error / empty when those states exist - Primary user action (click/submit) - Keyboard path for custom controls when non-native - **Robustness (when risk is real):** double-submit / spam click, interrupt open→close mid-animation, slow network loading UI 5. **Accessibility in tests** - axe-core (or equivalent) on critical components when tooling exists - Assert accessible names on icon-only controls 6. **Visual regression (optional)** - Storybook + Chromatic/Percy when the project already uses them
Details
- Skill name
testing- Repository
- sukirman1901/frontend-expert
- Path
skills/testing/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Testing skill do?
Test user-facing UI with TDD, component tests, a11y checks, and critical-path coverage. Use when writing or fixing UI tests, verifying loading/error/empty states, or when the user mentions test/TDD/coverage/regresi — including natural language, not only /test-ui.
How do I install the Testing skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Testing popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Ab Test Analysis
9shisuidata/ss-data-skills
Use when designing, checking, or interpreting A/B tests and experiments. Computes significance, confidence intervals, sample ratio mismatch, power, CUPED, and sample size with a bundled zero-dependency script, then judges validity risks, guardrails, and ship/iterate/rollback decisions and renders an HTML experiment report. 中文触发词:A/B 实验、AB 测试、实验解读、显著性、样本量计算、能不能全量。
Quality Loop
9sukirman1901/frontend-expert
Loop UI work until quality gates pass — judge/build, test, audit, fix, repeat. Use for “rapihin sampai bagus”, polish until audit passes, fix Critical/High design findings, or /polish. Do not use for one-shot “rapihin detail”, copy-only rewrites, or “rapikan kode”.
Local Dev Testing
9zllovesuki/cloudflare-agent-skills
Develop and test Cloudflare Workers locally with wrangler dev, Miniflare-compatible bindings, fixtures, integration tests, remote validation, and CI checks. Use when building local development workflows for Workers, D1, Durable Objects, KV, R2, Queues, or Workflows.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.