Desenvolvimento

Voice of Customer program - multi-source signal collection, theming and prioritization, evidence-to-action routing, and product / CS / marketing feedback loop closure. Use when: voice of customer, VoC program, customer feedback, NPS / CSAT / CES, qualitative theming, feedback synthesis, product feedback loop, customer insight engine.

Analyze failing tests from the last /qf-run and fix the source code to make them pass. Use when the user runs /qf-fix, asks to "fix failing tests", or asks to "fix test failures". Requires result files from a prior /qf-run.

Use when the user wants to "solve a model", "run the algorithm", "compute the solution", "find the optimal", "prove this theorem", "implement the solver", "solve this problem", "what algorithm should I use", "optimize this", "find the answer", or needs to execute a mathematical solution with computational rigor. This is the solving engine for models produced by /uber-model.

On-demand sales battlecards for live competitive deals - positioning matrix, top objections with responses, trap questions, proof points, and a "do not say" list. Use when: competitor surfaced in deal, sales battlecard, competitive enablement, deal-specific battlecard, objection handling, competitive trap questions, why we win against, why we lose to, displacement playbook.

Environment health check and auto-remediation for vibe-* projects. Checks node_modules vs package.json drift, nested .git directories, Tailwind and shadcn version mismatches, dotenv load order, Vite HMR WebSocket config, husky hook permissions, ESLint config validity, TypeScript path resolution, and missing dependencies in generated code. Auto-remediates where safe. Flags where human action is nee

Fundamentos de bioestatística: estatística descritiva, distribuições, teste de hipóteses e intervalos de confiança para dados biológicos. Utilize ao analisar resultados experimentais.

Enforce low Cognitive Complexity (SonarSource) and low Cyclomatic Complexity in ALL code written or modified, in any programming language, framework, or platform. This skill MUST activate automatically whenever code is being written, generated, modified, or refactored — no explicit trigger needed. Triggers include writing any function, method, class, module, script, handler, endpoint, test, or cod

Use when defining a project's test approach, when choosing what gets tested at unit vs integration vs e2e level, when setting per-component coverage targets, when reviewing test quality, or when CI is slow / flaky and tests need a strategy reset.

Write an end-of-session recap to .claude/last-session.md. Triggered by /wrap, "wrap up", "recap this session", or automatically by the Stop hook via the .claude/.wrap-pending marker.

Use when visualizing systems, architectures, or concept flows — brand-aware Excalidraw authoring via compact DSL

Generates and maintains two changelog files from git tags, TASKS.md, DECISIONS.md, and feature folders. CHANGELOG.md at repo root is developer-facing in Keep a Changelog format with task IDs and decisions. CHANGELOG_CLIENT.md is plain English, grouped by "what you can now do", written like a product update — no task IDs or framework names. Version detection reads git tags first, then package.json

Comprehensive knowledge base for Kibana plugin development. Covers plugin architecture, server/client patterns, saved objects, embeddables, UI actions, expressions, state management, logging, HTTP resources, and inter-plugin communication. Use this skill when building, debugging, or maintaining Kibana plugins.