Explorar skills

Hierarchical persistent planning for complex multi-phase development tasks. Use when the user requests tasks involving multi-file modifications, architecture refactoring, system design, or any work requiring detailed planning (tasks exceeding 5 tool calls). Creates a hierarchical plan directory structure: overview.md (global summary) + separate directories per phase (detailed specs, call chains, c

Deep methodology knowledge for STC including outcome regression, effect modifier selection, covariate centering, and comparison with MAIC. Use when conducting or reviewing STC analyses.

Writes or reviews UX copy — button labels, error messages, empty states, success messages, tooltips, form labels, onboarding text, confirmation dialogs. Voice-consistent, action-led, recovery-oriented. Localizable. No dark patterns.

Detecta textos gerados por IA identificando padrões característicos, frases e sinais estruturais de LLMs como ChatGPT e Gemini. Útil para auditar conteúdo, tornar a escrita de IA menos detectável ou compreender o que faz um texto soar como gerado por IA em diversos tipos de prosa.

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

Scaffold a complete Ansible role. Triggered by /new-role. Resolves role location from FQCN or path, asks whether multi-OS support is needed (RHEL, Solaris, Windows/WinRM), and generates a full role directory structure with realistic starter tasks, handlers, defaults, meta/main.yml, and OS-specific var files if requested. Shows summary before writing.

Transform acceptance criteria into plan-time runnable verification commands (behavioral, API, UI, error, config, data, contract types) with expected evidence shapes, then execute at verify time and assemble evidence bundles with honest completeness subsections (untested paths, known limitations, adversarial cases covered). Use when planning implementation against issue acceptance criteria or verif

Create technical implementation plans and architecture designs. Use when someone needs a detailed technical approach before coding begins — "create a plan", "plan this ticket", "how should we implement this", "technical design", "architect this", "design the approach", "plan the migration", "refactor plan", "how should we structure this", or when shaped work or a groomed ticket needs a concrete im

Defines the C# coding standards, patterns, and conventions to be applied consistently across all C# projects. Rules cover naming, structure, async patterns, null handling, dependency injection, logging, result patterns, and formatting. Apply these rules uniformly in all production code.

Use when diagnosing or resolving SAP performance problems — slow transactions, long-running batch jobs, expensive SQL, HANA resource issues, or general ABAP runtime bottlenecks.

Use when encountering any bug, test failure, or unexpected behavior — enforces root cause investigation before fixes. Prevents symptom-fixing, masking bugs, and "just try this" approaches. For code-forge features, use code-forge:fix instead.

Network meta-analysis in R, including network setup, consistency, treatment rankings, and league tables.