Pyroxin

Python-specific idioms, philosophy, and expert-level patterns. Use when working with Python code, including Jupyter notebooks (.ipynb). Covers Pythonic thinking, common pitfalls from other language backgrounds, testing ecosystem navigation, type hints trade-offs, and when to use modern Python features.

Systematic framework for rigorous, situationally-grounded decision analysis. Use when evaluating options with competing benefits where stated values may diverge from actual situational worth, when structural constraints rule out entire categories of value, or when the user wants a documented analytical process rather than a quick answer. Especially useful when early assumptions need challenging as

Git commit standards, branch strategy, and LLM-assisted development workflows. Use when making commits, managing branches, or working in high-velocity LLM-assisted development contexts. Covers atomic commits, conventional commits, branching strategies (trunk-based, GitHub flow), merge vs rebase decisions, and recovery patterns.

Logic programming thinking patterns and relational design principles. Use when working with logic languages (Prolog, miniKanren, Datalog, OWL2, Answer Set Programming) or applying declarative, constraint-based approaches in multi-paradigm systems.

Clojure-specific philosophy, idioms, and judgment frameworks. Use when working with Clojure code. Emphasizes data-oriented design, runtime validation with spec, REPL-driven development, and the philosophy of simplicity over ease.

Racket-specific tooling, libraries, idioms, and language-oriented programming philosophy. Use when working with Racket code. Emphasizes LOP, contracts, macros, and design methodology.

SWI-Prolog-specific tooling, standards, and idioms. Use when working with SWI-Prolog code. Emphasizes relational thinking, steadfastness, DCGs, constraints, and mandatory testing with PlUnit.

Functional programming principles, patterns, and practices. Use when working with functional languages (Racket, Clojure, Erlang, Haskell, Idris, Scheme, OCaml, F#, Elixir, etc.) without language-specific skills available, or when applying functional paradigms in multi-paradigm languages.

Core TDD philosophy and testing principles. Use when writing tests interactively or need testing guidance. Emphasizes tests as contracts, mock boundaries not internals, and implementation fixes over test changes.

Deprecated name; the skill formerly here is now opinionated-research:interactive-research. Retained as a context-level notice because Claude Code now ships a built-in deep-research workflow that runs one-shot, non-interactive fan-out research (no conversation after the report). interactive-research instead runs a persistent agent team you can keep questioning once the report lands. Guidance for Cl

Expert-level guidance for creating high-quality Claude Code skills. Use alongside Anthropic's skill-creator when creating new skills, improving existing skills, or needing guidance on skill content quality. Complements basic skill mechanics with research-driven content development, XML tag structuring, decision frameworks over mechanics, cross-references between skills, and systematic validation.

Object-oriented design principles, patterns, and practices. Use when working with object-oriented languages (Java, C#, C++, Python, Ruby, Swift, etc.) without language-specific skills available, or when applying OOP in multi-paradigm codebases.

Core software engineering philosophy and design principles based on Structure and Interpretation of Computer Programs (SICP). Use for all software development tasks including writing code, designing systems, refactoring, or making architectural decisions. MUST ALWAYS be loaded when working on any kind of software development or design task!

Pedagogical framework for teaching programming through Socratic dialogue. Use when a learner wants to LEARN programming rather than have code written for them. Triggers include "teach me", "help me understand", "I'm learning", "tutor mode", or requests to not provide solutions. Emphasizes productive struggle, graduated hints, metacognitive scaffolding, and emotional support.

Esta habilidad cubre patrones de desarrollo específicos de macOS, APIs de plataforma y marcos de decisión, incluyendo gestión de NSWindow, arquitectura NSDocument, sandboxing y patrones de UI. Es útil para desarrollar aplicaciones Mac, código Cocoa/AppKit, decisiones SwiftUI vs AppKit y consideraciones de Mac Catalyst.

Marcos de juicio y modismos críticos para scripting y automatización con Fish shell. Se enfoca en cuándo usar Fish vs bash, requisitos de compatibilidad macOS/Fedora y patrones específicos de Fish para prevenir errores, como anti-patrones de variables universales, funciones wrapper y guardas interactivas.

Herramientas específicas de Java, estándares de documentación, prácticas de prueba y modismos modernos. Úselo al trabajar con código o proyectos Java en la JVM.

Esta habilidad cubre modismos, herramientas y filosofía específicos de Swift, enfatizando la programación orientada a protocolos, la semántica de valor, la concurrencia estricta (Swift 6+) y las garantías de seguridad en tiempo de compilación para código Swift.