agentsclimarketplace
Sign in

Design qa

Skill newmindsgroup/ai-agent-skills-library/dist/skills/design-qa

Use when the user wants visual QA, screen QA, responsive QA, polish review, pre-launch design review, or a structured check of an implemented UI or design artifact. Also use when the user says review this UI, check mobile polish, verify the screen, or make sure the design feels consistent and complete.From its SKILL.md

Install
npx -y skills add newmindsgroup/ai-agent-skills-library --skill design-qa

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 262 tokens by cl100k_base, as published. Nobody here has run it

Design QA

Use this skill to standardize visual and UX quality checks after a design or implementation exists.

Read First

  • /Users/newmindsgroup/.codex/knowledge/design-reviews/design-qa-checklist.md
  • /Users/newmindsgroup/.codex/knowledge/design-reviews/visual-anti-pattern-checklist.md
  • /Users/newmindsgroup/.codex/knowledge/ux-patterns/states-heuristics.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/typography-rules.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/spacing-radius-elevation.md

Use screenshots, browser captures, or Figma screenshots when available. Prefer screenshot-driven review over abstract judgment.

Scope

  • visual hierarchy
  • CTA prominence
  • spacing consistency
  • mobile and desktop behavior
  • state coverage
  • accessibility basics
  • overall polish

Workflow

  1. Identify the surface and artifact type.
  2. Review the UI against the checklist and style defaults.
  3. Prioritize launch blockers before polish notes.
  4. Separate visual, UX, and responsive findings only when it improves clarity.

Outputs

  • prioritized QA findings
  • launch blockers
  • polish recommendations

What ships with it: 1 file

208 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.