Realiza uma crítica de design estruturada com base no briefing e no código. Verifica hierarquia visual, consistência, responsividade, acessibilidade e fidelidade estética. Use quando o usuário desejar uma revisão de design, crítica, controle de qualidade, polimento ou mencionar 'revisão' após construir.
Este skill, denominado julianoczkowski/design-review, é uma ferramenta especializada para agentes de IA (como Claude Code, Cursor ou Codex) que automatiza a realização de uma crítica de design completa e estruturada. Ele analisa o código da aplicação e o briefing original para avaliar aspectos cruciais como hierarquia visual, consistência entre componentes, responsividade para diferentes dispositivos, acessibilidade (seguindo as diretrizes WCAG) e fidelidade estética em relação ao design pretendido. O principal objetivo é substituir uma revisão manual de design, fornecendo um feedback objetivo e detalhado diretamente no ambiente de desenvolvimento. O desenvolvedor pode invocá-lo simplesmente solicitando uma 'revisão de design', 'crítica', 'QA/polimento' ou mencionando a palavra 'revisão' após construir uma funcionalidade. A ferramenta percorre a base de código, identifica pontos de melhoria e gera um relatório com as falhas encontradas e sugestões de correção, acelerando o processo de garantia de qualidade visual e de usabilidade.
npx skills add https://github.com/julianoczkowski/designer-skills/tree/main/skills/design-reviewInstalled? Explore more Imagem skills: steipete/songsee, affaan-m/frontend-design, mattpocock/improve-codebase-architecture · View all 6 →
Executa uma crítica de design estruturada contra o briefing e a base de código. Verifica hierarquia visual, consistência, responsividade, acessibilidade e fidelidade estética. Use quando o usuário desejar uma revisão de design, crítica, controle de qualidade (QA), polimento visual ou mencionar "revisão" após construir uma funcionalidade.
This repo contains 7 individual skills — each has its own dedicated page.
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when user wants to write a design brief, plan a new feature or page, define a UI direction, or mentions "brief".
Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".
Generate a design tokens file (CSS variables or Tailwind config) based on a chosen aesthetic philosophy, with light and dark mode palettes, spacing scale, type ramp, and component-level tokens. Use when starting a new project, establishing a visual system, setting up tokens, or mentions "tokens" or "design system".
Build distinctive, production-grade frontend interfaces with high design quality, guided by named aesthetic philosophies. Use when building components, pages, or applications. Generates working code with exceptional attention to aesthetic details and creative choices that avoid generic AI output.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, challenge an approach, or mentions "grill me".
Define the structural layer of a product or site before visual design begins. Covers navigation, content hierarchy, page structure, URL patterns, and user flows. Use when user wants to plan site structure, define navigation, map user flows, organize content, or mentions "IA" or "information architecture".
Generate spectrograms and feature-panel visualizations from audio with the songsee CLI.
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Add documentation for a new AI provider — usage docs, env vars, Docker config, image resources.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
This skill should be used when the user wants to visualize data. It intelligently selects the most suitable chart type from 26 available options, extracts parameters based on detailed specifications, and generates a chart image using a JavaScript script.