Senior Frontend SKILL makes Claude Code open your page in a real browser before it says done
// Detect dark theme var iframe = document.getElementById('tweet-2120513853725294751-511'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2120513853725294751&theme=dark" } A passing typecheck tells you nothing about whether the button can be reached with Tab, or whether a long name breaks the layout on a phone. That gap is the…
Senior Frontend Skill, a component of Claude Code Templates, ensures that Claude reads and writes code in a structured manner before declaring a UI task complete. This skill, with 31,000 downloads and version 2.0.0, prevents Claude from marking a UI task as finished too quickly based on a clean build. The skill emphasizes the importance of order, adding various UI states like loading, empty, error, success, pending action, and partial failure, each with required outcomes rather than suggestions.
The build rules prioritize platform-specific considerations, enforcing best practices such as using button elements for actions, href elements for navigation, and ensuring inputs have visible labels and appropriate types. Accessibility is a key focus, requiring accessible names for icon-only buttons and proper labeling for all inputs.
The skill also mandates that async results be placed in an aria-live region for proper screen reader handling. To install and use the skill, one can run npx claude-code-templates@latest --skill development/senior-frontend, which generates several files including the SKILL.md, reference documents, a NOTICE file, and two scripts. The skill is activated when invoked and loads additional reference documents only when needed.
The most time-consuming part of the skill is opening the page in a browser for verification, which involves running a script that checks various elements for accessibility and usability issues. While the skill adds time, it is particularly beneficial for projects involving keyboard navigation, mobile devices, or error handling scenarios, potentially reducing review time by catching common UI bugs before they become issues.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
