@/path/to/folder/ syntax. When you mention a folder, Elastic sees the complete directory structure and all file contents, perfect for understanding complex interactions between multiple files.
How Folder Mentions Work
When you type@ in the chat input and navigate to folders, Elastic shows you:
- Directory structure: Complete folder hierarchy
- File listings: All files within the folder
- Nested folders: Subdirectories and their contents
Syntax
@/src/components/@/utils/@/api/auth/@/tests/
What Elastic Sees
When you mention a folder, Elastic receives:- Complete directory structure - All files and subfolders
- All file contents - Every file within the folder
- Relationships - How files interact and depend on each other
- Architecture patterns - Organizational structure and conventions
Best Practices
When to Use Folder Mentions
- Architecture review:
@/src/components/ How is this component library organized? - Feature analysis:
@/api/auth/ Explain the authentication system - Testing:
@/tests/ Run through the test coverage - Documentation:
@/docs/ Update the documentation structure
Combining with File Mentions
Mix folder and file mentions for comprehensive context:Multiple Folder Mentions
Reference multiple directories to show relationships:Folder Types and Use Cases
Source Code Directories
Configuration Directories
Documentation Directories
Test Directories
Tips for Effective Folder Mentions
- Use trailing slash: Always end with
/to indicate a folder - Be strategic: Large folders might overwhelm the context
- Combine wisely: Mix with specific file mentions for focus
- Consider scope: Start with smaller folders for targeted questions
- Think hierarchically: Use parent/child folder relationships
Integration with Memory Bank
Folder mentions help Elastic understand:- Project architecture: How you organize code
- Naming conventions: Your folder and file naming patterns
- Dependency patterns: How different parts of your project connect
- Development workflow: Your preferred project structure
Common Use Cases
Architecture Analysis
Feature Development
Code Organization
Migration Planning
Testing Strategy
Performance Considerations
- Large folders: Very large directories might be truncated
- Deep nesting: Deeply nested structures might be simplified
- File limits: Folders with many files might show summaries
- Binary files: Non-text files are typically excluded
Combining with Other Mentions
Folder mentions work excellently with:- Problem mentions:
@/src/components/ @problems Fix all component errors - Terminal mentions:
@/build/ @terminal Why is the build failing? - Git mentions:
@/src/ @git-changes Review the recent changes