Escrita e Conteúdo

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "th

Sincroniza e mantém as traduções em chinês do repositório anthropics/skills. É usado para puxar atualizações, traduzir SKILL.md (incremental ou completo), gerar o índice chinês INDEX_ZH.md e verificar a integridade da tradução.

Contrarian opinion piece (~800-1500 words). Stakes a position against conventional wisdom in your niche. Use when you have a real fight to pick — a widely-held belief in your space that you genuinely disagree with and can defend with evidence.

Formata artefatos de teste aprovados em documentos prontos para revisão e saídas importáveis para Gherkin, Xray, Zephyr, TestLink e TestRail.

Use when existing architecture documentation needs refreshing after code changes, when running periodic doc maintenance, or when user asks to "update docs", "refresh documentation", or "sync docs with code".

Norwegian plain language (klarspråk) guidelines from Språkrådet. Use when writing Norwegian website copy, marketing text, UI labels, documentation, or any user-facing Norwegian content. Triggers on Norwegian text, norsk tekst, klarspråk, markedsføring, nettsidetekst, brukergrensesnitt, or when reviewing/improving Norwegian copy quality.

Positioning and pitch copy generator for bootstrapped founders. Produces ready-to-paste copy — positioning canvas, one-liner, elevator pitch, homepage hero copy, value propositions, taglines, cold email opener, and language bank. NOT analysis — usable marketing artifacts. Use when user runs `/positioning`, asks about "positioning", "value proposition", "elevator pitch", "tagline", "homepage copy",

Use when reviewing novel chapters or manuscripts for logic consistency, character authenticity, plot cohesion, foreshadowing payoff, emotional resonance, narrative vividness, and content compliance. Also triggers for first-chapter editorial audits against web novel platform submission standards. Triggers on requests like "check the story", "review this chapter", "is this consistent with character"

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

Publishes a `status: ready` draft from the weekly calendar to its configured target (Astro blog collection) and archives social derivatives. Reads scribetronic/publish-config.yaml. Updates calendar history and per-week plan. Optionally archives completed weeks. Does NOT push to social platforms (out of scope v1).

Short-form comparison post (X / LinkedIn / Threads). Two things contrasted to reveal a non-obvious preference. Use when the user wants to publish an "X vs Y" take — tools, approaches, mindsets, frameworks — and stake a side. Pairs well after a hot-take or how-to long-form piece.