design-validate
Skill4 starsChanged 5 days agoMITView on GitHub
Validate visual design changes across screen sizes, themes, content variants, readability, and brand coherence. Use for visual regression and design acceptance checks.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- tstapler/dotfilestheir own version, first seen Oct 10, 2026
- ba0918/claude-skillstheir own version, first seen Jul 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- tstapler/dotfiles★ 8same name
- ba0918/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- design-balance-and-proportionSkill
- design-brand-and-art-directionSkill
- design-buildSkill
- design-color-theorySkill
- design-diagnoseSkill
- design-hierarchy-and-emphasisSkill
- design-imagery-and-textureSkill
- design-layout-and-gridSkill
- design-movement-and-flowSkill
- design-reviewSkill
- design-rhythm-and-patternSkill
- design-typographySkill
- design-unity-and-systemsSkill
- security-api-files-and-realtimeSkill
- security-authentication-and-sessionsSkill
- security-authorizationSkill
- security-browser-and-originSkill
- security-buildSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- security-reviewSkill
- security-threat-model-and-designSkill
- security-validateSkill
- ux-accessibilitySkill
- ux-buildSkill
- ux-controls-and-inputsSkill
- ux-decisions-and-loadSkill
- ux-diagnoseSkill
- ux-feedback-and-performanceSkill
- ux-forms-and-errorsSkill
- ux-journeys-and-motivationSkill
- ux-navigation-and-structureSkill
- ux-onboarding-and-learningSkill
- ux-reviewSkill
- ux-trust-and-ethicsSkill
- ux-validateSkill
- ux-visual-hierarchySkill
- wcag-alternatives-and-mediaSkill
- wcag-assistive-tech-and-statusSkill
- wcag-buildSkill
- wcag-diagnoseSkill
- wcag-forms-and-error-preventionSkill
- wcag-keyboard-and-focusSkill
- wcag-language-and-predictabilitySkill
- wcag-navigation-and-discoverySkill
- wcag-pointer-and-touchSkill
- wcag-reviewSkill
- wcag-semantics-and-reading-orderSkill
- wcag-time-and-motionSkill
- wcag-validateSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Verify rendered visual outcomes and regressions.
- Very specific: line 15
Test relevant variants: mobile/desktop widths, available themes, light/dark, zoom/text-spacing overrides, localization, long/error/empty …
- Very specific: line 17
Check cross-lens issues with wcag-validate (actual WCAG criteria, keyboard and AT) and ux-validate (task outcome and behavior).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate visual design changes and screenshot outcomes
Scope
Verify rendered visual outcomes and regressions; treat aesthetic judgment separately from accessibility and usability evidence.
Procedure
- Translate each design finding to a concrete acceptance condition: intended focal element, consistent semantic role, improved grouping, correct image crop, token reuse, robust text wrapping, or matching brand brief. Record the baseline and the change under test.
- Test relevant variants: mobile/desktop widths, available themes, light/dark, zoom/text-spacing overrides, localization, long/error/empty data, component interaction states and image-load failures. Do not claim coverage for variants not actually rendered.
- Use automated visual diff where available, but inspect important differences manually to separate intentional improvements from regressions. Check layout overflow and token usage via code; use grayscale or a short exposure to test hierarchy. Inspect at least one responsive transition rather than merely checking fixed endpoints.
- Check cross-lens issues with
wcag-validate(actual WCAG criteria, keyboard and AT) andux-validate(task outcome and behavior). Visual checks cannot replace either. - Compare against
references/visual-test-matrix.md, recordpassed,failed, ornot-tested, link evidence, and report remaining brand/product judgment separately. Do not invent numeric aesthetic scores.
Output
A concise per-finding table: hypothesis → variant(s) tested → method/evidence → observed result → regression notes → status/untested gaps. A report with no screenshots or browser rendering must explicitly describe its limitation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.