Kb Path Instructions
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Runs the frontendchecklist CLI against local files or a deployed URL to check code against 380+ accessibility, performance, SEO and security rules, with fixable, cited findings.
Install Front-End Checklist CLI Review
$ npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist frontendchecklist --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/cli .claude/skills/frontendchecklist && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontendchecklist" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli into .claude/skills/frontendchecklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontendchecklist", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cliType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist frontendchecklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/cli .agents/skills/frontendchecklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontendchecklist" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli into .agents/skills/frontendchecklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontendchecklist", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist frontendchecklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/cli .cursor/skills/frontendchecklist && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontendchecklist" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli into .cursor/skills/frontendchecklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontendchecklist", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path packages/cli--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist frontendchecklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/cli .gemini/skills/frontendchecklist && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontendchecklist" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli into .gemini/skills/frontendchecklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontendchecklist", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist frontendchecklistInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/cli .github/skills/frontendchecklist && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontendchecklist" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli into .github/skills/frontendchecklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontendchecklist", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist frontendchecklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/cli .opencode/skills/frontendchecklist && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontendchecklist" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli into .opencode/skills/frontendchecklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontendchecklist", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontendchecklist- GitHub stars
- 74k
- Token cost
- ~692 tokens
- SKILL.md length
- 308 words
- Files
- 15 (incl. scripts)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
Runs the frontendchecklist CLI against local files or a deployed URL to check code against 380+ accessibility, performance, SEO and security rules, with fixable, cited findings.
- Works in 4 steps: frontendchecklist review --min-priority… → For each finding, run frontendchecklist… → Re-run the review until no critical/high… → …
- Reviewing frontend code against accessibility, performance and SEO rules before a commit
- SKILL.md covers When to use it, Commands, Reading results and Workflow
- Runs TypeScript and JavaScript scripts from its folder; calls npx and git
What it does
This skill wraps the frontendchecklist CLI, which works offline, prints JSON when piped and uses exit codes a workflow can branch on: 0 for fine, 1 for findings at or above a chosen priority, and 2 for bad input with an error on stdout. The review command statically checks files, directories or stdin, walking directories while skipping vendor folders, while the audit command fetches a public URL and reviews its live HTML; a search command finds rules by keyword, technology or category, and a rule command explains why a specific rule matters, how to check it and how to fix it.
Findings come back as a structured list of target, rule, title, priority, issue and an optional fix, and the skill is explicit that a clean result means nothing provable was found, not that the code is clean, since the checks are conservative static heuristics that cannot see things like rendered contrast or real focus order. A curated checklists command groups rules into passes such as launch, accessibility, SEO or performance for a structured review instead of running every rule at once.
The recommended workflow runs the review at a medium priority floor on the changed files, applies each finding's fix guidance by looking up its rule, re-runs the review until no critical or high findings remain, and surfaces any leftover medium or low findings to the user rather than silently dropping them.
When your agent uses it
- Reviewing frontend code against accessibility, performance and SEO rules before a commit
- Auditing a deployed page's live HTML against the Front-End Checklist
- Looking up why a specific front-end rule matters and how to fix it
- Running a structured pre-launch pass covering accessibility, SEO and performance together
Example prompts
- “Review my changed files against the checklist at medium priority and fix the high findings.”
- “Audit https://example.com against the Front-End Checklist and summarize the critical issues.”
- “Look up the rule about image alt text and show me how to fix it here.”
- “Run the pre-launch checklist pass on this page before we ship.”
Requirements
- Node.js to run the frontendchecklist CLI via npx
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- frontendchecklist review --min-priority medium
- For each finding, run frontendchecklist 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.
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (TypeScript and JavaScript), which the agent can run.
Shell commands in SKILL.md call:
npxgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Front-End Checklist CLI Review loads about 692 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 308 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 308 words, ~692 tokens.
Download SKILL.mdSave it as
.claude/skills/frontendchecklist/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.- name
- frontendchecklist
- description
- 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.
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>, thenfrontendchecklist rule <slug>. - For a structured pass (launch, accessibility, SEO, performance):
frontendchecklist checklists, thenfrontendchecklist 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
reviewandauditreturn{ 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/rulefor 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 highexits 0). - Mention any remaining medium/low findings to the user instead of silently ignoring them.
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 14 other files (scripts) in packages/cli of thedaviddias/Front-End-Checklist.
- SKILL.md
- .gitignore
- README.md
- package.json
- scripts/build.ts
- src/args.ts
- src/commands/audit.ts
- src/commands/lookup.ts
- src/commands/review.ts
- src/content.ts
- src/index.ts
- src/output.ts
- src/spec.ts
- tests/cli.test.mjs
- tsconfig.json
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Front-End Checklist CLI Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Front-End Checklist CLI Review this skillthedaviddias/Front-End-Checklist | 74k | — | ~692 | Automated safety check: Pass | MIT | |
| Kb Path InstructionsCommunity-Access/accessibility-agents | 423 | — | ~385 | Automated safety check: Pass | MIT | |
| Kill AI Slopyetone/kill-ai-slop | 1.3k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| UI/UX Design System AdvisorGalaxy-Dawn/claude-scholar | 5.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| GlideSrivarsanK/Glide | 120 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| UI UX Pro MaxOhh-889/skyroc | 795 | 26 repos | ~3.6k | Automated safety check: Notes | MIT |
Similar skills
Kill AI Slop
yetone/kill-ai-slop
Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.
UI/UX Design System Advisor
Galaxy-Dawn/claude-scholar
Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.
Glide
SrivarsanK/Glide
Authoritative guide and toolset for AI agents to operate, configure, and visually design applications using Glide (@srivarsank/glide).
UI UX Pro Max
Ohh-889/skyroc
UI/UX design intelligence. An agent skill from Ohh-889/skyroc.
- Official
Playwright Best Practices
sanity-io/sanity
A skill your agent uses when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling…
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Front-End Checklist CLI Review
What does Front-End Checklist CLI Review do?
Runs the frontendchecklist CLI against local files or a deployed URL to check code against 380+ accessibility, performance, SEO and security rules, with fixable, cited findings. This skill wraps the frontendchecklist CLI, which works offline, prints JSON when piped and uses exit codes a workflow can branch on: 0 for fine, 1 for findings at or above a chosen priority, and 2 for bad input with an error on stdout. The review command statically checks files, directories or stdin, walking directories while skipping vendor folders, while the audit command fetches a public URL and reviews its live HTML; a search command finds rules by keyword, technology or category, and a rule command explains why a specific rule matters, how to check it and how to fix it.
When should I use Front-End Checklist CLI Review?
Front-End Checklist CLI Review fits situations like: reviewing frontend code against accessibility, performance and SEO rules before a commit; auditing a deployed page's live HTML against the Front-End Checklist; looking up why a specific front-end rule matters and how to fix it; running a structured pre-launch pass covering accessibility, SEO and performance together.
How do I install Front-End Checklist CLI Review in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a claude-code`. Or copy the skill folder (packages/cli in thedaviddias/Front-End-Checklist) into .claude/skills/frontendchecklist in your project. Claude Code loads it when a task matches its description.
How do I install Front-End Checklist CLI Review in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a codex`. Or copy the skill folder (packages/cli in thedaviddias/Front-End-Checklist) into .agents/skills/frontendchecklist in your project. Codex loads it when a task matches its description.
Can I use Front-End Checklist CLI Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill frontendchecklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontendchecklist, .gemini/skills/frontendchecklist, .github/skills/frontendchecklist and .opencode/skills/frontendchecklist in your project.
What does Front-End Checklist CLI Review need to run?
Going by SKILL.md and its folder, Front-End Checklist CLI Review needs TypeScript and JavaScript for the scripts in its folder and the command-line tools its instructions call (npx and git). Our summary lists: Node.js to run the frontendchecklist CLI via npx.
Does Front-End Checklist CLI Review access the network?
SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Front-End Checklist CLI Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Front-End Checklist CLI Review use?
Front-End Checklist CLI Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Front-End Checklist CLI Review use?
About 692 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Front-End Checklist CLI Review?
Skills that share tags, products or a category with Front-End Checklist CLI Review: Kb Path Instructions (Community-Access/accessibility-agents, 423 stars), Kill AI Slop (yetone/kill-ai-slop, 1.3k stars), UI/UX Design System Advisor (Galaxy-Dawn/claude-scholar, 5.7k stars) and Glide (SrivarsanK/Glide, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Front-End Checklist CLI Review?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.