Struct CreateProjectArgs 

pub struct CreateProjectArgs {
    pub project_name: String,
    pub vision: String,
    pub tech_stack: String,
    pub summary: String,
}

Arguments for create_project command

Fields

project_name: String

Project name in kebab-case (e.g., my-awesome-project)

Must contain only lowercase letters, numbers, and hyphens Cannot contain spaces, underscores, or special characters

vision: String

High-level product vision content (2-4 paragraphs, 200+ characters)

Content Structure:

• Problem statement and market need
• Target users and their pain points
• Unique value proposition and competitive advantages
• Key features and roadmap priorities

Markdown Formatting Guidelines:

• Use ## headers for main sections (## Problem, ## Target Users, ## Value Proposition)
• Structure with bullet points and clear paragraphs
• Include specific examples and use cases
• Write in present tense, professional tone
• End with clear success metrics or goals

Goes into vision.md

tech_stack: String

Technology stack and architecture decisions (150+ characters)

Content Structure:

• Core languages and frameworks with versions
• Databases, storage, and data architecture
• Deployment platforms and infrastructure
• Development tools and build systems
• Rationale for each major technology choice

Markdown Formatting Guidelines:

• Use ## headers for categories (## Backend, ## Frontend, ## Database, ## Deployment)
• List technologies with bullet points and brief rationale
• Include version constraints where relevant
• Add ### subsections for complex areas
• Include links to documentation where helpful

Goes into tech-stack.md

summary: String

Concise summary of vision and tech stack (100+ characters)

Content Guidelines:

• 2-3 sentences capturing project essence
• Combine key points from vision and tech stack
• Focus on what makes this project unique
• Written for quick LLM context loading

Format:

• Clear, professional language
• Present tense, active voice
• Include primary technology and main value proposition
• No markdown formatting needed (plain text)

Goes into summary.md

Trait Implementations

impl Args for CreateProjectArgs

fn group_id() -> Option<Id>

Report the ArgGroup::id for this set of arguments

fn augment_args<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate Self via FromArgMatches::from_arg_matches_mut

fn augment_args_for_update<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate self via FromArgMatches::update_from_arg_matches_mut

impl Debug for CreateProjectArgs

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl FromArgMatches for CreateProjectArgs

fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

fn update_from_arg_matches_mut( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

impl McpToolDefinition for CreateProjectArgs

fn tool_definition() -> Tool

Generate the MCP tool definition from the struct

fn from_mcp_params(params: &Value) -> Result<Self>

Convert MCP parameters to the CLI argument struct