codebend3r/kasane

domain-tests

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.

release

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`.

version-bumper

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…

active-rebaser

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".

mapping-audit

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…

arc-mapping

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` +…

commit-messages

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`.

mapping-correction

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…

accessibility

Use when adding or editing any interactive element or data visualisation in kasane — Pressable, TextInput, Link, cover images, the episode/chapter rail or pie — or when asked about screen readers, VoiceOver, TalkBack, keyboard navigation, contrast, or a11y.

cross-platform-parity

Use when a kasane change touches networking, storage, navigation, fonts, safe areas, window chrome, or anything else that behaves differently on iOS, Android, web, or the Tauri desktop build — or when asked whether something works on native, on desktop, or in…

design-tokens

Use when writing or editing any StyleSheet in kasane — adding a component, restyling a screen, picking a colour, choosing spacing, or when asked to make the UI consistent, fix the palette, or clean up styles.

e2e

Use when adding or fixing browser-level tests for kasane, when a change touches routing, deep links, the Netlify SPA fallback or MangaDex proxy, or when asked to verify a user journey end to end rather than with unit tests.

quick-lookup-ux

Use when changing what kasane tells a user about where they are in a series — Quick lookup, the episode/chapter rail, arc detail, "arcs behind", auto-estimated mappings, progress marks, or any empty, partial, or "no answer" state on a series page.

supabase-migration

Use when changing kasane's Supabase schema — adding or altering a table, column, index, policy or grant, regenerating `src/types/supabase.ts`, or when asked about RLS, row-level security, or whether user data is exposed.

universal-component

Use when adding a component to kasane, when a route file grows past a few hundred lines, when the same UI is needed on both the anime and manga side, or when asked to extract, dedupe, refactor, or split a screen in this repo.