Cursor rule

1---
2description: "File organization and architectural patterns for the AI setup repository"
3globs: ["src/**/*", "app/**/*", "public/**/*", "docs/**/*"]
4alwaysApply: false
5---
6 
7# Project Structure & Architecture
8 
9Guidelines for organizing files and structuring the AI setup repository.
10 
11## Expected Project Structure
12 
13```
14.
15├── README.md                 # Project documentation
16├── LICENSE                   # MIT license
17├── .gitignore               # Node.js/Next.js patterns
18├── .cursor/rules/           # Cursor project rules
19├── .env.example             # Environment variable template
20├── package.json             # Dependencies and scripts
21├── next.config.js           # Next.js configuration
22├── tsconfig.json            # TypeScript configuration
23├── src/
24│   ├── app/                 # Next.js app directory
25│   ├── components/          # React components
26│   ├── lib/                 # Utility functions and AI clients
27│   ├── types/               # TypeScript type definitions
28│   └── utils/               # Helper functions
29├── public/                  # Static assets
30└── docs/                    # Additional documentation
31```
32 
33## Key Directory Guidelines
34 
35### Source Code Organization
36- `src/lib/` - Place AI client configurations and utilities here
37- `src/components/` - Reusable UI components, including AI-powered components
38- `src/app/api/` - API routes for AI services and integrations
39- `src/types/` - TypeScript definitions for AI responses and data models
40 
41### Component Organization
42- Group related components in feature-specific subdirectories
43- Keep component styles and tests near the component
44- Use index files for clean imports
45 
46### Utility Organization
47- Group related utilities in feature-specific directories
48- Separate AI-specific utilities from general utilities
49- Implement consistent naming patterns
50 
51## Architectural Principles
52 
53### 1. Node.js/Next.js Development
54- Follow Next.js 13+ App Router patterns when applicable
55- Use modern ES6+ JavaScript/TypeScript features
56- Implement proper async/await patterns for AI API calls
57- Use React Server Components where appropriate
58- Optimize for both development and production environments
59 
60### 2. File Naming Conventions
61- Use camelCase for JavaScript/TypeScript files
62- Use PascalCase for React component files
63- Use kebab-case for API routes and static files
64- Use descriptive names that indicate purpose
65 
66### 3. Import Organization
67- Group imports by type (external, internal, relative)
68- Use absolute imports with path aliases when configured
69- Keep imports organized and clean
70 
71### 4. Configuration Management
72- Keep all configuration files in the project root
73- Use TypeScript for configuration files when possible
74- Document configuration options and their purposes