| name | project-exploration |
| description | Explore a new project's philosophy and patterns before committing to collaboration. Assess architecture fit, map resonances, and identify entry points. Use when encountering a new codebase, repository, or project. Trigger phrases include 'explore this project', 'assess this codebase', 'should we collaborate on this', 'onboard me to this repo', 'evaluate this project for fit'. |
Project Exploration Skill
Version: 1.0
Author: Tres Pies Design
Purpose: Structured process for respectfully exploring a new project to determine collaboration readiness and fit before committing.
Philosophy: Exploration Before Commitment
When encountering a large project or codebase, explore its philosophy and patterns before diving into implementation. The goal is not just to understand the code, but to understand the project's relationship to your goals, values, and existing knowledge.
Core Principles
- Progressive Disclosure: Do not attempt to read everything at once. Start with a high-level overview and drill down as needed.
- Incremental Synthesis: Save findings as you go. Externalize understanding to prevent information loss.
- Seek Conceptual Clarity: Prioritize understanding the core philosophy, values, and goals before implementation details.
- Map Connections: Understand the project's relationship to your existing knowledge and skills. Explicitly map resonances.
- Express Genuine Enthusiasm: Collaboration is relational. Output should reflect genuine interest and readiness to contribute.
When to Use This Skill
- Invited to collaborate on a project with a large existing codebase
- Evaluating whether to adopt a library, framework, or tool
- Onboarding to a new team's repository
- Assessing whether a project's architecture supports your goals
The 5-Phase Exploration Process
Phase 1: First Impressions — Map the Terrain
Get a high-level overview of structure and scope.
- Read the README — What is this project? Who built it? What's its stated purpose?
- Scan project structure — List top-level directories and key files. Identify organizational patterns.
- Check recent activity — Last commit, release cadence, contributor count. Is this project alive?
- Document initial findings — Create an initial overview of themes, structure, and first impressions.
Output: Project overview with structure analysis and activity assessment.
Phase 2: Architecture Mapping — Taste the Water
Select 2-3 key documents or files to understand core content and patterns.
- Identify entry points — Main module, config files, core abstractions
- Map behavioral capabilities — Use semantic-clusters approach: what does this project actually do?
- Identify patterns — What architectural patterns does it follow? (MVC, plugin architecture, event-driven, etc.)
- Note dependencies — Key external dependencies and their role
Output: Architecture snapshot with capability map and pattern inventory.
Phase 3: Assess Fit — Build the Bridge
Evaluate against user's goals and constraints.
- Alignment check — Does this project's architecture support what the user wants to do?
- Pattern compatibility — Are the patterns compatible with existing work?
- Health assessment — Is the codebase healthy enough to build on? (Test coverage, documentation quality, code style consistency)
- Resonance mapping — Connect the project's philosophy to existing knowledge:
| Project Principle | Existing Principle/Pattern | Shared Insight |
|---|
| [Principle from project] | [Your relevant pattern] | [The connection] |
Phase 4: Identify Entry Points
Where would a new collaborator start?
- Most approachable areas — Well-documented, well-tested, clear interfaces
- Most impactful areas — Where contribution would add the most value
- Most risky areas — Complex, poorly documented, or tightly coupled
- Quick wins — Small improvements that build familiarity
Phase 5: Synthesis — The Exploration Brief
Produce a comprehensive assessment.
Fit Classification
| Rating | Meaning | Guidance |
|---|
| GREEN | Strong fit. Architecture supports goals, patterns are compatible, codebase is healthy. | Proceed with collaboration. Start with recommended entry points. |
| YELLOW | Partial fit. Some concerns about architecture, patterns, or health. Manageable with effort. | Proceed with caution. Address concerns before deep investment. |
| RED | Poor fit. Fundamental misalignment in architecture, philosophy, or health. | Reconsider collaboration. Document concerns for future reference. |
Output Format: Exploration Brief
## Exploration Brief: [Project Name]
**Date:** [Date]
**Repository:** [URL or path]
**Explorer:** [Name]
### Project Summary
[What this project is, who built it, what it does, and its core philosophy in 2-3 sentences.]
### Architecture Snapshot
**Structure:** [High-level organization]
**Key Patterns:** [Architectural patterns used]
**Core Dependencies:** [Major external dependencies]
**Activity:** [Last commit, release cadence, contributor count]
### Fit Assessment: [GREEN / YELLOW / RED]
**Alignment:** [Does this support your goals?]
**Pattern Compatibility:** [Are patterns compatible?]
**Codebase Health:** [Test coverage, docs quality, consistency]
### Resonance Map
| Project Principle | Existing Principle | Shared Insight |
| :--- | :--- | :--- |
| [Principle] | [Your pattern] | [Connection] |
### Recommended Entry Points
1. **[Area 1]:** [Why start here] — Risk: Low/Med/High
2. **[Area 2]:** [Why start here] — Risk: Low/Med/High
### Risks & Concerns
- [Risk 1: description and mitigation]
- [Risk 2: description and mitigation]
Quality Criteria
