Convierte ideas vagas en planes aprobados y con decisiones completas, con estructura validada antes de codificar. Útil cuando los usuarios preguntan en cualquier idioma sobre planificación, arquitectura, dirección de diseño, viabilidad, juicio de valor o si vale la pena implementar una función antes de hacerlo. No para correcciones de errores o ediciones pequeñas.
El skill tw93/think está diseñado para que los agentes de IA, como Claude Code, Cursor o Codex, transformen ideas iniciales vagas en planes detallados, aprobados y con todas las decisiones tomadas antes de comenzar a codificar. Es especialmente útil cuando un usuario solicita asistencia en planificación, arquitectura, dirección de diseño, análisis de viabilidad, juicio de valor o evaluación de si una característica merece ser implementada. El skill guía al agente para estructurar y validar el plan de manera rigurosa, asegurando que todas las partes interesadas estén de acuerdo y que la implementación sea factible. No debe utilizarse para tareas de corrección de errores o ediciones menores, ya que su propósito es la planificación estratégica y la toma de decisiones fundamentadas. Funciona en cualquier idioma que el usuario emplee, manteniendo la coherencia y claridad en la comunicación del plan resultante.
npx skills add https://github.com/tw93/waza/tree/main/skills/thinkConvierte ideas vagas en planes aprobados y con decisiones completas, con estructura validada antes de codificar. Útil cuando los usuarios preguntan en cualquier idioma sobre planificación, arquitectura, dirección de diseño, viabilidad, juicio de valor o si vale la pena implementar una función antes de hacerlo. No para correcciones de errores o ediciones pequeñas.
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.
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask in any language for UI, page, component, frontend, typography, screenshot-grounded visual polish, or complaints that a screen looks unclear, ugly, inconsistent, or visually wrong. Not for backend logic or data pipelines.
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.
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.
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".