slaktforskning

Audit place resolution against a real database to find outliers — places that resolve to the wrong country, state, or sub-region. Use when investigating bad map pins, validating new gazetteers, or debugging "why did Richmond, Kalifornien USA land in Canada?". Pairs with the `gazetteers` skill (build/extend) — this skill is for *testing* placement on real data.

Use whenever dispatching subagents in this project — implementer, spec-reviewer, or code-quality-reviewer. Wraps the upstream `superpowers:subagent-driven-development` skill with project-local prompt templates that center user goals (not just spec compliance) and require the dispatcher to verify user-observable outcomes before marking work done.

Decide which Playwright tier to run, capture the right evidence for plan close-out, and route work into the right project. Use when finishing a plan (gate before archive), when adding an e2e test (which project gets the spec), when CI fails on `[boot]` / `[crud]` / `[panels]` / `[reactivity]` / `[imports]` and you need to know which user-goal it protects, or when the question is "is `npm run test:e2e` enough or do I need `:full`?".

Extend the Släktforskning MCP server — add new tools to createProdServer.ts / createDevServer.ts, wire window.api bindings in tauri-window-api.ts + static-api stubs, test via tests/unit/mcp.test.ts, debug agent-facing IPC. Also covers the dev MCP HTTP bridge (src-tauri/src/ui_server.rs) used by ui_screenshot / ui_click / ui_eval / chart_*. Use when modifying anything in src/mcp/, src/renderer/tauri-window-api.ts, or src-tauri/src/ui_server.rs. Distinct from `slaktforskning-mcp` (which is for an agent *using* the MCP tools to do genealogy work for the user).

Build, extend, and debug gazetteers for place resolution. Use when adding new country gazetteers, modifying build scripts, debugging place matching, or questions about the gazetteer system (types, resolver, normalization, data sources).

Use when actually doing genealogy research with the Släktforskning MCP — building real family trees end-to-end, exporting/round-tripping, attaching media + face tags, importing custom gazetteers for places not in the bundled set. Pairs with `slaktforskning-mcp` (which lists the tools). Distinct from `slaktforskning-mcp-dev` (extending the MCP server itself). Triggers on real research workflows, "research X family", "test the app end-to-end", "set up a Bernadotte-style demo".

Add a new native importer for a genealogy file format (alongside the GEDCOM, Genney, Holger, RootsMagic, and Gramps importers we already ship). Use when the user asks to support a new app's file format — e.g. "add a Family Tree Maker importer", "let users import .ftm files directly", or "we should read .gpkg natively". Covers the multi-file pattern: src/import/<format>/, window.api bindings in tauri-window-api.ts, file picker, renderer-side fs read via invoke('fs_read_bytes_base64'), static-api stub, UI tab, MCP auto-detect, fixture-based tests.

Launch, debug, and verify the Tauri app during development. Use when testing UI changes, debugging the renderer or Rust host, verifying a build, or asking how to inspect the running app. Covers `npm start`, the bundle build, the dev MCP UI bridge port, and where logs land.

Wire undo/redo support for new mutations. Use when adding any function in src/api/ that writes to the database, when composing multi-step operations that must undo atomically, when binding a new window.api mutation, or when investigating "why didn't my action show up in the undo stack". Covers UndoAction shape, the snapshot-old-state-then-mutate sequence, beginGroup/endGroup for atomic multi-step ops, the mutating() data-changed fan-out via fireDataChanged(), and the relationship between undo and onDataChanged.

Walks the CLAUDE.md "Finishing a plan" 6-step checklist as one command, refusing partial work. Use when a plan's last task is `[x]`, when archiving any plan, or when "we shipped feature X" — the canonical replacement for human-walked archive flows. Catches the dominant failure mode: stale plans left in docs/plans/ because the 6 steps weren't run in order.

Triage a UX report (beta tester feedback, GitHub issue, user request) against the product principles (CLAUDE.md), reproduce against the running app via dev MCP, and produce one of three outcomes — "ship in next polish batch", "needs design", or "close with reasoned reply". Use whenever the user pastes feedback like Ben's reports, when a GitHub issue arrives, or when an idea is proposed and the question is "is this worth doing?"

Periodic re-read of recent shipped work against the product principles (CLAUDE.md), .claude/rules/plans.md, and .claude/rules/mandate.md. Catches plan-format drift, intent drift, workflow drift, and rules that didn't fire when they should have. Use every 2 weeks, after archiving 3+ plans, or when the user calls "let's retro." Outputs: a list of rule deltas to commit, or "clean — no drift found."

Stage the files belonging to the current concern and create a git commit. Always use this instead of manual git add/commit.

Owns CHANGELOG.md — block structure, bullet style, the 10-block rolling window, and the archive flow. Releases auto-publish per commit via CI; this skill is the changelog discipline around that. Use whenever editing CHANGELOG.md, bumping the version, or asked to "cut a release", "ship a release", "publish a release".

Session-start ritual. Walks the project state to produce a single-screen view of what's hanging, what's stale, and what's the proposed next move. Replaces "I start cold from CLAUDE.md + git log." Use at the top of any working session, when context is lost, or when asked "what's the state of the project?"

How the renderer talks to Rust in the Tauri build — the Specta-generated `bindings.ts` for Rust commands, the inlined renderer-local bindings in `tauri-window-api.ts`, when to add a Rust command vs a pure-TS binding, the generic Rust commands already shipped (`dialog_pick`, `fs_*`, `shell_*`, `media_*`, `db_*`), the `invoke()` shape and error convention. Use when editing `src/renderer/tauri-window-api.ts`, editing `src-tauri/src/lib.rs`, adding a binding that needs fs/dialog/shell/multi-window, or whenever the question is "should this be a Rust command or pure TS?".

Hard-won patterns for implementing drag interactions (move / resize / pan) in Vue components — especially inside CSS-transformed containers like the image-tagger overlay, the chart pan/zoom canvas, the resize-handle column splitter, and the panel resizer. Use whenever wiring `mousedown` / `mousemove` / `mouseup` (or pointer-equivalents) for anything the user has to drag. Covers window-level listeners, separating listener cleanup from state, pointer-events kill during drag, screen-pixel math, percentage positioning for overlays, async-reload races, and image-dimension guards.

Add a new feature, entity type, or field to the Släktforskning codebase. Use this skill whenever implementing any new data model change, CRUD operation, IPC binding, MCP tool, or Vue UI component — even if the user just says "add X" or "implement Y". Covers the full stack: schema, API, window.api wiring (Specta-generated for Rust commands + inlined renderer-local bindings), MCP, Vue.

When an audit, third-party finding, AI-generated codebase claim, or any "X is wrong / Y is missing / Z is 1000 LOC" statement is the input to a plan, validate the claim by grepping the actual code BEFORE writing the plan. Triggers on phrases like "the audit says", "the analysis found", "X is N LOC", "Y doesn't exist yet", "Z is duplicated across", or any claim about file/symbol existence, file size, or pattern presence that would change the shape of the plan.

Use when investigating any layout, visual, or "this looks different from that" issue in the renderer. The first action is reading the rendered DOM or computed styles — not reasoning about CSS. Reasoning only after the truth is on the table. Triggers on "panel doesn't fill", "X looks different from Y", "spacing is wrong", "border-radius missing", "wrong width", "rendered position is off".

Use BEFORE writing or editing any bounded UI surface in the renderer — a panel section in `src/renderer/components/*Panel.vue`, a modal in `src/renderer/components/modals/*`, or a nested sub-modal. Forces a one-sentence Purpose statement in the user's words and a CTA inventory across View/Add/Edit/Delete/Open. Catches the app's known UX inconsistencies (✕ means unlink in one section and delete in another; `+ Add person` on Place panel hides the actual primitive). Triggers on requests like "add a section to X panel", "redesign Y", "make Z consistent", and on plans in `docs/plans/` that open with mechanism instead of user intent. Lean specialization — defers to `superpowers:brainstorming` for net-new intent and to project `frontend-design` for the implementation HOW.

Design data schemas for genealogy apps — persons, families, events, sources, citations, media. Use for schema design, ERDs, modeling complex family structures, or any question about how the data model works in this project. Also triggers on questions about tables, foreign keys, relationships, or the GEDCOM-X vs GEDCOM alignment.

Use when diagnosing slow operations, CPU saturation, or hangs in the Tauri app. Covers CPU profiling setup for the renderer (Chromium DevTools / Safari Web Inspector against the system webview), the Rust host binary (cargo flamegraph / samply), cpuprofile + Firefox-Profiler analysis, and the known SQLite bottleneck patterns in this codebase.

Run tests, write new tests, and verify code changes. Use when implementing features, fixing bugs, or before committing.

ARIA accessibility patterns for the Släktforskning codebase — modals, combobox pickers, keyboard navigation, focus management, TTS, WCAG contrast enforcement. Use when adding or modifying any interactive UI component, and when changing any color token.

DELETE journaling is the canonical SQLite mode for this project. Use when reviewing any `PRAGMA journal_mode` code, when adding a sibling tool (rusqlite CLI, sqlite3 CLI, native better-sqlite3) that might share an .db file, or when investigating "SQLite3Error: unable to open database file" with no obvious cause.

PDF/SVG export, print button, print CSS, chart orientation, fit-to-page layout, and ReportsView rendering. Use whenever touching the print path, the Save SVG / Save PDF buttons, the @media print block in ReportsView, chart orientation mapping, or any keepsake/chart report component.

rusqlite-side DB patterns for the Tauri build — global Mutex<Option<Connection>>, the 5 SQL primitives in src-tauri/src/db.rs (db_run, db_get, db_all, db_batch, db_run_changes), parameter binding (positional via &[Value], named via named_params!), transaction wrappers, the prepare_cached statement cache, when to add an api/-layer function vs a Rust command, DELETE vs WAL journaling. Use when editing src-tauri/src/db.rs, adding any new Rust SQL helper, or asking "should this go in api/ or in Rust?".

Parse, validate, import/export GEDCOM files (5.5.1 and 7.0). Use for .ged files, genealogy data interchange, or GEDCOM compliance.

Use when the user asks you to do real genealogy research in the Släktforskning app via the MCP server — adding persons, building family trees, finding duplicates, citing sources, recording events with places, generating narratives. Distinct from `slaktforskning-mcp-dev` (which is about extending the MCP server itself). Triggers on any agent-driven research task involving the slaktforskning or slaktforskning-dev MCP tools.

Declare round-trip GEDCOM fidelity for new schema columns. Use when modifying src/api/schema.ts (adding/removing/renaming columns), changing src/gedcom/exporter.ts or src/import/gedcom/, or when CI fails with "GEDCOM fidelity registry missing N entries". Covers the four registry status kinds (lossless, lossless-via, lossy, excluded), how to write each, and what the per-field round-trip tests assert.

Frontend design patterns for Släktforskning — Vue 3 components, layout, colors, modals, i18n, error handling. Use when building any new view, component, or UI change in the renderer.

Layout algorithm patterns for tree charts (pedigree, hourglass, descendant). Use when building or modifying any chart layout that positions boxes in a tree structure.

Close stale GitHub issues and PRs that have had no activity for 60+ days. Comment before closing to explain why. Use whenever the user says "clean up stale issues", "close old issues", "handle stale PRs", "prune inactive issues", or asks to close issues with no recent activity.

Triage open GitHub issues — auto-label by type, find and close duplicates with a comment linking the original. Use whenever the user says "triage issues", "go through open issues", "handle new issues", or asks you to label/close/organize GitHub issues.

Welcome first-time contributors who open a PR or issue. Detects whether the author has contributed before and posts a friendly greeting if not. Use whenever the user says "welcome new contributors", "greet first-timers", "check for new contributors", or when reviewing a new PR or issue and wanting to acknowledge first-time contributors.

Synthesize user interviews, survey responses, or forum threads from genealogists into structured product insights and design prompts.

Research genealogy apps (Ancestry, FamilySearch, MyHeritage, etc.) to identify features, UX patterns, pricing, and competitive gaps.