frontendchecklist

Review frontend code and live pages against the Front-End Checklist (380+ rules for accessibility, performance, SEO, security, HTML, CSS, JavaScript, images, i18n, privacy, testing) using the `frontendchecklist` CLI. Use when writing, reviewing, or shipping HTML/CSS/JS/JSX/TSX/Vue/Svelte/Astro code, before a commit or PR, or when asked to audit a public URL.

Star: 74,442
Category: Frontend & design
License: MIT
Last commit: Oct 6, 2026

Install

Send the text below to Claude Code, Codex or Cursor. The agent reviews the Skill’s contents and installs it after you confirm.

读取 https://funcoding.ai/skills/thedaviddias/front-end-checklist/cli/install.md ，按里面的步骤帮我安装这个 Skill。

Star history

Last 7 days: +76
Last 30 days: +390

74k

Oct 18, 2017Oct 13, 2026

Star history
Oct 18, 2017	1584
Jun 30, 2018	25819
Mar 31, 2019	31555
Dec 31, 2019	34713
Sep 30, 2020	40466
Jun 30, 2021	51441
Mar 31, 2022	55983
Dec 31, 2022	60984
Sep 30, 2023	64083
Jun 30, 2024	66281
Mar 31, 2025	68553
Dec 31, 2025	71187
Jul 18, 2026	73034
Jul 27, 2026	73148
Aug 5, 2026	73270
Aug 14, 2026	73375
Aug 23, 2026	73492
Sep 1, 2026	73911
Sep 10, 2026	74015
Sep 19, 2026	74146
Sep 28, 2026	74260
Oct 7, 2026	74379
Oct 13, 2026	74442

Source repository

thedaviddias/Front-End-Checklist

🗂 The essential checklist for modern web development, for humans and AI agents

View on GitHub Homepage

More Skills in this repo29

See all

packages/cli/SKILL.md

Front-End Checklist CLI

frontendchecklist checks frontend code against the Front-End Checklist rules. It works offline, prints JSON when its output is piped (which is how you will usually call it), and uses exit codes you can branch on.

Run it with npx -y @frontendchecklist/cli <command> if frontendchecklist is not installed.

When to use it

After writing or editing frontend files: frontendchecklist review <paths>.
Before committing: git diff --cached | frontendchecklist review -.
When the user asks to audit a deployed page: frontendchecklist audit https://....
When you need the authoritative guidance for a topic: frontendchecklist search <topic>, then frontendchecklist rule <slug>.
For a structured pass (launch, accessibility, SEO, performance): frontendchecklist checklists, then frontendchecklist checklist <slug>.

Commands

Command	Purpose
`review <paths...\|->`	Static review of files, directories (walked; vendor dirs skipped), or stdin
`audit <https-url>`	Fetch a public page and review its HTML
`search [query] [--focus a,b] [-n 10]`	Find rules by keyword, technology, or category
`rule <slug>`	Why a rule matters, how to check it, how to fix it
`checklists` / `checklist <slug>`	Curated checklists and their rules
`categories`	Categories with rule counts
`schema`	Full command reference as JSON

Useful flags: --focus accessibility,seo, --min-priority high, --fail-on high.

Reading results

review and audit return { findings: [{ target, rule, title, priority, issue, fix? }], failing }.
Exit code 0: fine. 1: findings at or above --fail-on. 2: bad input or runtime error, with { "error": "..." } on stdout.
Findings are conservative static heuristics. "No findings" means nothing provable was found, not that the code is clean: follow up with search/rule for areas the heuristics cannot see (rendered contrast, focus order, real performance).

Workflow

frontendchecklist review <changed files> --min-priority medium
For each finding, run frontendchecklist rule <rule> and apply its fix guidance.
Re-run the review until no critical/high findings remain (--fail-on high exits 0).
Mention any remaining medium/low findings to the user instead of silently ignoring them.