Documentation.maverick Structure
← Back to Docs.maverick File Structure
The .maverick file is the heart of Maverick's plugin architecture. It defines workspaces, AI instructions, team configuration, and custom themes. Learn how to create extensible, self-documenting project structures.
Fractal Workspace Architecture
How .maverick files create nested, composable workspaces
# Example project structure
company-root/
├── .maverick # Root company workspace
├── instructions.md # Company-wide AI context
├── status.md # Real-time project status
├── legal/
│ ├── .maverick # Legal workspace
│ ├── instructions.md # Legal AI instructions
│ └── incorporation/
├── products/
│ ├── mobile-app/
│ │ ├── .maverick # Product workspace
│ │ ├── instructions.md # Product AI context
│ │ ├── status.md # Product status
│ │ └── features/
│ │ ├── auth/
│ │ │ ├── .maverick # Feature workspace
│ │ │ └── instructions.md
│ │ └── payments/
│ │ ├── .maverick # Feature workspace
│ │ └── instructions.md
🎯 Key Principles
- • Physical structure = Logical architecture
- • Each .maverick defines a bounded context
- • AI instructions inherit from parent workspaces
- • Moving folders = Refactoring system design
🌀 Plugin Architecture
- • Custom themes and look-and-feel
- • Extensible component systems
- • Template-driven generation
- • Community-driven improvements
Essential Files in Each Workspace
.maverick
JSON configuration defining workspace scope, team, AI preferences, and theme
instructions.md
AI-specific instructions and context for this workspace
status.md
Real-time status updates, always kept current by AI
Ready to Create Your First .maverick Workspace?
Start building with templates or create your own extensible workspace