Produz UI de alto padrão e distinta para páginas, componentes, interfaces visuais, tipografia e refinamento com base em capturas de tela. Use quando usuários solicitarem, em qualquer idioma, UI, página, componente, frontend, tipografia, refinamento visual baseado em capturas de tela, ou reclamarem que uma tela está confusa, feia, inconsistente ou visualmente incorreta. Não é para lógica de backend ou pipelines de dados.
tw93/design é uma skill para agentes de IA (como Claude Code, Cursor, Codex) especializada em design de interface de usuário (UI). Seu objetivo é ajudar desenvolvedores a gerar interfaces visuais de produção, com foco em páginas web, componentes, tipografia e refinamento visual orientado por capturas de tela. A skill é acionada quando um usuário pede melhorias visuais ou relata problemas como telas confusas, feias ou inconsistentes, independentemente do idioma. Ela funciona processando descrições textuais ou imagens de capturas de tela para produzir código CSS, HTML ou sugestões de design que elevem a qualidade visual do projeto. Não deve ser usada para lógica de backend ou pipelines de dados, mantendo-se focada exclusivamente na camada de apresentação. Sua utilidade está em acelerar o ciclo de design e desenvolvimento, garantindo consistência e estética profissional sem exigir conhecimento aprofundado de design por parte do desenvolvedor.
npx skills add https://github.com/tw93/waza/tree/main/skills/designInstalled? Explore more Imagem skills: steipete/songsee, affaan-m/frontend-design, mattpocock/improve-codebase-architecture · View all 6 →
Produz UI de alto padrão e distinta para páginas, componentes, interfaces visuais, tipografia e refinamento com base em capturas de tela. Use quando usuários solicitarem, em qualquer idioma, UI, página, componente, frontend, tipografia, refinamento visual baseado em capturas de tela, ou reclamarem que uma tela está confusa, feia, inconsistente ou visualmente incorreta. Não é para lógica de backend ou pipelines de dados.
This repo contains 7 individual skills — each has its own dedicated page.
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask review/看看代码/合并前/看看issue/PR/release/push or to implement an approved plan, with safety gates for dirty and untracked worktrees. Not for exploring ideas, debugging root causes, or prose review.
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask 检查claude/检查codex/检查pi/配置检查/健康度 or report agents ignoring instructions, missing validation, or code becoming hard to maintain. Not for debugging code or reviewing PRs.
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Runs a six-phase research workflow that turns unfamiliar domains, source bundles, or collected material into publish-ready output. Use when users ask in any language to research, study, deep-dive, compile sources, synthesize unfamiliar material, or turn a source bundle into a coherent reference. Not for quick lookups or single-file reads.
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask 看这个链接/读一下/read this/check this URL. Not for local text files already in the repo.
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.
Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like wording, or prepare launch and social copy. Not for code comments, commit messages, or inline docs.
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.