Use when drafting an internal or external announcement — product launches, milestones, or policy changes. Produces a tone-appropriate (formal or casual) draft with hook, substance, reason, and call-to-action, suitable for Slack, email, or an internal blog post.
Use when preparing user-facing release notes from git history and PR metadata. Generates a Keep-a-Changelog-format document grouped by semantic version, translating commit jargon into user impact and filtering out internal-only changes.
Use when running the internal-comms team's weekly rhythm covering the leadership sync, an all-hands status update, and a conditional company-wide announcement. Bundles the week's artifacts into a single package markdown with distribution list and publish timestamps.
Use when an incident has been resolved and a blameless postmortem is needed. Reconstructs the timeline from Slack #incident- channels, logs, and PagerDuty, then drafts a structured postmortem with 5-whys root cause analysis and owner-assigned action items.
Use when given a meeting transcript (Otter, Granola, Zoom, Google Meet, or manually typed) and need structured notes. Extracts decisions, action items with owner and deadline, open questions, and key points — omits small talk and verbatim transcription.
Use when a new hire or transfer is joining a team and needs a structured onboarding document. Generates a Day 1 / Week 1 / Month 1 guide from repository README, CODEOWNERS, CI config, wiki pages, and team directory — including access checklist, reading list, first-PR target, glossary, and runbook index.
Use when a team needs a weekly (or ad-hoc) written status update covering shipped work, in-flight work, next steps, risks, and asks. Pulls from git history, PRs, and the project board, then drafts a 300-word update in plain language with no status-theater.
Use when the marketing team needs a weekly analytics rollup across GA4, Mixpanel, HubSpot, and social/email platforms. Produces a one-page digest with week-over-week changes, hypotheses for the changes, recommended next actions, and an explicit signal-vs-noise call on each metric.
Use when the marketing team needs a weekly competitive intelligence digest covering competitor content, positioning shifts, pricing changes, and product launches. Produces a dated digest with new content summaries, positioning deltas, pricing deltas, product moves, and a recommended response for each signal.
Use when a marketer gives you a content brief (topic, audience, goal, length) and needs a publish-ready blog post, case study, or whitepaper. Produces a structured draft with hook, thesis, scannable body, CTA, and meta description in the brand voice defined in references/brand-voice-guide.md.
Use when a marketer needs a full email sequence drafted (nurture, onboarding, re-engagement, or promotional) with subject line variants, mobile-first body copy, a single CTA per email, and CAN-SPAM/GDPR compliance baked in. Pulls from references/email-templates.md for proven sequence structures.
Use when running the marketing team's weekly content cycle end-to-end on a Mon-Fri cadence. Orchestrates competitor monitoring, long-form content, SEO, social, email, and analytics into a single weekly report.
Use when a page or post needs keyword research, intent classification, and on-page SEO review before publish. Produces a keyword map (seed to related queries with intent), on-page recommendations (title, meta, headings, links, alt text, schema), and a Core Web Vitals checklist.
Use when a marketer needs to atomize a pillar piece (blog post, launch, case study) into platform-native social posts for LinkedIn, X/Twitter, and the newsletter. Produces posts that match each platform's shape, with posting-time guidance and zero hashtag spam.
Use when a page or flow needs a WCAG 2.1 AA conformance audit. Runs axe-core against the live DOM via Chrome DevTools MCP, inspects the accessibility tree, verifies keyboard navigation and focus order, checks color contrast, ARIA roles, landmarks, headings, form labels, skip links, and alt text — and reports every…
Use when an OpenAPI 3.x specification (or URL to one) needs to be turned into a runnable API test suite. Generates Schemathesis property-based tests, REST-assured (Java) suites, or supertest (Node) specs covering positive, negative, auth, and rate-limit flows — and validates every response against the declared schema.
Use when a defect needs to be filed in a structured, reproducible format. Produces a bug report with an observed-behavior title, environment, numbered steps to reproduce, expected vs. actual, frequency, severity, priority, attachments, related tickets, and workaround. Enforces reproducibility before filing.
Use when a user story, acceptance criteria, or Jira ticket needs to be turned into a runnable Playwright or Cypress end-to-end test. Generates page-object-model specs with data-testid selectors, explicit waits, network mocking for edge cases, screenshot-on-failure, and inline accessibility assertions.
Use when preparing a release build for production and a complete pre-release QA sweep is required. Orchestrates API, E2E, performance, and accessibility testing, then consolidates results into a single release-readiness report with a go/no-go recommendation.
Use when a page, release candidate, or route needs a Core Web Vitals and Lighthouse audit with prioritized fix recommendations. Runs Lighthouse via Chrome DevTools MCP, captures a performance trace, analyzes long tasks and render-blocking resources, and produces actionable guidance per metric (LCP, INP, CLS, TTFB…
Use when realistic, seeded test data is needed from a JSON Schema, OpenAPI component schema, or database schema (PostgreSQL / MySQL / SQLite DDL). Generates reproducible records that honor constraints (unique, min/max, enum, foreign keys, formats) using faker libraries, and emits SQL inserts, JSON, or CSV. Supports a…
Use when a rep needs a battlecard against a named competitor for a live deal or quarterly enablement. Maps competitor positioning, ICP, pricing, differentiators, weaknesses, win/loss patterns, and public review sentiment into a one-page battlecard.
Use when a rep needs a personalized outbound email sequence grounded in a research brief. Produces a 3-step cold or 4-step warm sequence with subject lines under 45 characters, bodies under 120 words, one clear CTA per email, and no filler phrases.
Use when a rep needs a pre-outreach account brief on a named company. Produces a one-page dossier covering firmographics, tech stack, trigger events, hiring signals, known pain points, and three concrete outreach angles tied to triggers.
18 4mo agoA52 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: