Devtools

Frontend DevTools audit workflow — Lighthouse/CWV, a11y (axe), network/layout, when checks are MUST vs optional. Use for /test-ui deep passes, "audit performance", "cek Lighthouse", "axe", or verifying UI before ship with tooling evidence.

9 stars 1 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sukirman1901/frontend-expert

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sukirman1901/frontend-expert --skill devtools
Manual install
git clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/devtools ~/.claude/skills/devtools

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# FE DevTools

## Overview

Use browser/tooling evidence when available — don’t invent Lighthouse scores. Pair with `performance`, `accessibility`, and `testing`.

## When to use

- `/test-ui` or ship checks when tooling exists in the project
- User asks for Lighthouse, axe, Network, Layout shift, Coverage
- Design/perf audit needs **measured** Performance or Accessibility scorecard rows
- Verifying no horizontal overflow / focus order with real viewport tools

## When to skip

- No runnable app / static markdown-only change
- User wants theory-only advice with no environment
- Pure token rename with no UI surface

## MUST vs optional

| Check | MUST when | Optional |
|-------|-----------|----------|
| **Responsive viewports** | Layout UI ship (320/768/1024/1440) | — |
| **Keyboard / focus** | Interactive forms, dialogs, drawers | — |
| **axe / a11y scan** | `/test-ui`, `/design` deep, or user asks | Quick source-only audit |
| **Lighthouse / CWV** | Perf ask, public landing, `/design` deep with app running | Tiny internal chrome tweak |
| **Network waterfalls** | Suspected overfetch / huge assets | Default CRUD form |
| **Layout / CLS** | Animations, fonts, images without dimensions | Static settings copy |

**Rule:** Never fabricate scores. If tools didn’t run → scorecard = `not evaluated`.

## Workflow

1. **Confirm target** — URL/route or local preview command
2. **Viewport** — resize or device mode; note Responsive Conventions
Read the full skill on GitHub

Details

Skill name
devtools
Path
skills/devtools/SKILL.md
License
MIT
Repo updated
5 November 2026

FAQ

What does the Devtools skill do?

Frontend DevTools audit workflow — Lighthouse/CWV, a11y (axe), network/layout, when checks are MUST vs optional. Use for /test-ui deep passes, "audit performance", "cek Lighthouse", "axe", or verifying UI before ship with tooling evidence.

How do I install the Devtools 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 Devtools popular?

It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.

Related skills

Accessibility

9

sukirman1901/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.

Frontend & Design

Anti Slop Code

9

sukirman1901/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.

Software Development

Anti Slop Design

9

sukirman1901/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.

Frontend & Design

Engineering Vocabulary

9

sukirman1901/frontend-expert

Name a frontend engineering concept from a loose description. Reverse-lookup for FE technical terms — user describes a pattern informally ("supaya gak fetch ulang", "render cuma yang keliatan"), skill returns the proper name + brief definition. Use when the user uses informal language for a technical concept, or when you need the correct term to pick the right implementation.

Frontend & Design

Design Vocabulary

9

sukirman1901/frontend-expert

Name a design or UI concept from a loose description. Reverse-lookup for design terms — user describes something vaguely ("card floating over blur", "zig-zag layout"), skill returns the proper name + brief definition. Use when the user uses informal language for a UI concept, or when you need the correct term to search references or communicate precisely.

Frontend & Design

Fidelity

9

sukirman1901/frontend-expert

Spec vs implementation fidelity — Figma/Dev Mode/screenshot compare, spacing tolerance, token remap, close-enough rules. Use when matching a design file, "pixel perfect", "mirip Figma", design QA, or /design with a provided mock.

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.