Skip to content
cccskills
FreePublished on GitHub

ag-avaliar-ux-design-library

Avalia qualidade UX de um projeto comparando screenshots reais contra a Design Library (24 solucoes + design system). Captura telas via Playwright, pontua aderencia a tokens/patterns, identifica desvios. Produz UX Compliance Report.

The English summary is being prepared. Showing the original description.

Works withPlaywright
See how to install

Files included (2)

  • SKILL.md8.1 KB
  • source.json796 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

ag-avaliar-ux-design-library — Avaliacao UX contra Design Library

Papel

Avalia a qualidade visual/UX de um projeto comparando o que foi implementado contra o padrao da empresa (Design Library + Design System). Captura screenshots reais, compara contra as solution specs, e produz um UX Compliance Report com score e acoes.

Diferenca de outros skills:

  • ag-revisar-ux: Review pontual com heuristicas de Nielsen (generico)
  • ag-testar-ux-qualidade: UX-QAT PDCA com design tokens (testes continuos)
  • ag-meridian D4-LOOKS: Score visual generico (4 viewports)
  • Este skill: Compara contra a PROPRIA Design Library da empresa (padrao interno)

Invocacao

/ag-avaliar-ux-design-library http://localhost:3000
/ag-avaliar-ux-design-library http://localhost:3005 --scope "/dashboard,/consultas"
/ag-avaliar-ux-design-library ~/Claude/GitHub/salarios-platform --threshold 80

Pre-requisitos

  1. Playwright MCP disponivel (para screenshots)
  2. App rodando (localhost ou URL deployada)
  3. Design Library acessivel em ~/Claude/assets/design-library/
  4. Design System em ~/Claude/assets/design-library/UI_UX/raiz-educacao-design-system.md

Pipeline (5 fases)

DISCOVER → CAPTURE → MATCH → EVALUATE → REPORT

Fase 1: DISCOVER — Mapear telas do projeto

  1. Navegar para URL da app via Playwright MCP
  2. Capturar snapshot de acessibilidade (browser_snapshot)
  3. Identificar rotas/paginas disponiveis na navegacao
  4. Se --scope especificado, filtrar rotas
  5. Classificar cada tela por tipo: dashboard, form, table, chat, workflow, layout, etc.

Fase 2: CAPTURE — Screenshots de cada tela

Para cada tela identificada:

  1. Navegar via browser_navigate
  2. Aguardar carregamento completo (browser_wait_for)
  3. Capturar screenshot full-page:
    browser_take_screenshot({ type: "png", filename: "ux-compliance/{slug}-desktop.png", fullPage: true })
    
  4. Capturar em mobile (375px):
    browser_resize({ width: 375, height: 812 })
    browser_take_screenshot({ type: "png", filename: "ux-compliance/{slug}-mobile.png" })
    browser_resize({ width: 1440, height: 900 })  # restaurar
    
  5. Capturar snapshot de acessibilidade (para analise estrutural)
  6. Capturar console errors (browser_console_messages)

Fase 3: MATCH — Associar telas a solucoes da Design Library

Para cada tela capturada:

  1. Ler ~/Claude/assets/design-library/catalog.md
  2. Identificar qual(is) solution(s) a tela DEVERIA seguir:
Tipo de tela detectadoSolution esperada
Dashboard com KPIs01-dashboard-kpi
Tabela com dados02-table-filters-export
Formulario multi-step03-forms-multistep
Timeline/historico04-status-workflow-timeline
Layout principal05-app-shell-sidebar
Workflow visual06-workflow-builder
Chat/AI07-chat-ai-streaming
Viewer PDF08-pageflip-3d
Kanban/board11-dragdrop-virtual-scroll
Export/docs12-document-generation
RAG/busca13-rag-knowledge-base
Graficos/BI15-bi-data-explorer
Contratos17-contract-lifecycle
  1. Ler a spec da solution matched: ~/Claude/assets/design-library/solutions/NN-id/spec.md
  2. Se NENHUMA solution matched → marcar como "sem padrao" (gap na library)

Fase 4: EVALUATE — Pontuar aderencia

Para cada tela, avaliar 6 dimensoes (0-10 cada):

D1: Token Compliance (cores, fonts, spacing)

Ler ~/Claude/assets/design-library/UI_UX/raiz-educacao-design-system.md e verificar no screenshot + snapshot:

  • Cores da marca (Orange #F7941D, Teal #5BB5A2) presentes?
  • IBM Plex Sans como font principal?
  • Spacing consistente com escala 4px?
  • Border radius padrao (8px)?
  • Dark mode funcional (se aplicavel)?

D2: Solution Adherence (comparacao com spec)

Se solution matched:

  • Layout segue o diagrama ASCII da spec?
  • Props obrigatorias implementadas?
  • Features-chave presentes (ex: sparkline no KPI, filtros na tabela)?
  • CSS patterns alinhados com a spec?

D3: Component Quality (componentes base)

  • Usa shadcn/ui ou componentes do catalog? (vs HTML raw)
  • Botoes com estados (hover, disabled, loading)?
  • Inputs com labels e validacao visual?
  • Cards com estrutura consistente?
  • Icones do mesmo set (Lucide)?

D4: Responsividade

  • Desktop (1440px) legivel e alinhado?
  • Mobile (375px) funcional sem scroll horizontal?
  • Elementos nao sobrepostos?
  • Touch targets >= 44px em mobile?

D5: Acessibilidade Visual

  • Contraste suficiente (WCAG AA 4.5:1)?
  • Focus states visiveis?
  • Nao depende apenas de cor para transmitir info?
  • Alt text em imagens (via snapshot)?

D6: Consistencia Cross-Tela

  • Mesma sidebar/nav em todas as paginas?
  • Mesma paleta de cores (sem cores random)?
  • Mesma tipografia (sem fonts diferentes)?
  • Espacamentos uniformes entre paginas?

Score UXC (UX Compliance)

UXC = D1*0.20 + D2*0.25 + D3*0.20 + D4*0.15 + D5*0.10 + D6*0.10
UXCStatusSignificado
90-100ExcelenteTotalmente alinhado com Design Library
80-89BomPequenos desvios, aceitavel (threshold default)
65-79RegularDesvios significativos, precisa ajustes
50-64FracoImplementacao diverge bastante do padrao
< 50CriticoNao segue o padrao da empresa

Fase 5: REPORT — Gerar relatorio

Salvar em docs/ux-compliance-{date}.md:

# UX Compliance Report — {Projeto}

**Data**: YYYY-MM-DD
**URL**: {url}
**Telas avaliadas**: N
**UXC Score**: XX/100

## Resumo por Tela

| Tela | Solution Ref | D1 | D2 | D3 | D4 | D5 | D6 | Score | Status |
|------|-------------|----|----|----|----|----|----|-------|--------|
| /dashboard | dashboard-kpi | 8 | 7 | 9 | 8 | 7 | 9 | 79 | Regular |
| /usuarios | table-filters | 9 | 8 | 8 | 7 | 8 | 9 | 82 | Bom |

## Desvios Criticos (P0)

- [screenshot] Tela X usa cor #FF0000 em vez de #F7941D (token violation)
- [screenshot] Form sem labels (a11y violation)

## Desvios Importantes (P1)

- Tela Y nao usa KPI card padrao (reinventou componente)
- Spacing inconsistente no header (12px vs 16px padrao)

## Gaps na Design Library

- Tela Z nao tem solution equivalente → sugerir criacao de solution spec #25

## Screenshots

- `ux-compliance/dashboard-desktop.png`
- `ux-compliance/dashboard-mobile.png`
- ...

## Acoes Recomendadas

1. [P0] Corrigir cores para tokens do design system
2. [P1] Substituir KPI custom por `dashboard-kpi` solution
3. [P2] Adicionar nova solution spec para tela Z

Integracoes

Com ag-1-construir

Pode ser chamado na fase REVIEW para verificar compliance antes de SHIP:

REVIEW = ag-revisar-codigo + ag-avaliar-ux-design-library (se UI)

Com ag-7-qualidade (MERIDIAN)

Complementa D4-LOOKS com verificacao contra padrao interno:

  • MERIDIAN D4: "a tela parece boa?" (generico)
  • Este skill: "a tela segue NOSSO padrao?" (especifico)

Com ag-2-corrigir

Desvios P0/P1 podem ser passados como input para correcao automatica:

/ag-2-corrigir lista: [desvios do UX Compliance Report]

Regras

  1. SEMPRE capturar screenshots REAIS — nunca avaliar sem evidencia visual
  2. SEMPRE comparar contra a Design Library — nao usar padrao generico
  3. Se solution nao existe → e um GAP na library, nao um erro do projeto
  4. Score e relativo ao padrao interno — 100 = perfeitamente alinhado, nao "bonito"
  5. Mobile e obrigatorio — se nao cabe em 375px, e desvio
  6. Report com screenshots como evidencia — desvio sem screenshot nao conta

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

007

Free

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

See all skills by aibot88

Report a problem with this skill