// the find
thedaviddias/Front-End-Checklist
🗂 The essential checklist for modern web development, for humans and AI agents
Front-End Checklist is a structured collection of 385 frontend quality rules across HTML, CSS, JavaScript, performance, accessibility, SEO, and more, with a companion website, MCP server, and shareable checklists. It has evolved from a static markdown file into a full Next.js app with user accounts, progress tracking, and an MCP endpoint that lets AI agents query the rule corpus directly. The target audience is frontend developers who want a systematic review workflow rather than ad-hoc gut checks.
The MCP server integration is the genuinely interesting move — exposing the rule corpus as 11 MCP tools means agents can query specific rules, audit a live URL, or search by category without you copy-pasting the whole checklist into a prompt. The priority system (Critical/High/Medium/Low) is consistently applied and gives a triage order that's actually useful during an audit. The rules themselves are specific and actionable: 'Use transform and opacity for animations' is more useful than 'make animations fast'. The repo also ships a real test suite, e2e with Playwright, and CI workflows — it's not just a glorified markdown file.
The rule set is static MDX authored by one person, so accuracy and completeness are a bet on that person keeping up — there's no community review pipeline that would catch a stale or wrong rule before it ships. The MCP server is a hosted endpoint at mcp.frontendchecklist.io, which is fine until it goes down or rate-limits you; local stdio mode is available but the setup path isn't prominent. At 385 rules, the checklist is long enough that working through it linearly on a real project is unrealistic — the filtering and checklist features help, but there's still no way to say 'I'm building a landing page, give me the 30 rules that actually matter'.