aif-plan

Name: aif-plan
Availability: InStock
Author: vanyastaff

Automate adding Rust crates with workspace and library configuration.

2|Updated May 26, 2025

Search Tags:#project management #development workflow #workspace #rust #cargo #crates

Ready to run

npx skills add https://github.com/vanyastaff/nebula --skill aif-plan-vanyastaff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-plan
Source: https://github.com/vanyastaff/nebula/tree/main/.ai-factory/skill-context/aif-plan
Command: npx skills add https://github.com/vanyastaff/nebula --skill aif-plan-vanyastaff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of adding new crates to the Nebula project, ensuring consistency and adherence to established development practices.

Core Features & Use Cases

New Crate Generation: Automates the creation of new Rust crates with proper naming conventions and workspace integration.
Configuration Enforcement: Ensures new crates adhere to workspace Cargo.toml rules and includes essential lib.rs configurations.
Dependency Management Guidance: Promotes the use of event-driven communication over direct downward dependencies.
Use Case: When a developer needs to add a new feature that requires a dedicated crate, this Skill guides them through the correct setup process, preventing common errors and maintaining project integrity.

Quick Start

Follow the new crate workflow to add a 'nebula-auth' crate to the project.

Frequently Asked Questions about aif-plan

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

FAQPage Schema

How do I add a new crate to a Rust workspace project?▼

To add a new crate to a Rust workspace, you must configure the root Cargo.toml, apply correct naming conventions, and set up the initial lib.rs file. This ensures the new crate integrates properly with the existing project architecture.

Why do my Rust workspace crates fail to compile after adding a new module?▼

Rust workspace compilation often fails when new crates do not adhere to established Cargo.toml rules or lack essential lib.rs configurations. Enforcing specific workspace configuration patterns prevents these common setup errors.

What is the best way to manage dependencies between crates in a Rust workspace?▼

The recommended approach for crate dependency management is using event-driven communication instead of direct downward dependencies. This maintains project architecture integrity and prevents tight coupling between modules.

Does adding a new crate to a workspace require specific Cargo.toml patterns?▼

Yes, adding a new crate requires adherence to specific Cargo.toml patterns to enforce workspace rules. Proper configuration ensures the crate follows project naming conventions and integrates with the broader workspace setup.

Can I automate Rust crate creation and library setup for my development workflow?▼

Automating Rust crate creation enforces proper naming conventions, workspace configuration, and library setup during generation. This guides developers through the correct workflow, preventing manual errors when adding features that require dedicated crates.