feature-creator

Automate end-to-end feature creation for QoreDB with Rust, Tauri, and React.

137|8|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/QoreDB/QoreDB --skill feature-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-creator
Source: https://github.com/QoreDB/QoreDB/tree/main/.agent/skills/feature-creator
Command: npx skills add https://github.com/QoreDB/QoreDB --skill feature-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides a standardized, end-to-end workflow for adding a new feature to QoreDB, aligning the Rust/Tauri backend with the React frontend to ensure consistency and maintainability.

Core Features & Use Cases

  • End-to-end scaffolding: Guides the creation of a Rust command under src-tauri/src/commands, module registration, and a TypeScript SDK wrapper, plus optional React UI hooks.
  • Standardized architecture: Enforces a uniform structure across backend and frontend for new features, reducing integration gaps.
  • Use Case: When a product requirement calls for a new feature, use this workflow to generate a complete integration template and ensure consistent deployment steps.

Quick Start

Create a new feature by following the backend, frontend, and UI steps outlined to scaffold a full feature pipeline.

Frequently Asked Questions about feature-creator

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

FAQPage Schema
How do I scaffold a new feature across a Rust Tauri backend and React frontend?

To scaffold a new feature, you generate a Rust command template under src-tauri/src/commands, register the module, and create a TypeScript SDK wrapper. This workflow provides end-to-end feature creation templates to align Rust/Tauri backends with React frontends.

What is the standard workflow for wiring a Rust backend command to a TypeScript SDK?

The standard workflow for wiring a Rust backend command to a TypeScript SDK involves creating a Rust command template, wrapping it with a TypeScript SDK layer, and optionally integrating React UI hooks. This ensures uniform structure and reduces integration gaps across the stack.

Can I use this feature creation workflow to standardize state handling across Rust and React?

Yes, you can use this feature creation workflow to standardize state handling across Rust and React. It provides clear module registration and state handling guidance, enforcing a uniform architecture for new features across the Tauri and React environment.

Does the end-to-end feature workflow require setting up React UI integration templates?

Setting up React UI integration templates is optional within the end-to-end feature workflow. The required components are a Rust command template and a TypeScript SDK wrapper, while the React UI hooks are provided to complete the frontend pipeline if needed.

What's the best way to ensure consistent module registration when adding new commands in Tauri?

The best way to ensure consistent module registration when adding new commands in Tauri is to follow a standardized end-to-end feature workflow. This approach scaffolds Rust commands and enforces a uniform structure, preventing integration gaps during feature deployment.

When should I use an automated feature workflow instead of manually connecting Tauri and React?

You should use an automated feature workflow instead of manually connecting Tauri and React when a product requirement calls for a new feature. It generates a complete integration template, ensuring consistent deployment steps and reducing architectural misalignment across the stack.