skills.rest
Zeus-Deus
Zeus-DeusCOMMUNITY
Explore all skills by this author →
GitHub

codemux-features

Plan, implement, and verify Codemux ADE features across Rust backend and React frontend.

11|2|Updated Mar 6, 2026
Search Tags:#frontend#backend#rust#feature-implementation#ade#codemux
One-click install
npx skills add https://github.com/Zeus-Deus/codemux --skill codemux-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codemux-features
Source: https://github.com/Zeus-Deus/codemux/tree/main/.claude/skills/codemux-features
Command: npx skills add https://github.com/Zeus-Deus/codemux --skill codemux-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standardized blueprint for implementing Codemux ADE features with a consistent backend-first approach and UI integration, ensuring new capabilities align with project conventions.

Core Features & Use Cases

  • Defines a repeatable workflow for adding major Codemux features such as a Tasks System, MCP server, settings panel, notification sounds, and custom keybinds.
  • Clarifies cross-cutting concerns across Rust backend, Tauri commands, and React frontend, including testing, documentation, and UI alignment with codemux-ui.
  • Serves as a reference to maintain quality and coherence when extending Codemux with new capabilities, across multiple modules and teams.

Quick Start

Follow this guide to implement a new Codemux ADE feature from design through verification.

Frequently Asked Questions about codemux-features

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

FAQPage Schema
How do I implement a new feature in a Tauri app using Rust and React?▼

To implement a Tauri feature, design the backend state in Rust, expose Tauri commands, align the React frontend UI, integrate sockets or CLI, and update documentation for a coherent end-to-end workflow.

What is the standard process for adding a tasks system to a Rust backend?▼

Adding a tasks system requires designing Rust backend state, exposing Tauri commands, building the React frontend UI, integrating necessary sockets, and verifying the complete feature against project conventions.

How do I expose Rust backend state to a React frontend using Tauri commands?▼

You expose Rust backend state by defining Tauri commands that the React frontend can invoke, ensuring the frontend UI aligns with backend capabilities and project conventions throughout the integration.

Can I use this workflow to add a settings panel and custom keybinds to a Tauri application?▼

Yes, this workflow supports implementing major features like a settings panel and custom keybinds by standardizing the Rust backend state design, Tauri command exposure, and React frontend UI alignment.

What's the best way to ensure UI alignment when extending a React frontend with new capabilities?▼

The best way to ensure UI alignment is following a standardized workflow that bridges Rust backend state and Tauri commands with codemux-ui frontend conventions, maintaining quality across multiple modules.

Why does adding MCP server features require backend-first design in Rust?▼

Adding an MCP server requires backend-first design in Rust to establish a stable foundation before exposing Tauri commands and aligning the React frontend, ensuring the new capability integrates coherently.

Related Skills

Explore More Software Engineering Skills→
QoreDBQoreDB
137

feature-creator

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

Official
Advanced
skerishKangskerishKang

Page Doc Writer

Generate page documentation markdown from front-end files and QA results.

Community
Intermediate
dreamtidesdreamtides

tauri-v2

Create Tauri v2 desktop apps with React, TypeScript, and Rust.

Official
Advanced
miles990miles990
20

desktop-apps

Develop cross-platform desktop applications using Electron and Tauri frameworks.

Community
Intermediate