Zavelinski

Use when starting any non-trivial task to pick the BEST available capability (skill, plugin, MCP connector, agent, workflow) instead of the first one that works. Maps relevant skills/MCPs/agents, compares, picks the highest-quality fit, announces it, then…

Use when the user says "godmode", "god mode", "/godmode", or wants max-capability mode for the session. Turns on exhaustive, best-tool-first behavior: map and use the BEST skill/plugin/MCP/agent, prefer Workflow/subagents for substantial work, verify before…

Use when the user says "godmode", "god mode", "/godmode", "ativa godmode", or wants max-capability mode for the session. Turns on exhaustive, best-tool-first behavior: map and use the BEST skill/plugin/MCP/agent, prefer Workflow/subagents for substantial…

Use when the user says "salve" (or /salve) to ship and persist the current work in one shot. Persists context, commits, pushes to GitHub, opens and merges a PR into the main branch, triggers/confirms the deploy if the project has one, fast-forward-updates the…

Use quando o usuario disser "salve" (ou /salve) para entregar e persistir o trabalho atual de uma vez. Persiste contexto, commita, sobe no GitHub, abre e mergeia um PR na branch principal, dispara/confirma o deploy se o projeto tiver, atualiza a checkout…

Use when the user asks for a weekly AI news digest / roundup / "what happened in AI this week", or says /weekly-ai-digest. Pulls the last 7 days of AI news from multiple sources (via the last30days plugin if installed, else WebSearch + Perplexity), dedupes…

When a task needs a specific format or style and zero-shot keeps drifting, give 2-5 carefully chosen examples instead of more instructions. Use for extraction/classification/formatting/tone tasks the model keeps getting subtly wrong. Trigger with…

To evaluate or compare outputs (candidate answers, PRs, drafts, model results) objectively, define an explicit rubric first and score each criterion with evidence, instead of a vibe "looks good". Use to pick the best of N options, gate quality, or grade…

When two components/services talk (API client+server, producer+consumer, module boundary), pin the contract they share and test BOTH sides against it, instead of only unit-testing each in isolation. Use on integration boundaries, API changes, microservices,…

When you MUST feed a large blob into context (a long log, transcript, doc, or dataset dump), compress it to the salient parts first instead of pasting it whole. Use before including big inputs you cannot avoid. Distinct from context-warden (session…

When an answer will be consumed by code or another step (not a human), define a schema first and make the output conform to it, instead of free text you then regex. Use for tool arguments, API payloads, extraction/classification results, agent-to-agent…

Before a commit, push, paste, or share, scan the diff/text for leaked secrets (API keys, tokens, private keys, passwords, connection strings) and block them, instead of leaking and rotating later. Use before any git push, before sharing logs/config, before…

For a contested or high-stakes answer, have several agents propose answers then critique each other across a couple of rounds until they converge, instead of trusting one model or a blind vote. Use on hard design calls, ambiguous root-cause debates, or claims…

For a complex problem, first decompose it into an ordered list of simpler subproblems, then solve them in sequence, feeding each answer into the next, instead of one-shotting the whole thing. Use on multi-step tasks, hard algorithmic problems, or anything…

Before shipping a factual or analytical answer, draft it, generate independent verification questions about its own claims, answer those, and revise the draft to fix what the checks expose. Use on research answers, multi-claim summaries, audits, anything…