All authors
Claude Skills by BipBop-Labs
github.com/BipBop-Labs16 skills1 installs28 views
- Best PromptingMejores prácticas, agnósticas al modelo, para escribir y revisar texto dirigido a un LLM. Úsala siempre que se escriba, edite o revise un system prompt, una descripción de tool, un brief para un subagente, un archivo de instrucciones para agentes o un prompt de compactación, al depurar un prompt que no se comporta como se espera, y al revisar PRs que tocan prompts.Votes: 0GitHub stars: 3
- CommitCrear 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.Votes: 0GitHub stars: 3
- Create SkillsCreate 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.Votes: 0GitHub stars: 3
- Krug Usability TestingKnowledge 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.Votes: 0GitHub stars: 3
- MicrocopyEscribir 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.Votes: 0GitHub stars: 3
- Ousterhout Software DesignKnowledge 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.Votes: 0GitHub stars: 3
- PrAbrir 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.Votes: 0GitHub stars: 3
- Simple WritingWrites and 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 ide...Votes: 0GitHub stars: 3
- AdrRules for reading existing ADRs and deciding whether a new ADR is warranted. Use when working under an existing ADR, evaluating an important lasting design constraint, or discussing ADRs. A dependency, schema, interface, or implementation change alone does not warrant a new ADR.Votes: 0GitHub stars: 3
- DistillFind qualifying lasting design constraints in code and history, filter out implementation-only or already documented choices, rank remaining candidates, and triage each with the user as accept (write ADR), accident (known debt), reject, or skip, with resumable state. Use when the user runs /adr:distill or asks to bootstrap, extract, or derive ADRs from existing code.Votes: 0GitHub stars: 3
- InitSet up Architecture Decision Records in the current repository (folder, template, index, known-debt log, CLAUDE.md or AGENTS.md pointer, optional validation hook). Use when the user runs /adr:init or asks to add, bootstrap, or wire up ADRs. Idempotent and adopts existing ADR folders.Votes: 0GitHub stars: 3
- NewRecord a new Architecture Decision Record from the current conversation or diff, with context, options, decision, and consequences confirmed by the user, including updating or consolidating related ADRs. Use when the user runs /adr:new, says "write an ADR for this", or asks to record a lasting architectural constraint. Apply the standing eligibility filter before drafting.Votes: 0GitHub stars: 3
- ReviewCheck the current diff or branch against accepted Architecture Decision Records and flag likely violations, changes that need a new ADR, and touches to known debt. Report only, never block or fix. Use when the user runs /adr:review or asks whether a change respects the ADRs or design decisions.Votes: 0GitHub stars: 3
- Research FirstAntes de hacer una tarea, investiga en internet cómo la resuelve la industria (estándares, regulaciones, guías oficiales, patrones establecidos, prior art, código open source e implementaciones similares, y errores conocidos), destila lo encontrado en un brief con fuentes y después hace la tarea apoyada en ese brief. Úsala cuando la persona la mencione dentro de su petición, o pida "investiga primero", "busca cómo se hace", "qué dice la industria", "cuáles son los estándares", "qué regulación...Votes: 0GitHub stars: 3
- Test AuditUse whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.Votes: 0GitHub stars: 3
- Writing Simplified Technical EnglishWrite English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and pro...Votes: 0GitHub stars: 3