Best frontend CLAUDE.md rules
CLAUDE.md rule sets for frontend development — React, TypeScript, and modern UI frameworks.
CLAUDE.md rule sets for frontend development — React, TypeScript, and modern UI frameworks.
Compared at a glance
The top 5 picks side by side on trust, install, platform support, and disclosed notes — full rationale for each below.
| Field | React Expert - CLAUDE.md Rules for Claude Code Transform Claude into a framework-agnostic React core specialist focused on the built-in Hooks, the Rules of Hooks, and component fundamentals from the official React docs Open dossier | Angular Expert - CLAUDE.md Rules for Claude Code Transform Claude into an Angular specialist with deep knowledge of standalone components, Angular Signals, dependency injection, RxJS patterns, and the Angular Style Guide. Open dossier | Vue 3 Composition API Expert - CLAUDE.md Rules for Claude Code Transform Claude into a Vue 3 specialist with deep knowledge of the Composition API, script setup syntax, Pinia state management, and Vue Router best practices. Open dossier | AI-Generated Frontend Accessibility Review Rules Source-backed rules for reviewing AI-generated frontend UI changes for accessibility before merge, with semantic HTML, keyboard paths, focus management, labels, automated scan limits, manual checks, and privacy-safe evidence. Open dossier | Production Codebase Auditor - CLAUDE.md Rules for Claude Code Expert in comprehensive production codebase analysis with Zod validation enforcement, security vulnerability detection, and code consolidation strategies Open dossier |
|---|---|---|---|---|---|
| Trust | |||||
| Install risk | Review first | Review first | Review first | Review first | Review first |
| Notes | Safety · Privacy ✓ | Safety · Privacy · | Safety · Privacy · | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | rules | rules | rules | rules | rules |
| Source | source-backed | source-backed | source-backed | source-backed | source-backed |
| Author | JSONbored | jaso0n0818 | jaso0n0818 | MkDev11 | JSONbored |
| Added | 2025-09-15 | 2026-06-13 | 2026-06-13 | 2026-06-04 | 2025-09-26 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — | — |
| Safety notes | — missing | — missing | — missing | ✓AI-generated UI can silently replace semantic controls with divs, remove labels, hide focus indicators, break keyboard order, change error messaging, or add motion that affects users. Automated scans catch important classes of issues but do not prove that custom widgets, focus restoration, reading order, copy meaning, or assistive-technology behavior are correct. Browser automation and accessibility checks should run against local, preview, or staging environments with test accounts so forms, payments, messages, and destructive actions are not triggered in production. | ✓Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified. |
| Privacy notes | ✓Guidance covers React state and effects; keep API keys, tokens, and secrets out of client-side React code and bundles, since anything in the client is exposed to users. | — missing | — missing | ✓Accessibility evidence can include screenshots, DOM text, accessible names, form values, labels, user content, network traces, browser storage, cookies, and test account data. Do not paste raw screenshots, traces, accessibility trees, DOM snapshots, customer names, private routes, or production form data into public PR comments without redaction. Use synthetic content and test accounts for accessibility examples, especially when reviewing auth, billing, dashboards, healthcare, education, or support flows. | ✓Auditing reads source, configuration, and logs that may contain secrets or personal data; keep any captured sensitive values out of shared audit reports. |
| Prerequisites | — none listed | — none listed | — none listed |
| — none listed |
| Install | — | — | — | — | — |
| Config | — | — | — | — | — |
| Citations | |||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
- 01Why it made the cut
React Expert - CLAUDE.md Rules for Claude Code is included because it has privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 02Why it made the cut
Angular Expert - CLAUDE.md Rules for Claude Code is included because it has source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 03Why it made the cut
Vue 3 Composition API Expert - CLAUDE.md Rules for Claude Code is included because it has source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 04Why it made the cut
AI-Generated Frontend Accessibility Review Rules is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 05Why it made the cut
Production Codebase Auditor - CLAUDE.md Rules for Claude Code is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 06Why it made the cut
React Server Components Expert for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 07Why it made the cut
Security-First React Components for Claude is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 08Why it made the cut
TypeScript API Client Compatibility Review Rules is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 09Why it made the cut
Svelte Expert - CLAUDE.md Rules for Claude Code is included because it has privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 10Why it made the cut
tRPC Expert - CLAUDE.md Rules for Claude Code is included because it has privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 11Why it made the cut
NestJS Expert - CLAUDE.md Rules for Claude Code is included because it has privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 12Why it made the cut
Prisma Expert - CLAUDE.md Rules for Claude Code is included because it has privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
Missing a pick? Propose an edit to this list — every change goes through the same review queue as new entries.
Suggest a pickGet the weekly brief
One calm read on Claude workflows. Sundays. No tracking pixels.
Unsubscribe any time. No tracking pixels. No partner blasts.