Menu
Research genealogy apps (Ancestry, FamilySearch, MyHeritage, etc.) to identify features, UX patterns, pricing, and competitive gaps.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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".
| name | web-research |
| description | Research genealogy apps (Ancestry, FamilySearch, MyHeritage, etc.) to identify features, UX patterns, pricing, and competitive gaps. |
This skill helps you research existing genealogy applications to inform product ideation — understanding what's out there, what works, what's missing, and where opportunities lie.
When researching the competitive landscape, prioritize these platforms:
Structure your findings as:
Brief overview of the market (2-3 sentences).
For each platform: name, pricing, target user, 3-5 key features, 1-2 notable weaknesses.
A markdown table: platforms as columns, feature categories as rows, with ✓/✗/partial markers.
Bulleted list of underserved needs or missing features that a new app could address.
Top 3-5 strategic opportunities based on the research.
Släktforskning differentiates on being local-first (no cloud, no subscription), agent-friendly (built-in MCP server for AI assistance), and research-grade (Source → Citation model). When researching competitors, pay special attention to:
See docs/PLAN.md for the current roadmap — focus research on features relevant to upcoming work.
