skills.rest
planetaryescape
planetaryescapeOFFICIAL
Explore all skills by this author →
GitHub

mxr-development

Manage the mxr mailbox development lifecycle, daemon debugging, and release pipeline.

70|7|Updated Mar 20, 2026
Search Tags:#development#cli#sqlite#rust#daemon#mailbox
One-click install
npx skills add https://github.com/planetaryescape/mxr --skill mxr-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mxr-development
Source: https://github.com/planetaryescape/mxr/tree/main/.agents/skills/mxr-development
Command: npx skills add https://github.com/planetaryescape/mxr --skill mxr-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured environment for managing the development lifecycle of the mxr mailbox project, preventing context bloat and ensuring architectural consistency across its daemon-backed, local-first codebase.

Core Features & Use Cases

  • Architectural Guidance: Enforces strict crate boundaries and domain invariants to maintain system integrity.
  • Development Workflow: Standardizes the build, test, and verification loop for features and daemon management.
  • Release Automation: Provides a clear, step-by-step protocol for shipping new versions across Homebrew, shell scripts, and Cargo.

Quick Start

Use the mxr-development skill to guide you through the process of implementing a new provider adapter while adhering to the project's crate dependency rules.

Frequently Asked Questions about mxr-development

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

FAQPage Schema
How do I manage Rust daemon development and maintain architectural consistency?▼

Rust daemon development requires enforcing strict crate boundaries and domain invariants. This Skill standardizes the workflow for source modifications, daemon debugging, and architectural guidance to maintain system integrity across a local-first codebase.

What is the best way to enforce crate dependency rules when implementing new provider adapters?▼

Enforcing crate dependency rules involves adhering to strict architectural boundaries during implementation. This Skill guides you through adding provider adapters while verifying that crate dependencies and domain invariants remain intact throughout the process.

How do I automate cross-platform release pipelines for Rust CLI tools via Homebrew and Cargo?▼

Automating cross-platform release pipelines requires a standardized protocol for shipping versions. This Skill provides step-by-step release automation across Homebrew, shell scripts, and Cargo to verify and deploy new builds.

Does local-first mailbox storage work with IPC-based daemon communication during debugging?▼

Local-first mailbox storage integrates directly with IPC-based daemon communication. This Skill facilitates daemon debugging and feature verification while ensuring adherence to local-first storage principles and IPC protocols.

Why does strict crate boundary enforcement matter for mailbox daemon architecture?▼

Strict crate boundary enforcement prevents context bloat and maintains architectural consistency in mailbox daemon projects. This Skill ensures source modifications respect these boundaries, preserving system integrity and domain invariants.

Related Skills

Explore More Software Engineering Skills→
wcyganwcygan
1

rust-crate-creator

Create a new Rust crate with workspace dependency pinning and standard documentation.

Community
Intermediate
gabergergaberger
4

hex-dev-rebuild

Rebuild and deploy the hex-nexus binary in release mode.

Community
Advanced
giosuetedeschi-specgiosuetedeschi-spec

personal-tool-builder

Architect custom CLI utilities for local-first personal productivity workflows.

Community
Intermediate
borgbaseborgbase
682

architecture-review

Analyze Rust CLI architecture for workspace layout, crate boundaries, and error handling.

Official
Advanced