
Content Without CSS Check
Reviews pages to confirm content still makes sense with CSS disabled or replaced.
- Repository
- thedaviddias/Front-End-Checklist
- Stars
- 74,632
- Licence
- MIT
- Files
- 2 files
What it does
When this skill is installed, the agent reviews web page markup, layout components and design-system patterns to check whether meaning depends on styling. It looks at reading order in the HTML, semantic structure such as headings and lists, whether form labels and error messages are tied to their fields, and whether important text is hidden in CSS generated content. It then suggests semantic HTML fixes and ways to test key pages with styles turned off.
Great for
- Front-end developers reviewing templates or components for accessibility
- Designers and QA testers checking that key user journeys still work without styling
- Teams auditing a design system for layout that depends on visual cues
Skip it if
- Pages whose only purpose is visual, such as decorative graphics, where removing CSS is not meaningful
- Full accessibility audits, since this covers one checklist rule and does not test with assistive technology
Try asking
- “Review this login form template and tell me whether labels and error messages still make sense with CSS disabled.”
- “Check our product card component for content that depends on CSS ordering or pseudo-element text.”
- “Audit this checkout page's DOM order against its visual reading order and list problems.”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 2 original files, the MIT licence and an attribution note.
content-without-css.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip content-without-css.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip content-without-css.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Paste the rendered HTML or the component source along with the CSS so the agent can spot where meaning comes from styling.
- Ask the agent to list the steps to test the page with author styles disabled in your browser, then run them yourself.
- Pair the review with a screen reader or keyboard test, since this skill only reasons about markup.
What's inside
- references/rule.md
- SKILL.md
Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.