Crie um resumo de design através de uma entrevista interativa, exploração do código e decisões de design de experiência. Salvo como um arquivo markdown no projeto. Use quando o usuário quiser escrever um resumo de design, planejar um novo recurso ou página, definir uma direção de UI ou mencionar "brief".
Esta skill, 'julianoczkowski/design-brief', é uma ferramenta para agentes de IA que permite criar briefings de design de forma colaborativa. Ela conduz uma entrevista interativa para coletar requisitos, explora a base de código existente para entender o contexto técnico e documenta decisões de design de experiência. O resultado é um arquivo markdown (.md) salvo diretamente no projeto, servindo como um artefato central para planejamento e alinhamento da equipe. É especialmente útil quando o usuário precisa iniciar um novo recurso, página ou definir a direção da interface do usuário, simplificando o processo de documentação de design diretamente no ambiente de desenvolvimento.
npx skills add https://github.com/julianoczkowski/designer-skills/tree/main/skills/design-briefCrie um resumo de design através de uma entrevista interativa, exploração do código e decisões de design de experiência. Salvo como um arquivo markdown no projeto. Use quando o usuário quiser escrever um resumo de design, planejar um novo recurso ou página, definir uma direção de UI ou mencionar "brief".
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".
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".
Run a structured design critique against the brief and codebase. Checks visual hierarchy, consistency, responsiveness, accessibility, and aesthetic fidelity. Use when user wants a design review, critique, QA pass, polish pass, or mentions "review" after building.
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".
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
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, or mentions "grill me".