Explorar skills

Automated blog content pipeline. Research, write, generate images, create WordPress draft, and prepare social media versions overnight. Wake up to a complete content package ready to publish.

Use when implementing any feature or bugfix, before writing implementation code

Check and strengthen the alignment between team-level goals (OKRs, KPIs) and company strategy. Use this skill when goals have been set but their connection to strategy is unclear, inconsistent, or contested.

Use when the user asks for root-cause-first debugging of bugs, test failures, flaky behavior, build issues, or integration defects with tracked verification and regression lock-down.

Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error h

Use when Claude Code needs to diagnose or fix a bug against active SpecDD specs.

Create structured QA round documents for manual testing phases. Generates tracking docs with issue logging, session planning, and verification workflows.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Uma investigação de causa raiz em 4 fases para qualquer problema técnico, como bugs, falhas de teste ou comportamento inesperado. Ela exige a identificação da causa raiz antes de tentar correções, não permitindo soluções aleatórias.

Run one or more dynamic-verification probes against a local ephemeral docker-compose mirror of the target system. Captures observation traces as committed artefacts at `lineage/{repo}/probe-runs/{date}-{probe_id}.yaml` and merges measured values back into `feature-flows.yaml`, `test-map.yaml`, and per-sidecar `confidence_per_field` annotations. Local-only execution per APPROACH.md section 5 rule 1

Run code review against design documents, checking acceptance criteria, security, performance, and test coverage. Use when reviewing implementation quality or running /review.

Coordinator that executes a plan in parallel groups via background subagents. Spawns implementers, then dedicated test-runner / static-analyse subagents, then routes failures back to the original implementer (SendMessage) or a fresh fixer. Fully autonomous — no human-in-loop.