codebend3r

Use when accessibility is the subject in this repo. Triggers include "is this accessible", "run an a11y audit", "check WCAG", "screen reader", "keyboard navigation", "can you Tab to the map", "the family tree needs keyboard support", "add aria labels", "is…

Use when `main` has moved and the local feature branches or worktrees are stale in the-known-world repo — "rebase all branches", "rebase the worktrees", "sync the branches with main", "main was updated", "run active-rebaser", "get the feature branches caught…

Use when adding, moving, renaming, or reviewing a React component in this repo. Triggers include "add a component", "scaffold a new component", "create components/Foo", "does this component follow the conventions", "why is there no test for X", "check the…

Use when populating, filling in, seeding, or writing up a house or a character in the-known-world repo — e.g. "populate House Crakehall", "fill in `crakehall.md`", "populate Eddard Stark", "seed Cersei", "write up Robert Baratheon" — i.e. turn a stub or thin…

Use when deciding which content entries to populate next in this repo. Triggers include "what should I write next", "which characters are still stubs", "how many placeholders are left", "find the empty entries", "what's worth populating", "prioritize the…

Use when authoring, correcting, or checking a date in this repo. Triggers include "what era should this be", "is this date right", "the timeline is stretched", "this entry sorts in the wrong place", "should this be BC or AC", "what precision do I use", "I…

Use when naming, creating, or renaming a git branch in the-known-world repo — "new branch called X", "make a branch for Y", "start a branch", "rename this branch", or any `git checkout -b` / `git switch -c` / `git branch -m`. Enforces flat kebab-case names of…

Use when authoring, amending, squashing, fixup-ing, rebasing, or cherry-picking any git commit message in the-known-world repo, and when creating, titling, describing, or updating a GitHub pull request there (`gh pr create` / `gh pr edit`, or after pushing…

Use when adding or changing logic in kasane's `src/data/`, `src/state/`, or `src/api/` layers, or when asked to add test coverage, write unit tests, or verify pure functions in this repo.

Use when cutting a kasane release — bumping the version, tagging, shipping the web build to Netlify, producing Tauri desktop binaries, or building for iOS/Android. Also use when asked why the store version differs from `package.json`.

Use when asked whether kasane is due for a version bump — "should we bump the version", "check main for a bump", "run the version bumper" — or after merging work into main and wondering if the release version is stale. Decides patch vs minor vs major, asks…

Use when local main has just been updated — pulled, fast-forwarded, merged a PR, or reset — and the other branches and worktrees are now behind it. Also use when asked to "rebase everything", "catch the branches up", or "run the active rebaser".

Use when checking kasane's catalog for bad arc mappings — after inserting or editing a series in Supabase, before cutting a release, when a user reports an episode pointing at the wrong chapter, or when asked to "audit the catalog", "check the mappings", or…

Use when adding a new show's arc mapping — i.e., the user asks to "map <show>", "add a mapping for <show>", or the catalog has no entry for the show. Covers AniList GraphQL ID/count lookup, web research for arc boundaries, and inserting the `series` +…

Use when writing a git commit message or pull request title, before invoking `git commit`, `git commit --amend`, `git rebase`, `git cherry-pick`, or `gh pr create`.

Use when changing a series that already exists in the catalog — a new season aired, the manga published past the last mapped arc, an arc boundary was wrong, a film is missing, or the `mapping-audit` script reported an error to fix. For a series with no…

Use when wizteros user-facing copy has to be checked against the server-cost contribution framing, or when asked "audit the copy", "is this copy safe", "compliance check", "review the landing page copy", "does this wording cross the line". Also triggers on…

Use when the media stack containers on the Synology docker hosts need to move to their latest images — Sonarr, Radarr, Sabnzbd, Prowlarr, Lidarr, Seerr, Audiobookshelf, Bookshelf. Triggers include "update the arr stack", "update sonarr and radarr", "pull the…

Use when the wizteros invitation set needs checking — the four per-tier baseline links, their expiry, their scope, or whether the 03:00 rotation is still running. Triggers include "audit the invitations", "check the invite links", "are the baseline invites…

Use when one wizteros member has an access, invite, or billing problem that needs diagnosing before anything is changed. Triggers include "X paid but can't watch", "resend the invite for Y", "why was Z disabled", "member says they were charged", "look up…

Use when looking for membership growth opportunities among people who already showed interest and did not convert. Triggers include "find sales opportunities", "who should we win back", "draft a win-back email", "anyone we can re-invite", "who declined and…

Use when asked whether the wizteros production stack is working, without deploying anything. Triggers include "is the stack healthy", "are webhooks failing", "is everything up", "why did no invite go out", "morning check", "is the bridge alive", "did Stripe…

Use when checking whether Stripe, the stripe-bridge store, and Wizarr still agree about who is paying and who has access, on a routine sweep or after a Tailscale Funnel or bridge outage. Triggers include "reconcile stripe with wizarr", "who is paying but not…

Use when the wizteros live end-to-end suites are in play, either running them or deciding whether they should be run at all. Triggers include "run the e2e tests", "retest the flow", "verify tiers against live wizarr", "is the invite flow still working", "e2e…

Use when a court-vision page feels slow, when a branch touches pages, layouts, data fetching, or perf-budget.json, when the CI perf job fails, or when asked whether load times are inside the acceptable threshold. Covers running the budget check, reading a…

Use when main has moved locally in court-vision and the other branches are now stale, or when asked to rebase every branch and worktree onto main. Covers the per-branch rebase, when a conflict may be resolved versus abandoned, and the force-with-lease push…

Use when authoring, amending, squashing, fixup-ing, rebasing, or cherry-picking any git commit message, or when creating or editing a pull request title, in court-vision. Covers the mandatory `CV:` prefix on commit subjects AND PR titles, bullet style,…

Use when asked whether court-vision is due for a version bump, when main has taken on work since the last v* tag, or when cutting a release. Covers deciding patch vs minor vs major from the commit log and applying the bump.

Use when adding or changing a test in court-vision, when a new lib module or component needs its co-located test, or when a bun:test run fails in a way that looks like an environment problem rather than a real assertion failure.

Use when authoring, amending, squashing, fixup-ing, rebasing, or cherry-picking any git commit message in the crammr repo (path contains `crammr`). Covers the mandatory `CRMR:` subject prefix, bullet style, brevity, backticks, and agent attribution removal.

Use when splitting a single crammr quiz module into three difficulty-level modules (`<lang>-1/2/3` with display names `<Lang> — Level 1/2/3`) in the `crammr` repo (path contains `crammr`). Triggers include "split the X module into level 1/2/3", "break up the…

Use when opening, editing, retitling, or rewriting the body of any pull request in the crammr repo (path contains `crammr`) — `gh pr create`, `gh pr edit`, or drafting PR text for the user to paste. Covers the mandatory `CRMR:` title prefix, the fixed section…

Use when authoring, amending, squashing, fixup-ing, rebasing, or cherry-picking any git commit message in the pokemax repo — covers subject line, bullet body, backtick rules, and the ban on AI attribution.

Use when opening a pull request in the pokemax repo, writing or rewriting a PR title or body, or editing an existing PR's description — including when the user says "open a PR", "raise a PR", "push this for review", or asks to fix up a PR description.