add-feature

Add new entity types and CRUD operations across schema, API, IPC, MCP, and Vue UI.

2|Updated Apr 2, 2026

Search Tags:#database migrations #MCP tools #add feature #IPC bindings #Vue components #SQLite schema #Tauri Specta

Ready to run

npx skills add https://github.com/jonaseck2/slaktforskning --skill add-feature-jonaseck2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-feature
Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/add-feature
Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill add-feature-jonaseck2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add a new feature to the Släktforskning codebase without accidentally breaking reachability, layering, safety rules, or MCP/UI integration paths.

Core Features & Use Cases

Full-stack change checklist: guides updates across TypeScript types, SQLite schema/migrations, API CRUD, IPC bindings, MCP tools, Vue UI, tests, and docs.
Strict data fidelity guardrails: prevents persisting inferred/guessed values and enforces the Prime Directive for DB mutations.
Correct integration wiring: ensures renderer bindings (pure TS or Rust-backed Specta commands) and MCP tool registration are added in the right places.
Verification-focused workflow: includes required unit and UI verification steps so changes actually work for users and agents.

Quick Start

Use this skill whenever you need to implement a new data model change, CRUD operation, IPC binding, MCP tool, or Vue UI component end-to-end for Släktforskning.

Frequently Asked Questions about add-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add a new feature across SQLite schema, API, and Vue UI without breaking layering rules?▼

To add a feature safely, follow a strict checklist order across TypeScript types, SQLite migrations, API CRUD, IPC bindings, MCP tools, and Vue UI. This enforces DB migration guards and prevents persisting inferred values across all layers.

How do I wire Tauri Specta commands and window.api IPC bindings for a new CRUD operation?▼

Wiring IPC bindings requires adding renderer-side window.api and Rust-backed Specta commands in the correct integration points. The workflow ensures both pure TS and Rust-backed paths are connected along with MCP tool wrappers for consistent agent access.

What's the best way to register MCP tools for a new entity type in a full-stack TypeScript and Rust codebase?▼

Registering MCP tools involves wrapping new CRUD operations and adding them to the MCP tooling layer alongside Vue UI and IPC updates. This guarantees AI-accessible tools maintain consistent behavior with the underlying SQLite schema and API.

How do database migration guards work when adding new fields to an existing SQLite schema?▼

Database migration guards enforce the Prime Directive for DB mutations, preventing the persistence of inferred or guessed values. They act as strict data fidelity guardrails during schema changes to ensure only verified data is stored.

Do I need to update both renderer components and MCP tooling when implementing a new data model change?▼

Yes, implementing a data model change requires updating renderer components and MCP tooling simultaneously. The full-stack checklist mandates synchronized updates across TypeScript types, API CRUD, IPC bindings, Vue UI, and tests to ensure functionality works for users and agents.

Why does my new Vue component fail to reach the backend API after adding IPC bindings?▼

Vue components fail to reach the backend when IPC bindings are not wired in the right places, such as missing Rust-backed Specta commands or unregistered window.api methods. Following the verification workflow catches these integration gaps through required unit and UI testing.