thedaviddias/Front-End-Checklist / plugins/front-end-checklist/skills/frontend-checklist-global
frontend-checklist-global
VerifiedUse when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.4 KB |
| references/categories.md | markdown | 8.4 KB |
references/categories.md
View on GitHub# Front-End Checklist Global Skill Reference
This aggregate skill routes to the Front-End Checklist MCP tools across 386 rules.
## Tool Routing
| Goal | Preferred tool |
| --- | --- |
| Review pasted code or a single file | `review_code` |
| Audit a public page | `audit_url` |
| Find relevant rules by topic | `search_rules` |
| Browse available categories | `list_categories` |
| Get the full content for one rule | `get_rule` |
| Get remediation guidance | `fix_rule` |
| Explain impact to the user | `explain_rule` |
| Pull a curated checklist at once | `get_checklist_rules` |
| Start from a workflow or quick checklist | `get_workflow`, `get_quick_reference` |
## Frontend Review Guardrails
- Do not infer missing metadata from a component fragment that is not responsible for document head output.
- Do not infer required fields, password policies, or decorative-image intent unless the code makes the intent explicit.
- Favor exact evidence from the snippet over broad style advice.
- When the snippet is a partial component, focus on what the component itself controls.
## Rule-Derived Highlights
- **Set explicit width and height on images**
Reserve findings for meaningful content images; decorative micro-SVGs or ornament-only assets are low-priority exceptions when CSS already reserves stable space
Example low-risk exception: `<img src="/divider.svg" alt="" aria-hidden="true">` should not be flagged on its own without evidence of visible layout shift
Always set `width` and `height` attributes on `<img>` matching the image's intrinsic dimensions
Pair with `height: auto` in CSS to keep the image fluid while preserving the aspect ratio
Missing dimensions are the leading cause of Cumulative Layout Shift (CLS) from images
- **Hide decorative elements from assistive technology**
Use alt='' (empty) for decorative images—not alt='image' or missing alt
Add aria-hidden='true' to decorative SVGs and icons
Use CSS background-image for purely decorative visuals
Role='presentation' removes semantic meaning from elements
Do not automatically raise performance findings on decorative micro-assets unless the snippet shows real layout instability
- **Use transform and opacity for animations**
Only transform and opacity can be composited on the GPU without triggering layout
Use will-change: transform sparingly to promote an element to its own compositor layer
Prefer CSS transitions and animations over JavaScript animation libraries for simple effects
Respect prefers-reduced-motion to disable animations for users who need it
- **Respect reduced motion preferences**
Use prefers-reduced-motion media query to disable non-essential animations
Never flash content more than 3 times per second (seizure risk)
Replace motion with opacity/color transitions when reduced motion is enabled
Provide user controls to pause or disable animations
- **Use semantic table markup for screen readers**
Use <th> elements for headers with scope='col' or scope='row'
Add <caption> to describe the table's purpose
Never use tables for layout—use CSS Grid or Flexbox instead
Use id/headers for complex tables with merged cells
For simple tables with a clear adjacent section heading, missing `scope` is often a stronger finding than missing `<caption>`
- **Define proper table headers**
Use `<th>` for all table headers, not `<td>`
Apply `scope="col"` or `scope="row"` to clarify header relationship
Ensure every data cell is associated with at least one header
In simple tables, prefer fixing header associations before escalating to caption-level recommendations
Missing `scope="col"` on a straightforward header row is often the clearest first fix
- **Minimize costly DOM read/write operations**
Never interleave DOM reads (offsetHeight, getBoundingClientRect) with DOM writes (style changes)
Batch all reads first, then all writes
Use requestAnimationFrame for visual updates
Use DocumentFragment or innerHTML for bulk DOM insertion
Avoid per-frame React state updates across many visible components when a simpler CSS or reduced-frequency approach would work
- **Validate forms accessibly**
Associate error messages with fields using aria-describedby
Use aria-invalid to indicate validation state
Mark required fields programmatically with `required` or `aria-required`
Provide inline error messages near the field
Don't rely solely on color to indicate errors
- **Secure password input fields**
Use type='password' with correct autocomplete attribute
Provide accessible show/hide toggle for password visibility
Show password strength indicator with requirements
Never store or transmit passwords in plain text
Support password managers with proper input names
- **Provide visible custom focus indicators**
Never use outline: none or outline: 0 without a visible :focus-visible replacement
Use :focus-visible instead of :focus to show indicators only during keyboard navigation
Focus indicators must have 3:1 contrast ratio against adjacent colors (WCAG 2.2)
Provide at least 2px solid outline with an offset for a high-quality focus ring
If a focus ring is drawn with pseudo-elements, verify it is anchored to the correct positioned element and not clipped by `overflow: hidden`
## Known Safe Patterns
- **Decorative Divider**
Safe example: `<img src="/divider.svg" alt="" aria-hidden="true">`
Treat this as a safe decorative pattern by default. Do not flag alt text or missing dimensions unless the snippet also shows a real layout-shift risk.
- **Client-Handled React Form**
Safe example: `<form onSubmit={event => event.preventDefault()}><label htmlFor="q">Search</label><input id="q" type="search" /></form>`
Do not require `method` or `action` when client-side submit handling is explicit and the form controls are otherwise accessible.
- **Next Metadata API**
Safe example: `export async function generateMetadata() { return { title: 'Docs', description: 'Reference' } }`
Do not infer missing canonical-url, meta description, or Open Graph tags just because literal `<head>` markup is absent from the component file.
- **Preview Card Images**
Safe example: `<img src={resource.image} alt="" className="object-cover" /><img src={favicon} alt="" width={20} height={20} />`
In link-preview or resource-card UIs, decorative preview/favicons can legitimately use empty alt when adjacent text already provides the destination name. Do not invent responsive-image or layout-shift defects for tiny favicon assets without stronger evidence.
- **Aspect-Ratio Media Wrapper**
Safe example: `<div className="aspect-2/1 overflow-hidden"><img className="object-cover w-full h-full" ... /></div>`
When a wrapper already reserves media space with a stable aspect ratio, do not automatically raise a missing dimensions finding for the child preview image.
- **Pseudo-Element Focus Ring**
Safe example: `focus-visible:outline-none focus-visible:after:ring-2 after:absolute after:inset-0`
If focus styling depends on a pseudo-element, verify the ring is anchored to the correct positioned element. A removed native outline is only safe when the replacement ring is clearly reliable.
- **Per-Frame React Counter Animation**
Safe example: `requestAnimationFrame(animate); setCount(Math.floor(eased * target))`
Repeated requestAnimationFrame state updates across multiple components are a concrete performance concern when shown directly in the code.
- **Simple Data Table Headers**
Safe example: `<thead><tr><th>Priority</th><th>Rule</th><th>Title</th></tr></thead>`
For simple data tables, prefer conservative column-header findings before speculating about row headers or outer-layout landmarks.
- **Adjacent Heading + Table**
Safe example: `<h2>Issues</h2><table><thead>...</thead><tbody>...</tbody></table>`
A nearby visible section heading may already provide table context. Prefer scope/header association findings before requiring a caption unless the table purpose is ambiguous.
## Category Coverage
- **accessibility**: 89 rules · 9 critical · 25 high
- **css**: 31 rules · 10 high
- **html**: 34 rules · 3 critical · 12 high
- **i18n**: 5 rules
- **images**: 25 rules · 1 critical · 15 high
- **javascript**: 26 rules · 1 critical · 12 high
- **performance**: 43 rules · 1 critical · 22 high
- **privacy**: 5 rules · 2 high
- **security**: 22 rules · 4 critical · 10 high
- **seo**: 93 rules · 19 high
- **testing**: 13 rules · 7 high
Rules browser: https://frontendchecklist.io/rules
Full reference: https://frontendchecklist.io/llms-full.txt
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |