import-format-add

What problem does it solve?

It helps you extend Släktforskning by adding a native importer when users have genealogy data from another desktop app, so their files can be imported directly instead of requiring an intermediate GEDCOM export.

Core Features & Use Cases

• Native importer blueprint for new formats: Defines the end-to-end wiring (picker, bytes-based loading, transform pipeline, UI tab, and MCP discovery) so the new format behaves like existing GEDCOM/Genney/RootsMagic/Gramps/Holger imports.
• Format-shape driven implementation guidance: Recommends diffing against the closest existing importer shape (SQLite-like vs XML-like vs wrapped bundles) to minimize guesswork and match Släktforskning’s import conventions.
• Correct Tauri + renderer integration: Covers using invoke('fs_read_bytes_base64') for renderer-side file loading, implementing both file-path and bytes-based importer variants, and ensuring fireDataChanged() refreshes the UI.
• Schema discovery and transform correctness: Provides concrete steps to inspect real samples (e.g., SQLite .schema, XML scanning) and mandates multi-phase entity creation, event/person/place linkage, citations, media, and transaction handling.
• Safety against data loss: Includes guardrails to avoid silent drops by reporting skipped/unrepresentable data in summaries or notes.

Quick Start

Add a native importer for your genealogy format by creating the expected src/import/<format>/ structure, wiring the SKILL.md-driven picker and bytes-based run flow, and implementing a transform that imports persons, relationships, events, citations, and media while updating progress and summaries.