project-overview
NewComplete project architecture and structure guide. Use when exploring the codebase, understanding project organization, finding files, or needing comprehensive architectural context. Triggers on architecture questions, directory navigation, or project overview needs.
Summary
This skill provides a comprehensive overview of the project's architecture, directory structure, and key files, helping developers quickly understand how the codebase is organized.
- It is especially useful when onboarding to a new project, navigating unfamiliar code, or needing high-level context before making changes.
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "project-overview": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/project-overview
Show me the project structure and main directories.
What is the architecture of this project and where are the key files?
Security Audits
Frequently Asked Questions
What is project-overview?
This skill provides a comprehensive overview of the project's architecture, directory structure, and key files, helping developers quickly understand how the codebase is organized. It is especially useful when onboarding to a new project, navigating unfamiliar code, or needing high-level context before making changes.
How to install project-overview?
To install project-overview: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "project-overview": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is project-overview best for?
project-overview is a mcp categorized under General. It is designed for: planning, coding. Created by lobehub.
What can I use project-overview for?
project-overview is useful for: When joining a new project and needing to understand its overall structure and key components.; When searching for a specific file or module but unsure where it lives in the directory tree.; When planning a new feature and needing to know which parts of the codebase will be affected.; When debugging an issue and needing to trace the flow across different layers or services.; When reviewing a pull request and wanting to see how the changes fit into the broader architecture.; When documenting the project and needing a clear summary of its organization..