Skip to content
Back to skills

Frontend Design Design Quality Orchestrator

ASecurity

Route broad frontend design work through product, visual, usability, accessibility, responsive, state, and release gates.

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

Security analysis

A100/100

Scanned October 2, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Frontend Design Design Quality Orchestrator?

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

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

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-orchestrator
name: Frontend Design Quality Orchestrator
description: Route broad frontend design work through product, visual, usability, accessibility, responsive, state, and release gates.
stack:
  - Frontend
  - HTML
  - CSS
  - Design Systems
category: design
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - improve frontend design
  - design quality review
  - make UI better
  - frontend UX audit
---

# Frontend Design Quality Orchestrator

## Purpose

Turn broad interface requests into one bounded design pass with measurable closure.

## When to Use

- A page, feature, component family, or design system needs coordinated review.
- The dominant design risk is unclear or multiple specialist skills could apply.

## Do

- Run product intake, classify the dominant risk, and choose one primary plus at most three secondary skills.
- Record intent, constraints, rejected alternatives, evidence, acceptance criteria, and owner.
- Validate accessibility, responsive behavior, component states, and release evidence before closure.

## Do Not

- Do not load every design skill for one task or substitute decoration for task success.
- Do not approve attractive work with undefined loading, error, empty, keyboard, or responsive behavior.

## Review Checklist

- [ ] Primary user task, constraints, and dominant risk are explicit.
- [ ] Selected skills have bounded scope and evidence.
- [ ] Release blockers have an owner or are resolved.

## Expected Output

1. Diagnosis and selected skills.
2. Design decision record and smallest safe implementation plan.
3. Final scorecard, blockers, and release decision.

## 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…