bonny

Writes blog posts for simple-history.com matching the author's voice and style. Use when drafting posts, announcements, or marketing copy.

How to design and regenerate marketing screenshots for the wordpress.org plugin page (banner-1544x500.png, screenshot-1.png, etc). Covers the event mix that converts, the reproducible WordPress Playground pipeline that bakes it, and every non-obvious gotcha from previous shoots. Use when refreshing screenshot-1.png, banners, or any image showing the Simple History event log.

Query Google Analytics (GA4) for simple-history.com traffic, top pages, referrers, and the premium_* UTM campaigns that tag admin links. Use when the user asks about visits, traffic sources, which admin links lead to the site, upsell click-through, or campaign performance.

Adds changelog entries to readme.txt following keepachangelog format. Use when updating the Unreleased section or documenting changes for a release.

Guidance for writing and running tests in Simple History. Covers which framework to use, how to run existing tests, and how to create new ones (including the codegen recording workflow).

Surface and triage local issues that are safe and quick for an AI to implement and easy for a human to verify. Use when the user wants to "knock out issues", asks for "quick wins", "low-hanging fruit", "what's easy to do right now", or wants a batch of small tasks to work through in one session.

Guides implementation of structured action links on log events. Use when adding get_action_links() to a logger or migrating from get_log_row_details_output().

Use for quick local testing with WordPress Playground CLI. Spins up a disposable WordPress instance with the plugin mounted — no Docker needed. Ideal for worktrees, quick feature checks, and parallel testing on different branches.

Kolla produktionsserverns hälsa — CPU, minne, disk, Docker-containrar och Redis — via SSH till Hetzner. Använd när användaren frågar saker som 'hur mår prod', 'kolla cpu på prod', 'redis health', 'är allt OK på servern', 'docker stats prod'. Subkommandon: (tomt)/all, cpu, mem, disk, docker, redis.

Hantera projektets todos i `todo.md` + `todos/`. Använd när användaren frågar/ber om todos — t.ex. 'vad är nästa todo', 'vilka todos har vi', 'visa todo #N', 'markera #N klar', 'avfärda #N', 'skapa todo …'. Subkommandon: (tomt)/list, next, show <nr>, done <nr>, reject <nr>, new <titel>.

Use after editing any Markdown (.md) file in this repo. Kör `prettier --write` på de ändrade filerna så formatering (radbrytning, tabeller, listor) blir konsekvent. Gäller README, AGENTS.md, CLAUDE.md, docs/, todos/ och allt annat .md.

Läs och bearbeta Obsidian-dokumentet `Inbox Brottsplatskartan.md` — snabba idéer/anteckningar användaren har dumpat på språng. Använd när användaren ber om att kika i inboxen, hämta nya idéer, skapa todos från inboxen, t.ex. 'kolla inboxen', 'vad ligger i inboxen', 'skapa todo från inbox #N', 'töm inboxen'. Subkommandon: (tomt)/list, show <nr>, todo <nr> [titel], remove <nr>, process.

Use after editing any PHP file in this Laravel project. Kör `composer analyse` (PHPStan/Larastan level 5 via Docker) och rapportera nya errors innan arbetet marks som klart. Gäller alla .php-ändringar under app/, routes/, config/, database/, tests/.

Use after skapande eller editering av shell-script (.sh, .bash, eller skript med shebang #!/usr/bin/env bash / #!/bin/sh). Kör `shellcheck` på de ändrade filerna och åtgärda warnings innan arbetet anses klart.