agentic-jumpstart-architecture

Document architectural guidelines for the Jarvy CLI, covering Rust structure and tool patterns.

Updated Jul 13, 2024
One-click install
npx skills add https://github.com/bearbinary/Jarvy --skill agentic-jumpstart-architecture-bearbinary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-jumpstart-architecture
Source: https://github.com/bearbinary/Jarvy/tree/main/.claude/skills/agentic-jumpstart-architecture
Command: npx skills add https://github.com/bearbinary/Jarvy --skill agentic-jumpstart-architecture-bearbinary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive architectural blueprint for the Jarvy CLI, ensuring consistency, maintainability, and scalability in its development.

Core Features & Use Cases

  • Codebase Structure: Defines the organization of the Rust project, including modules and their responsibilities.
  • Tool Implementation Patterns: Outlines a standardized approach for adding new tool support, including platform-specific logic and error handling.
  • Registry System: Explains the mechanism for registering and dispatching tool installation handlers.
  • Use Case: A new developer joining the Jarvy project can immediately understand how to contribute a new tool or modify existing functionality by consulting these guidelines.

Quick Start

Review the src/tools/ directory structure and the add_handler function signature for implementing new tools.

Frequently Asked Questions about agentic-jumpstart-architecture

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

FAQPage Schema
How do I structure a Rust CLI project for maintainability and scalability?

Structure a Rust CLI project by defining clear module responsibilities, using a registry system for dispatching handlers, and isolating platform-specific code to ensure maintainability and scalability.

How do I add a new tool to a Rust CLI using a registry system?

Add a new tool by reviewing the src/tools/ directory structure and implementing the add_handler function signature to register and dispatch tool installation handlers within the registry system.

What is the best way to handle errors in a Rust CLI application?

Handle errors in a Rust CLI application using the thiserror crate to define custom error types, ensuring consistent error propagation and clear diagnostic messaging across modules.

How does platform detection work in Rust CLI tool implementation?

Platform detection in Rust CLI tool implementation works by isolating platform-specific code into dedicated modules, allowing the tool to execute conditional logic based on the detected operating system.

How do I implement telemetry in a Rust CLI using OpenTelemetry and PostHog?

Implement telemetry in a Rust CLI by integrating PostHog for product analytics and OpenTelemetry for distributed tracing, establishing a telemetry architecture to monitor application performance and usage.

Can I use thiserror for error handling in a Rust CLI with platform-specific code?

Yes, thiserror supports error handling in a Rust CLI with platform-specific code by allowing you to define custom error enums that encapsulate diverse platform-level failures and standardize error propagation.