Skip to content
Back to skills

Frontend Design Design Quality Release Gate

ASecurity

Score product intent, visual identity, usability, components, accessibility, responsiveness, states, motion, and validation with blocker overrides.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
designgotestingapifrontendperformance

Works with

  • api

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill frontend--design--design-quality-release-gate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Frontend Design Design Quality Release Gate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Frontend  Design  Design Quality Release Gate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-frontend-design-design-quality-release-gate/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-frontend-design-design-quality-release-gate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: frontend.design.design-quality-release-gate
name: Design Quality Release Gate
description: Score product intent, visual identity, usability, components, accessibility, responsiveness, states, motion, and validation with blocker overrides.
stack:
  - Frontend
  - UX
  - Design Systems
  - Testing
category: quality
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - design release gate
  - frontend quality score
  - design QA
  - approve UI release
---

# Design Quality Release Gate

## Purpose

Provide measurable closure for design work: blockers override score, while evidence prevents subjective iteration from continuing indefinitely.

## When to Use

- A feature, page, component family, or multi-agent design pass is ready for release decision.
- Teams need shared design definition of done.

## Do

- Score product intent and task success (20), visual identity (15), hierarchy (10), component API/reuse (15), accessibility (15), responsiveness (10), states/feedback (10), and motion/performance/regression validation (5).
- Attach implementation, task, screenshot, and test evidence; classify remaining work by severity, owner, and date.
- Pass at 85 or above with no blocker; conditionally approve at 70-84 only with owned remediation; fail below 70 or on any blocker.

## Do Not

- Do not average away critical blockers, inflate score through low-value polish, or use a rubric instead of product judgment.

## Review Checklist

- [ ] Score has evidence for every category.
- [ ] User-task and accessibility blockers are resolved or decision is fail.
- [ ] Accepted debt has owner and date.

## Expected Output

1. 100-point scorecard and evidence.
2. Blocker list and approval status.
3. Owned remediation and accepted-debt record.

## References

- [Design Excellence Guide](../../../../docs/design-excellence-guide.md)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…