rustfeed-architecture

Document Rustfeed workspace crate layout and inter-crate dependencies.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/ereferen/rustfeed --skill rustfeed-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rustfeed-architecture
Source: https://github.com/ereferen/rustfeed/tree/main/.claude/skills/rustfeed-architecture
Command: npx skills add https://github.com/ereferen/rustfeed --skill rustfeed-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents the Rustfeed workspace, crate layout, and inter-crate dependencies to help contributors understand project structure.

Core Features & Use Cases

  • Clarifies the Cargo workspace with top-level crates and their roles (rustfeed-core, rustfeed-cli, rustfeed-tui).
  • Maps inter-crate dependencies and module boundaries to guide future changes.
  • Provides onboarding guidance for new contributors when adding features or reorganizing architecture.

Quick Start

Review the architecture guide to understand how crates are organized and where to place new architectural changes.

Frequently Asked Questions about rustfeed-architecture

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

FAQPage Schema
How do I organize a Rust Cargo workspace with multiple crates?

A Rust Cargo workspace organizes multiple crates like rustfeed-core, rustfeed-cli, and rustfeed-tui under a single root, mapping inter-crate dependencies and module boundaries to guide structural changes and feature additions.

Where should I place new modules in a Rust workspace project?

New modules in a Rust workspace should be placed within designated source paths like rustfeed-core/src, rustfeed-cli/src/commands, and rustfeed-tui/src to maintain consistent architecture and module boundaries across crates.

What's the best way to onboard contributors to a Rust project structure?

Onboarding contributors to a Rust project involves documenting the workspace crate layout, mapping inter-crate dependencies, and providing an architecture guide that explains where to place structural changes when adding features.

How do I introduce cross-crate features in a Rust workspace?

Introducing cross-crate features in a Rust workspace requires understanding inter-crate dependencies and module boundaries, then enforcing placement of architecture artifacts within the appropriate crate source directories like rustfeed-core/src.

When do I need to update the architecture guide for a Rust project?

You need to update the architecture guide when making structural changes to a Rust workspace, such as adding new crates, reorganizing modules, or introducing cross-crate features that affect the documented inter-crate dependencies.