FEA Checklist

Reference

The list I actually work through: markup, SEO, accessibility, RTL and Arabic typography, images, performance, forms, security, and the launch gate. Each item says why it matters, and your progress is kept in this browser.

Runs entirely in your browserFrontEnd-Checklist

The full dataset from the FrontEnd-Checklist repo, unedited — 23 sections, 262 items, severity intact.

Progress

0 of 262 done

Search the checklist

Your ticks are saved in this browser only.

Don't sit blocked, and don't invent things silently. Use this escalation order whenever you hit a question, a missing screen, or undefined content.

Have ANY question? Ask in the team channel before you guess.Required10 minutes of asking saves 2 hours of rework. No question is too small — if you're unsure, ask. The whole team benefits from the answer.
Missing copy / SEO tags / alt text / error messages? Draft with ChatGPT (or any LLM), then refine.RequiredUse AI for first drafts of: <title>, meta description, OG titles & descriptions, image alt text, empty-state copy, error messages, button labels. Always review and tighten before shipping — AI drafts are a starting point, not a final answer.
```
Prompt template:
  "Write a 150–160 char meta description for a page about <X>.
   Tone: <brand voice>. Audience: <who>. Include keywords: <list>."
```
UI screen / state / breakpoint NOT clear in Figma? Ask the UI designer FIRST — never invent.RequiredIf a state (hover, error, empty, loading), a breakpoint, an icon, or a spacing value is missing or ambiguous in Figma, ask the designer before building. Inventing it leads to rework and 'this isn't what I designed' meetings.
Small/isolated UI piece NOT in Figma and designer not blocking? Generate with an AI UI tool, then align to the design system.RecommendedFor small gaps (a 404 illustration, a simple empty-state card, a placeholder skeleton) you can use Google Stitch, v0, Galileo AI, or similar. Generate fast, then re-skin to match your tokens (spacing, color, type) before merging.
Never ship placeholder content (lorem ipsum, 'TBD', random stock photos)RequiredFlag the gap, request real content, ship when ready. Placeholders shipped to production = embarrassment + emergency hotfix.
Match existing codebase conventions before introducing new onesRequiredIf the project already uses BEM, you use BEM. Already on Tailwind, you stay on Tailwind. Introducing new patterns mid-project requires a team discussion first.
Document any assumption, AI-generated content, or open question in the PR descriptionRequiredIf you used ChatGPT for copy, an AI tool for a small component, or made a judgment call — say so in the PR. Reviewers should not have to guess what was hand-built vs generated, or what's still pending.

262 results