CSS Component Testing
SkillDev toolsGuides CSS and layout tests for FigUI3 components. Use when validating component CSS, nested selectors, tokens, interaction states, computed styles, layout boxes, or visual regressions.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the CSS Component Testing skill
What this skill tells your AI
The instructions your AI receives, as published by rogie/figui3 in .cursor/skills/css-component-testing/SKILL.md and read by ahel’s review.
Test public CSS behavior in a browser. Prefer computed styles and bounding boxes for stable assertions; use screenshots only for targeted visual regressions.
What To Test
- Token-driven styles resolve through CSS custom properties.
- Public states work: hover, focus, selected, disabled, open, dragging.
- Layout dimensions and positioning stay within expected bounds.
- Light and dark
color-schemepaths do not throw or hide content. - Nested selectors compile through the existing build pipeline.
Test Pattern
- Mount the smallest fixture that exposes the CSS behavior.
- Wait for custom elements and fonts/layout to settle.
- Read
getComputedStyle,getBoundingClientRect, or public attributes/classes. - Assert behavior, not implementation details, unless debugging a specific regression.
Avoid
- Broad screenshot snapshots for every component.
- Assertions tied to browser antialiasing or exact subpixel layout unless necessary.
- Testing private class names when a public attribute/state can be asserted instead.
Signals
- GitHub stars
- 66
- Forks
- 1
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
css-component-testing- Source
- github.com/rogie/figui3