seliaste/nvim-config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: update project progress and context documentation for clarity and structure

Browse source 
Signed-off-by: juliano.barbosa <julianomb@gmail.com>
This commit is contained in:
juliano.barbosa 2025-02-03 18:45:48 -03:00
parent 0a9b04a7c8
commit b8fb6c42f6
4 changed files with 170 additions and 162 deletions
Download patch file Download diff file Expand all files Collapse all files

114
cline_docs/systemPatterns.md
View file

@ -3,10 +3,10 @@
## Architecture Patterns
### 1. Plugin System
- Uses lazy.nvim for plugin management
- Plugins are defined in init.lua
- Supports lazy loading via events/commands
- Custom plugins can be added in lua/custom/plugins/
- Uses `lazy.nvim` for plugin management.
- Plugins are defined in `init.lua`.
- Supports lazy loading via events/commands.
- Custom plugins can be added in `lua/custom/plugins/`.
### 2. Configuration Structure
```
@ -23,80 +23,80 @@
### 3. Key Design Patterns
#### Modular Configuration
- Core settings in init.lua
- Plugin-specific configurations in separate files
- Custom configurations isolated in lua/custom/
- Core settings in `init.lua`.
- Plugin-specific configurations in separate files.
- Custom configurations isolated in `lua/custom/`.
#### Event-Driven Architecture
- Uses Neovim's event system for plugin loading
- Autocommands for specific behaviors
- LSP events for IDE features
- Uses Neovim's event system for plugin loading.
- Autocommands for specific behaviors.
- LSP events for IDE features.
#### Layer-Based Organization
1. Core Settings Layer
- Basic Vim options
- Key mappings
- Global variables
1. **Core Settings Layer**
- Basic Vim options.
- Key mappings.
- Global variables.
2. Plugin Layer
- Plugin management
- Plugin configurations
- Plugin-specific settings
2. **Plugin Layer**
- Plugin management.
- Plugin configurations.
- Plugin-specific settings.
3. LSP Layer
- Language server configurations
- Completion setup
- Diagnostic settings
3. **LSP Layer**
- Language server configurations.
- Completion setup.
- Diagnostic settings.
4. UI Layer
- Colorscheme
- Statusline
- Visual enhancements
4. **UI Layer**
- Colorscheme.
- Statusline.
- Visual enhancements.
## Technical Decisions
### 1. Configuration Language
- Lua chosen over VimScript for:
- Better performance
- Modern syntax
- Rich data structures
- Better integration with Neovim
- Better performance.
- Modern syntax.
- Rich data structures.
- Better integration with Neovim.
### 2. Plugin Selection
- Minimal but powerful set of defaults
- Focus on maintained, actively developed plugins
- Preference for Lua-based plugins
- Built-in LSP over CoC or similar alternatives
- Minimal but powerful set of defaults.
- Focus on maintained, actively developed plugins.
- Preference for Lua-based plugins.
- Built-in LSP over CoC or similar alternatives.
### 3. Code Organization
- Single init.lua for easy understanding
- Modular structure available through kickstart-modular.nvim
- Clear separation between core and user customizations
- Single `init.lua` for easy understanding.
- Modular structure available through `kickstart-modular.nvim`.
- Clear separation between core and user customizations.
### 4. Performance Considerations
- Lazy loading of plugins
- Efficient event handling
- Minimal startup impact
- Careful LSP configuration
- Lazy loading of plugins.
- Efficient event handling.
- Minimal startup impact.
- Careful LSP configuration.
## Key Technical Standards
1. Code Style
- Consistent Lua formatting
- Clear commenting
- Documented configuration options
1. **Code Style**
- Consistent Lua formatting.
- Clear commenting.
- Documented configuration options.
2. Plugin Management
- Versioned dependencies
- Conditional loading
- Clear plugin specifications
2. **Plugin Management**
- Versioned dependencies.
- Conditional loading.
- Clear plugin specifications.
3. Error Handling
- Protected calls for plugin loading
- Fallbacks for missing dependencies
- Clear error messages
3. **Error Handling**
- Protected calls for plugin loading.
- Fallbacks for missing dependencies.
- Clear error messages.
4. Documentation
- Inline documentation
- Help files
- Clear user instructions
4. **Documentation**
- Inline documentation.
- Help files.
- Clear user instructions.