Claude Skills by BipBop-Labs

Mejores prácticas de prompting para escribir y revisar prompts de agentes y features con LLM (destilado de Anthropic y adaptado a Revi). Úsala siempre que se escriba, edite o revise un system prompt, prompt de tool, o contenido dirigido a un LLM, y como referencia al revisar PRs que tocan prompts.

Crear commits atómicos y bien redactados desde un agente: revisar el diff real, elegir qué se stagea, seguir el estilo del repositorio y respetar los hooks. Úsala cuando la persona pide commitear, "haz un commit" o entrega un mensaje como guía.

Create or revise portable agent skills and validate their packaging. Use when adding a SKILL.md workflow for Claude Code, Codex, or ChatGPT, or when reviewing a skill for quality, safety, and distribution.

Knowledge base from \"Rocket Surgery Made Easy\" by Steve Krug: do-it-yourself usability testing to find and fix usability problems. Use when planning or running user tests, validating a concept or sketch early in discovery, recruiting participants, writing test tasks and scenarios, facilitating think-aloud sessions, involving stakeholders as observers, debriefing and prioritizing findings, choosing minimal fixes, or reviewing a test plan, script, or scenario for bias and clue-giving.

Escribir microcopy (botones, errores, vacíos, confirmaciones) siguiendo las convenciones de Revi. Úsalo al agregar o cambiar texto de UI, emails del producto, placeholders, mensajes de estado o CTAs.

Knowledge base from \"A Philosophy of Software Design\" by John Ousterhout. Use when designing or reviewing code for complexity, module depth, information hiding, interface design, error handling, comments, naming, or performance — or when a design decision needs a rationale beyond taste.

Abrir un pull request desde un agente con secciones estructuradas para quien revisa y para el cliente (resumen técnico, plan de pruebas y resumen en español). Úsala cuando la persona pide crear un PR o preparar su descripción.

Rewrites text so a reader with no context, no patience and no technical background gets it on the first read. Two levels: plain language (default) and easy read (maximum simplicity, for readers who struggle with text). Use when a message must land with non-technical users - client emails, release notes for non-developers, instructions for support or admin staff, in-app copy, error messages, onboarding docs - or when asked to \"make this simpler\", \"explain it like they have no idea\", \"leng...