Explorar skills

Root cause analysis for software bugs in large legacy codebases. Use this skill WHENEVER the user asks WHY a bug happens, asks for RCA, mentions root cause analysis, says /bug.why, /bug.investigate, asks "why is this failing", "find the root cause", "trace this exception", "investigate this bug", "post-incident review", or pastes a stack trace, error log, exception, NullReferenceException, SqlExce

Use when asked for "deep research", "thorough analysis", "comprehensive report", "investigate", "due diligence", or when multiple sources are needed to answer complex questions. Produces well-sourced research reports through iterative refinement.

{{ 𝛀𝛀𝛀 }} Investigate a codebase in detail

Writing style guide for Jason Warren. Use this skill whenever writing prose, reports, documentation, or any substantive text for Jason — including drafting sections, editing existing content, or rewriting passages. Also use when Jason asks you to review or improve writing. Trigger on any request involving writing, drafting, editing, or composing text that isn't purely code. This includes github Pu

Systematic 5-step debugging flow for Next.js 15 + React 19 + TypeScript apps. Load when a UI bug is reported, hydration error appears, Server Action returns wrong data, or cache invalidation fails. Forces layer isolation (server vs client, action vs component, cache vs render) before touching code — prevents "fix here, break there" cascades.

Invoke any time a user is writing iOS/Swift tests or asking why tests behave a certain way — including XCTest versus Swift Testing (@Test/#expect) choices, async ViewModel tests with @Observable or @Published, snapshot testing across device sizes, mocking protocols for dependency injection, setUp/tearDown lifecycle issues, tests that fail on CI but pass locally, flaky async tests, testing VIPER/TC

Generate an annotated ansible.cfg for a specific environment. Triggered by /new-conf. Asks for target environment (dev, CI, or AWX) and generates a fully annotated ansible.cfg covering all official sections including defaults, privilege escalation, SSH connection, vault config, callback plugins, and fact caching. Shows summary before writing.

Use when executing iterative tasks, continuous improvement, quality assurance, process optimization, or when user asks to 'apply PDCA', 'iterate and improve', 'continuous improvement cycle', 'plan-do-check-act'.

Um motor anti-clichê para escrita de IA que, com um método de escrita central (3 tipos de núcleo), 7 ferramentas, 7 verificações de qualidade e técnicas "golden finger", garante que romances gerados por IA não tenham um "sabor de IA". Validado em 47 capítulos, é compatível com Claude Code, Cursor e Windsurf.

CRM-style contact and deal pipeline management. Use this skill when the user wants to manage contacts, track deals, schedule follow-ups, or export contact lists.

Shape rough ideas into clear, actionable work definitions. Use this skill whenever someone has an unstructured idea that needs to become a concrete work definition — feature requests, bug reports, PRDs, customer feedback, Slack threads, stakeholder asks, or vague "we should do X" statements. Trigger phrases include "shape this", "scope this", "write a PRD", "define this work", "turn this into a ti

Use when designing, building, or troubleshooting solutions on SAP Business Technology Platform — subaccounts, Cloud Foundry, Kyma, CAP, HANA Cloud, XSUAA, destinations, or any BTP service.