FranLuciano04
@FranLuciano04
Public Skills
cerrar-modulo
by FranLuciano04
Barrera de revisión de un módulo de implementación de Rumbo. Prepara el pedido de review para Codex, arregla sus hallazgos confirmados en ramas fix/ (DEC-0019) y, con la aprobación del equipo, cierra el módulo con el tag mod-N. Usar cuando alguien pida cerrar o revisar el módulo MN, o diga que Codex ya terminó su review.
implementar-ticket
by FranLuciano04
Orquesta la implementación de un ticket de Rumbo con TDD (rojo → verde → refactor → review → fix) usando subagentes según la capa del ticket y el modelo que asigna, y lo cierra con un PR. Usar cuando alguien pida implementar, seguir o retomar un ticket T-NNN que ya tiene tomado.
review-de-ticket
by FranLuciano04
Criterios, orden de búsqueda y formato de salida para revisar el diff de un ticket de implementación de Rumbo. La precargan los subagentes reviewer-ticket y reviewer-seguridad dentro de /implementar-ticket; no se usa suelta.
security-and-hardening
by FranLuciano04
Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
pr
by FranLuciano04
Escribe y abre el pull request de un ticket de Rumbo con el formato fijo del proyecto (objetivo, trazabilidad, evidencia TDD, tests y cobertura, review, modelos, riesgo y checklist). La usa /implementar-ticket al cerrar cada ticket; también se puede invocar con /pr T-NNN desde la rama de un ticket.
test-driven-development
by FranLuciano04
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
code-simplification
by FranLuciano04
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
code-review-and-quality
by FranLuciano04
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.
debugging-and-error-recovery
by FranLuciano04
Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.
api-and-interface-design
by FranLuciano04
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
frontend-ui-engineering
by FranLuciano04
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
performance-optimization
by FranLuciano04
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
ci-cd-and-automation
by FranLuciano04
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
incremental-implementation
by FranLuciano04
Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
source-driven-development
by FranLuciano04
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
observability-and-instrumentation
by FranLuciano04
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
tomar-ticket
by FranLuciano04
Toma el próximo ticket de implementación de Rumbo con el semáforo de Git (push atómico a main), o uno puntual si se lo nombra. También libera tickets propios o vencidos. Usar cuando alguien quiera empezar a programar, pida «dame un ticket», «qué hay para hacer», «tomá T-NNN» o «liberá T-NNN».
planning-and-task-breakdown
by FranLuciano04
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
interview-me
by FranLuciano04
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
spec-driven-development
by FranLuciano04
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
shipping-and-launch
by FranLuciano04
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
documentation-and-adrs
by FranLuciano04
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
gestionar-skills
by FranLuciano04
Gestiona, instala, crea, actualiza y comparte skills de Claude Code para Rumbo. Usar cuando alguien pida agregar, instalar, eliminar, revisar o distribuir una skill o un plugin con skills.