get_architecture_recommendation
Get architectural guidance before implementing major features, with recommended design patterns, file structure, technology choices, and implementation steps.
Instructions
RECOMMENDED: Get expert architectural guidance before implementing major features.
This tool provides flexible project lookup. You can specify any combination of identifiers, and it will resolve to the matching project.
Priority: project_id > workspace_path > project_name
WHEN TO USE:
Before implementing significant new features or capabilities
When you're unsure about the best architectural approach
For complex features that affect multiple parts of the system
When choosing between different implementation strategies
To ensure consistency with existing architecture
Before making structural changes to the codebase
HIGHLY RECOMMENDED FOR:
New major features
Significant refactoring efforts
Integration with external systems
Changes to core architecture
Performance-critical implementations
THIS PROVIDES:
Recommended approach and design patterns
File structure and organization suggestions
Technology and library recommendations
Implementation steps and considerations
Rationale for the recommendations
AFTER RECEIVING RECOMMENDATIONS:
Review the suggested approach
Save the decision with save_decision() if you adopt the recommendation
Implement following the suggested structure
Update architecture tracking with update_architecture()
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Additional context - requirements, constraints, preferences (optional) | |
| project_id | No | Project ID from create_project() (optional if project_name or workspace_path provided) | |
| constraints | No | List of constraints - e.g., ["must use PostgreSQL", "must be stateless"] (optional) | |
| project_name | No | Project name to look up (alternative to project_id) | |
| workspace_path | No | Workspace directory path (alternative to project_id) | |
| feature_description | Yes | Clear description of what you're building (required) - e.g., "User authentication system with JWT tokens" | |
| implementation_style | No | Preferred approach - "modular", "monolithic", or "auto" (default: "modular") | modular |