analyze-project-context

name	analyze-project-context
description	Use when starting work on any project (technical or non-technical) to understand structure, standards, and best practices before making changes

Analyze Project Context

Overview

Build comprehensive, evidence-based understanding of ANY project type (code, documentation, content, mixed) before making changes. Works for technical projects, content projects, documentation repositories, and everything in between.

Core principle: Discover what exists, infer patterns, document best practices, establish constitution.

When to Use

Use when:

• Starting work on a new project
• User asks to "analyze the project" or "understand the codebase"
• Before making significant changes
• Need to understand project structure and conventions
• Setting up AI agent workflow for a project

Works for:

• Software projects (Node.js, Python, Go, etc.)
• Documentation repositories
• Content projects (marketing, writing, guides)
• Mixed projects (docs + code)
• Design projects (templates, assets)
• Any organized file structure

Core Principles

• Evidence Over Assumption: Discover what exists, don't assume structure
• Pattern Recognition: Infer conventions from existing files
• Universal Applicability: Works for any project type
• Document Findings: Create AGENTS.md and constitution.md
• Depth Control: Use discovery budget (max 2-3 tool calls per category) to avoid analysis paralysis

Workflow

1. Project Type Detection

Action: Identify project type from file structure

Discovery: