Categories
Indexed Skills (32)
adr
Trigger: ADR, architecture decision record, technical decision. Create ADRs that document context, options, rationale, consequences, and trade-offs.
buildable-issue
Creates agent-ready GitHub issues that are ready to build. Formerly framed as sdd-issue / SDD-ready issue creation. Use when creating a buildable issue, implementation-ready ticket, SDD-ready issue, preparing work for an orchestrator, or when the user says "create an issue", "write a ticket", or "I need to build X". Also use when the user references an existing issue and wants it enriched with scope, constraints, acceptance scenarios, and technical context.
design-patterns-pragmatic
Trigger: design patterns, GoF patterns, Java patterns, strategy, adapter, factory, builder, decorator, observer. Choose patterns only when they solve real design forces.
english-tutor
Trigger: explicit English tutoring, correction, practice, or /english. Improve user-provided English while preserving intent and privacy.
java-api-design
Trigger: Java API design, public API, encapsulation, modules, visibility, contracts, binary compatibility. Design Java APIs with clear boundaries.
java-clean-code
Trigger: Java clean code, Java naming, Java readability, Java style, Java maintainability. Improve Java code clarity using modern Java and official guidance.
java-exception-robustness
Trigger: Java exceptions, error handling, try-with-resources, resource cleanup, checked exceptions, robustness. Design Java failure handling safely.
java-immutability-modeling
Trigger: Java immutability, records, value objects, defensive copies, mutable collections, DTO modeling. Model Java data safely and clearly.
java-refactor-engram-contract
Trigger: Java refactor Engram contract, anchor-first topic keys, java-refactor-anchor-first. Centralize phase handoff and evidence rules.
java-secure-coding
Trigger: Java secure coding, Oracle Secure Coding Guidelines, input validation, trust boundaries, deserialization, least privilege, sensitive data. Review Java code for secure implementation practices.
java-solid-design
Trigger: Java SOLID, Java OO design, SRP, OCP, LSP, ISP, DIP, composition over inheritance. Evaluate Java object-oriented design tradeoffs.
java-testing
Trigger: Java tests, JUnit, Mockito, AssertJ, legacy code, characterization tests, seams. Generate and retrofit Java tests safely.
prd-light
Trigger: PRD light, quick PRD, lightweight PRD, MVP requirements. Create lightweight PRDs for small features, internal tools, and early ideas.
prd
Trigger: PRD, product requirements, technical product spec. Create rigorous PRDs for high-stakes, cross-team, regulated, or security-sensitive work.
programming-practices-core
Trigger: programming best practices, clean code, DRY, KISS, YAGNI, readability, maintainability. Evaluate general code quality without depending on language-specific skills.
prompt-evaluator
Trigger: prompt review, prompt evaluation, improve prompt, evaluar prompt. Refine prompts for clearer LLM execution.
refactor-java
Comprehensive catalog of 60+ Java refactoring techniques for behavior-preserving code improvements. Trigger when the task is Java refactoring, code-smell cleanup, restructuring, API-compatible design improvement, or a named refactoring technique. This skill is the right lazy-load signal when the worker must preserve observable behavior, check public-contract compatibility, apply useful-only JavaDoc, and produce one Java Refactor Quality Gate verdict. Covers Java 8 and Java 11+ examples for every technique. Even if the user just pastes Java code and asks for improvement suggestions, use this skill to identify applicable techniques. También se activa en castellano: "refactorizar", "refactorizar código Java", "mejorar este código", "malos olores del código", "olores de código", "código sucio", "limpiar código", "simplificar condicionales", "principios SOLID", "cómo mejorar este código", "código limpio", "reestructurar clase", "mejorar calidad del código", "técnica de refactorización", "extraer método", "renombra
refactor
Cross-language catalog of 62+ refactoring techniques based on Martin Fowler's "Refactoring" and Alexander Shvets' "Refactoring Guru". Detects the project's language automatically and provides idiomatic examples. Works with Java, Python, TypeScript, JavaScript, C#, Go, Kotlin, Ruby, PHP, Rust, Swift. Use this skill whenever the user asks to refactor code, improve code quality, eliminate code smells, simplify conditionals, restructure classes, improve API design, or apply any named refactoring technique. Also trigger when the user mentions code smells, legacy code improvement, clean code practices, SOLID principles, or asks "how can I improve this code". Even if the user just pastes code and asks for improvement suggestions, use this skill to identify applicable techniques. También se activa en castellano: "refactorizar", "refactorizar código", "mejorar este código", "malos olores del código", "olores de código", "código sucio", "limpiar código", "simplificar condicionales", "principios SOLID", "cómo mejorar es
refactorch-phases
Shared RefactorCh phase contracts for Engram topic keys, artifact references, handoff envelopes, and phase-to-phase persistence. Trigger: refactorch phase contract, refactorch Engram handoff, target brief, refactor plan, gate review.
rfc
Trigger: RFC, request for comments, technical proposal. Create RFCs for feature designs, engineering changes, trade-offs, alternatives, and open questions.
scout
Trigger: scout Project Profile, refactorch profile, Project Profile refresh. Build or refresh reusable RefactorCh Project Profiles.
service-boundary-analysis
Trigger: service boundary analysis, microservice inputs/outputs, API/consumer/output mapping. Inspect backend service boundaries with evidence and confidence.
summarize
Expert in pedagogical book chapter synthesis. Use this skill WHENEVER the user wants to summarize a book chapter, analyze text or document content, study a chapter, extract key ideas from a reading, or when they mention words like "summary", "chapter", "book", "analyze this text", "summarize this", "cornell", "TL;DR" of long-form content. Also trigger when the user uploads a PDF, EPUB, or document and asks to understand or study it in parts. También se activa en castellano: "resumen", "resumen del capítulo", "resumir esto", "resumir el capítulo", "analizar este texto", "capítulo", "libro", "ideas clave", "resumen del libro", "estudiar el capítulo", "síntesis", "notas cornell", "extraer ideas principales", "dame un resumen", "qué dice este capítulo", "resumir documento", "analizar lectura".
tcr
Implements the TCR (Test && Commit || Revert) methodology for ultra-short, safe commits during refactoring and development. Use this skill whenever the user wants to apply TCR, make atomic commits after each green test, commit frequently during refactoring, or follow a test-driven commit workflow. Also trigger when the user mentions "TCR", "test and commit", "commit after each test", "atomic commits", "micro commits", "revert on red", or asks for a disciplined commit cadence during code changes. También se activa en castellano: "test y commit", "commitear tras cada test", "commits atómicos", "micro commits", "revertir en rojo", "commits pequeños", "flujo TCR", "metodología TCR", "test verde y commit".
whisper-extract
Extract, transcribe, and summarize audio or video files using OpenAI Whisper. Use this skill whenever the user wants to transcribe audio or video, extract what was said in a recording, get a transcript of a meeting/interview/lecture/podcast, or generate a summary of spoken content. Also trigger when the user mentions files like .mp3, .mp4, .wav, .m4a, .ogg, .flac, .webm, .mkv, .mov and wants text out of them. Generates a .md file with an AI summary followed by the full literal transcript. También se activa en castellano: "transcribir", "transcripción", "extraer audio", "qué dice este audio", "transcribir reunión", "transcribir entrevista", "pasar audio a texto", "resumir grabación", "transcribir este video", "extraer texto de audio", "transcript", "whisper", "grabar y resumir".
write-ac
Generate structured Jira acceptance criteria in Gherkin format (Given/When/Then). Use when the user wants to define, write, or create acceptance criteria for a Jira task, story, or ticket. Triggers include "acceptance criteria", "AC", "write the ACs", "define ACs for", or any request to document expected behavior as testable conditions. También se activa en castellano: "criterios de aceptación", "CA", "escribir los criterios", "definir criterios de aceptación", "crear los CA", "ACs del ticket", "criterios Gherkin", "dado cuando entonces", "condiciones de aceptación", "escribir los ACs", "generar criterios", "criterios para esta historia", "definir los criterios".
usm
Trigger: USM, user story map, story map, mapa de historias, MVP slice. Create journey-first story maps with MVP slicing and Mermaid output.
jira-spike
Create or refine Jira Spike tickets in Jira Markup. Use when the user wants a Spike, research ticket, investigation ticket, technical exploration, discovery work, research question, or SDD-ready Spike input.
jira-task
Create or refine Jira Task tickets in Jira Markup. Use when the user wants a Jira Task, technical task, implementation task, maintenance task, operational work item, developer-ready task, acceptance criteria for a task, or SDD-ready Task input.
jira-user-story
Create or refine Jira User Story tickets in Jira Markup. Use when the user wants a user story, story ticket, product capability, end-user outcome, acceptance criteria for a story, developer-ready story, or SDD-ready User Story input.
teach-me
Trigger: teach me, enseñame, aprender, seguimos con. Tutor any topic with curriculum, Engram progress, spaced repetition, and practice-first checks.
spike
Generate well-structured Jira Spike tickets in Jira Markdown syntax. Use when the user wants to create a spike, investigation task, technical research task, or feasibility study for Jira. Triggers include requests like "create a spike", "write a Jira spike", "I need a spike for [topic]", or any request to document a technical investigation or research task as a Jira ticket. También se activa en castellano: "crear un spike", "escribir un spike", "spike de investigación", "tarea de investigación", "investigación técnica", "spike en Jira", "necesito un spike para", "estudio de viabilidad", "ticket de investigación", "spike técnico", "hacer un spike", "documentar investigación", "crear tarea de investigación".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.