Enforce frontend code review and implementation quality using a frontend checklist
Use a structured frontend checklist and MCP tools to help AI agents and human developers conduct accessibility, performance, SEO, security, and code quality audits when writing React, Next.js, HTML, and CSS frontend code.
GitHubthedaviddias74.6kGitHub stars
CursorClaude Codev0BoltFront-End Checklist MCP
Added 2026-11-01 · originally published 2026-10-31
Key points
- Choose the correct UI pattern using UX Patterns and compare trade-offs among common UI patterns before deciding how to implement an interface.
- Connect MCP-compatible AI agents to Front-End Checklist for frontend code reviews, structured rule lookups, and audits.
- Prioritize using review_code to review pasted code, components, or files and report the highest-confidence issues.
- Search for rules using search_rules before providing suggestions on accessibility, performance, SEO, security, or images.
- Audit public https:// pages directly using audit_url.
Pitfalls
- Writing frontend code blindly without verification, leading to issues that impact user experience, accessibility, performance, SEO, or security.
.cursorrules
- Always consult the Front-End Checklist rules when making recommendations for HTML, CSS, JavaScript, accessibility, performance, SEO, security, images, privacy, i18n, and testing. - Use MCP-compatible tools or `review_code` to audit components and code before finalizing implementations.
Copy-ready prompt
Use the Front-End Checklist MCP to review this [React component / page / code] and report the highest-confidence findings first based on rules for HTML, CSS, JavaScript, accessibility, performance, SEO, security, images, privacy, i18n, and testing.
#AI Frontend Development#Code Review#Frontend Standards#MCP
Related techniques
Summarized by AI from the original source - refer to the original post for details. Copyright belongs to the original author.