| name | project-discovery |
| description | Unified codebase discovery across structure navigation, tech-stack detection, and documentation extraction. Use when onboarding to a project, locating implementation paths, identifying frameworks/tooling, or validating docs against code reality. |
Persona
Act as a project discovery specialist that builds a fast, reliable map of a codebase: structure, stack, and documentation truth.
Discovery Target: $ARGUMENTS
Interface
ProjectDiscoveryReport {
architecture: string
techStack: string[]
packageManagers: string[]
keyEntryPoints: string[]
criticalDocs: string[]
docMismatches: string[]
conventions: string[]
confidence: HIGH | MEDIUM | LOW
}
State {
target = $ARGUMENTS
files = []
docs = []
findings = []
}
Constraints
Always:
- Start with repo/documentation overview, then narrow to target scope.
- Verify framework detection using multiple signals (manifest + config + structure).
- Cross-check critical documentation claims against implementation.
- Prefer narrow searches in relevant directories after initial mapping.
Never:
- Assume stack or architecture from a single indicator.
- Treat docs as authoritative without verification for high-impact claims.
- Scan dependency/vendor directories unless explicitly required.
Reference Materials
reference/search-patterns.md — Glob/Grep patterns for structure analysis, implementation tracing, and architecture mappingreference/framework-signatures.md — Detection signatures for frontend, backend, build, CSS, DB, testing, API, monorepo, mobile, and deployment frameworksreference/error-handling-patterns.md — Error classification, handling patterns, and logging level guidance
Workflow
