Front-End-Checklist
thedaviddias/Front-End-Checklist
The essential checklist for modern web development
Overview
A repository containing a comprehensive front-end quality system designed for both human developers and AI agents, including rules, guidelines, and interactive tools.
Categories
Tags
Similar tools
ECC
affaan-m/ECC
affaan-m/ECC
ollama
ollama/ollama
Local inference runtime and CLI for open-weight large language models
prompts.chat
f/prompts.chat
f/prompts.chat
langflow
langflow-ai/langflow
Metadata derived from provided repository information.
dify
langgenius/dify
Production-ready platform for agentic workflow development.
browser-use
browser-use/browser-use
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
Install
git clone https://github.com/thedaviddias/Front-End-ChecklistREADME
Front-End Checklist
Front-End Checklist is the open-source front-end quality system for humans and AI agents. It turns front-end best practices into a practical review workflow you can browse on the web, run through with MCP-compatible tools, or work through directly in this README.
- Website: frontendchecklist.io
- Rules: frontendchecklist.io/rules
- MCP server: mcp.frontendchecklist.io
Companion project: UX Patterns for Devs helps developers choose the right UI pattern before using Front-End Checklist to verify implementation quality.
[!IMPORTANT] Use the website for browsing and filtering, the MCP server for agent workflows, and this README when you want the checklist in one place.
What you get
385English rules across11active categories11MCP tools exposed by the hosted server- Rule pages with explanations, remediation guidance, and verification steps
How to use this checklist
- Start with the category navigator below and jump straight to the part of the checklist you need.
- Work through the checkbox items that apply to your project, audit, or pull request.
- Open the linked rule pages when you need the full guidance, examples, verification steps, and AI prompts.
- Use frontendchecklist.io for interactive browsing, and mcp.frontendchecklist.io when you want agents to use the same rule corpus directly.
Priority legend
- ![Critical][critical_img] means site-breaking, compliance-sensitive, or security-sensitive issues that should be fixed first.
- ![High][high_img] means issues with major impact on user experience, accessibility, performance, or discoverability.
- ![Medium][medium_img] means strong best practices that should be part of normal frontend quality review.
- ![Low][low_img] means useful improvements that are situational or lower urgency.
Choose your workflow
Browse online
- Explore all rules at frontendchecklist.io/rules
- Use curated checklists at frontendchecklist.io/checklists
- Open a category page for focused audits and implementation guidance
Choose the right pattern first
Front-End Checklist helps you review implementation quality. If you are still deciding what interface to build, use UX Patterns for Devs to compare common UI patterns, understand tradeoffs, and find practical guidance for forms, navigation, data display, feedback states, authentication, and AI interfaces.
Contribute to the checklist
- Install dependencies:
pnpm install - Run local development:
pnpm dev - Validate structure:
pnpm validate:rule-structure - Score the corpus:
pnpm score:rules - Regenerate derived artifacts:
pnpm generate:skillsandpnpm generate:readme
Use with MCP
Connect an MCP-capable agent to Front-End Checklist for frontend code review, structured rule lookup, audits, and remediation workflows across React, Next.js, HTML, CSS, JavaScript, accessibility, performance, SEO, security, images, privacy, i18n, and testing.
[!TIP] Best first use: point an MCP-capable agent at a real component, page, or public URL and explicitly ask it to use the Front-End Checklist MCP for the highest-confidence frontend findings first. Some clients discover installed MCP tools lazily, so naming the server in the prompt helps.
- Public endpoint: mcp.frontendchecklist.io
- Public docs: frontendchecklist.io/mcp
- Local/editor integration: stdio server at
packages/mcp/src/cli.ts
What you can do:
- Review pasted code or file contents against the checklist
- Audit a live public URL
- Fetch a specific rule with remediation guidance
- Search rules by keyword,