Frontendchecklist

CommunityPopular

thedaviddias

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.

Overview

Publisher	thedaviddias
Repository	`Front-End-Checklist`
Skill name	`frontendchecklist`
Stars	74.4K
Forks	6.8K
Bundled files	12
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
12 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by thedaviddias on GitHub. Read the source before you install it.

Installation

Install the Frontendchecklist AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git /tmp/Front-End-Checklist
mkdir -p .claude/skills
cp -r /tmp/Front-End-Checklist/packages/cli .claude/skills/frontendchecklist

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Frontendchecklist in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Frontendchecklist on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Frontendchecklist is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Frontendchecklist AI skill do?

Why use Frontendchecklist on TypingMind?

Because you install it once and use it with any model. Frontendchecklist is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Frontendchecklist in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thedaviddias/Front-End-Checklist/tree/main/packages/cli. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Frontendchecklist?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Frontendchecklist?

As many as you like. As long as a model supports skills, you can use Frontendchecklist with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Frontendchecklist AI skill free?

Yes. It is published on GitHub by thedaviddias under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Openclaw Repair Sweep

openclaw

OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Front-End Checklist CLI

When to use it

Commands

Reading results

Workflow

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now