sergekostenchuk/ui-ux-agent-skill-system

ux-audit-skill

Audit existing UI screens, URLs, screenshots, Figma frames, HTML/CSS/React code, dashboards, mobile flows, and landing pages for UX, accessibility, responsive behavior, visual hierarchy, conversion blockers, state coverage, and regression risk.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill ux-audit-skill

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

UX Audit Skill

Use this specialist for evidence-backed review of existing UI artifacts. The output is a severity matrix and actionable refactor brief, not a generic design essay.

Operating Modes

  • review-live-url: audit a reachable URL with available browser/static evidence.
  • review-screenshot: audit image-only context without DOM claims.
  • review-code: audit source files and templates.
  • refactor-brief: convert findings into implementation tasks for another skill.
  • regression-check: compare before/after evidence and remaining risks.

Required Workflow

  1. Classify available evidence using references/audit-evidence-model.md.
  2. Apply references/severity-model.md before ranking findings.
  3. Use assets/audit-report.template.md for audit output.
  4. Use assets/regression-report.template.md for before/after checks.
  5. Apply ../../shared/privacy-policy.md before screenshots, Figma, or authenticated state.
  6. If a URL is available, reuse local scripts listed in ../../shared/tool_inventory.json.
  7. Label every finding by evidence type: DOM, screenshot, source, automated, or Manual.

Evidence Boundaries

  • Screenshot-only input cannot support DOM, Lighthouse, axe, or runtime claims.
  • Source-only input cannot prove rendered layout unless run or screenshot evidence exists.
  • Manual findings are allowed but must be labeled Manual.
  • Planned tools are not evidence.

Validation

bash
python3 $CODEX_SKILLS_DIR/.system/skill-creator/scripts/quick_validate.py $CODEX_SKILLS_DIR/ux-audit-skill
python3 $CODEX_SKILLS_DIR/senior-skill-architect/scripts/lint_production_skill.py $CODEX_SKILLS_DIR/ux-audit-skill

Output Shape

text
Audit target:
Evidence available:
Ran:
Skipped:
Severity matrix:
Top fixes:
Verification plan:
Privacy notes:
Residual risk:

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
sergekostenchuk
Community

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

Installazioni / 1h
1
GitHub Stars
35
Aggiornato
13 set
sergekostenchuk
Community

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

Installazioni / 1h
1
GitHub Stars
35
Aggiornato
13 set
sergekostenchuk
Community

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

Installazioni / 1h
1
GitHub Stars
35
Aggiornato
13 set
sergekostenchuk
Community

editorial-quality-gate

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

Installazioni / 1h
1
GitHub Stars
35
Aggiornato
13 set