Skills publicadas
refactoring
Safe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct.
code-review
Structured code review focusing on correctness, security, and maintainability. Correctness before style. Every reviewer comment must be actionable.
surgical-changes
Enforces minimal code modifications — touch only what you must. Prevents drive-by refactoring, comment deletions, and style changes unrelated to the task.
test-driven-development
Red-green-refactor cycle with meaningful coverage. Tests are written before implementation. Coverage is a side effect of good tests, not the goal.
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.
prompt-injection-defense
Guards AI agents and LLM-powered applications against prompt injection attacks — both direct and indirect. Validates AI inputs and outputs at every trust boundary.
security-hardening
Applies OWASP Top 10, secrets management, and least-privilege principles before any code ships. Security is a build step, not an afterthought.
simplicity-first
Prevents overengineering by enforcing minimum viable code. No speculative features, no premature abstractions, no unnecessary complexity.
api-design
Design stable, versioned, self-documenting APIs. Easy to use correctly, hard to use incorrectly. Apply Hyrum's Law from day one.
multi-agent-orchestration
Designs and coordinates multi-agent pipelines where specialized agents collaborate to complete complex tasks. Includes communication protocols, failure handling, and state management.
task-decomposition
Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.
ai-output-validation
Validates, parses, and sanitizes AI-generated outputs before they reach end users or downstream systems. Structured output enforcement, schema validation, and fallback handling.
code-explanation
Get layered, context-aware explanations of unfamiliar code. Understand what it does, why it was written that way, and how to work with it safely.
documentation
Document decisions, not just implementations. ADRs for architectural choices, inline docs for non-obvious code, and runbooks for operational knowledge.
goal-driven-execution
Transforms imperative instructions into declarative goals with verifiable success criteria. Enables autonomous looping until verified completion.
hallucination-prevention
Detects and mitigates LLM hallucinations in production pipelines. Validates AI-generated facts, code, and decisions before they reach end users or downstream systems.
performance-optimization
Measure first, optimize second. Data-driven performance improvements with before/after benchmarks and production validation.
ci-cd-pipelines
Automated quality gates from commit to production. Every merge to main is potentially shippable. No manual steps in the deployment path.
error-handling
Graceful degradation and meaningful error messages. Errors are first-class citizens, not afterthoughts. Every error path is designed, not discovered.
frontend-engineering
Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.
integration-testing
Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.
production-deployment
Zero-downtime deployments with pre-flight checks, staged rollouts, and rollback plans. Never ship to production without a verified rollback strategy.
idea-to-spec
Converts vague ideas into concrete, testable specifications with acceptance criteria. No implementation begins without a spec.
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
research-and-summarize
Distill complex topics into layered, actionable summaries. Start with the key insight, layer in detail, end with recommended next action.
think-before-coding
Forces explicit reasoning before writing any code. Surfaces assumptions, manages confusion, and prevents hallucination by demanding clarity upfront.
context-loading
Load minimum necessary context into agent context windows. Prevents token bloat, reduces cost, and improves focus. Only load what the current task needs.
debugging-methodology
Systematic root cause analysis for production and development bugs. Hypothesis-driven debugging — never guess-and-check.
incremental-coding
Build in verifiable increments. Never implement more than can be tested right now. Ship partial working systems over complete broken ones.
observability
Structured logging, distributed tracing, and alerting for AI systems and traditional services. You can't fix what you can't see.
rag-and-memory
Patterns for Retrieval-Augmented Generation (RAG) and agent memory systems. Retrieves only relevant context, prevents context bloat, and maintains coherent state across sessions.
Alerta por categoría