Skip to content
Back to skills

Frontend Quality Bar

ASecurity

Enforce a high-quality, production-ready standard for changes in this Next.js + Chakra UI frontend repo. Use for UX polish, accessibility, performance, error/loading states, code hygiene, and “ready to merge” checks (lint/format/build).

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 8, 2026
developmentnextjsdebuggingfrontendperformance

Works with

  • cursor

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill frontend-quality-bar --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Frontend Quality Bar?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Frontend Quality Bar
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-frontend-quality-bar/badge)](https://www.skillsdirectory.com/skills/majiayu000-frontend-quality-bar)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: frontend-quality-bar
description: Enforce a high-quality, production-ready standard for changes in this Next.js + Chakra UI frontend repo. Use for UX polish, accessibility, performance, error/loading states, code hygiene, and “ready to merge” checks (lint/format/build).
---

# Frontend Quality Bar (Stacked Poker)

## Always start here

1. Read `.cursor/rules/frontend-guidelines.mdc` (project expectations).
2. Identify the user-facing surface (page/component) and list required states:
   - loading, empty, error, success
3. Prefer small, incremental changes; avoid broad refactors unless requested.

## Definition of done (minimum)

- UI has loading/error handling for async work that affects UX.
- No console errors in normal flows; logs are purposeful for debugging only.
- Accessibility basics: labels, keyboard access, focus visibility.
- Responsive: works in both portrait/landscape where applicable.
- Styling uses theme tokens/semantic tokens (no random hexes).

## Commands

- `npm run lint`
- `npm run build`
- `npm run format` (when touching many files)

For convenience, run `scripts/quality.sh` from this skill.

## What to load next

- For a detailed PR checklist: read `references/checklist.md`.
- For perf/a11y patterns that match this repo: read `references/perf-a11y.md`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.