Claude Code Project Analyzer

This skill helps you understand and work with codebases that use CLAUDE.md files for project documentation. It provides comprehensive analysis of project architecture, development workflows, security patterns, and deployment procedures.

What This Skill Does

When working with a repository containing a CLAUDE.md file, this skill will:

1. Read and analyze the project documentation

2. Understand the architecture and technology stack

3. Identify security patterns and implementation details

4. Guide you through development and deployment workflows

5. Help you make modifications safely while respecting security constraints

Instructions

When a user asks about a project with a CLAUDE.md file or requests help working with their codebase:

Step 1: Locate and Read Project Documentation

First, check if a CLAUDE.md file exists in the repository root:

```bash

Check for CLAUDE.md file

ls -la CLAUDE.md

```

If found, read the complete file:

```bash

Read the project documentation

cat CLAUDE.md

```

Step 2: Analyze Project Structure

Based on the CLAUDE.md content, identify and summarize:

**Project Type**: Framework, language, and purpose

**Key Components**: Main application files and their responsibilities

**Architecture Pattern**: How the application is structured

**Technology Stack**: Frameworks, libraries, and tools used

Step 3: Understand Development Workflow

Extract and explain:

**Local Development Commands**: How to run, build, and test the application

**Environment Setup**: Required environment variables and configuration

**Development Flow**: Branch strategy, deployment pipeline, and environments

Step 4: Identify Security Patterns

Analyze and document:

**Authentication Mechanisms**: How the application authenticates requests

**Authorization Rules**: Role-based access controls or permissions

**Rate Limiting**: Request throttling and abuse prevention

**Input Validation**: Data validation and sanitization patterns

**Hardcoded Parameters**: Security constraints that prevent modification

**IMPORTANT**: When security controls are explicitly marked as intentional (e.g., "intentionally restrictive", "intentionally immutable"), always respect these constraints. Do not suggest modifications that would weaken security unless the user has a specific, justified reason.

Step 5: Provide Context-Aware Guidance

When the user asks for help:

**For general questions**: Provide an overview referencing specific sections of CLAUDE.md

**For modification requests**: Check if the change affects security-critical code and warn accordingly

**For deployment questions**: Reference the deployment section and provide step-by-step guidance

**For debugging**: Identify relevant files and architectural patterns that might be involved

Step 6: Reference Specific Code Locations

When discussing implementation details, always reference:

**File paths**: Exact location of relevant code

**Line numbers**: When mentioned in CLAUDE.md (format: `file:line`)

**Code patterns**: Specific implementation patterns to follow or avoid

Step 7: Respect Project Constraints

Always honor constraints documented in CLAUDE.md:

**Hardcoded security parameters**: Do not suggest making them configurable

**Rate limits**: Explain why they exist before suggesting changes

**Deployment requirements**: Follow documented deployment procedures

**Environment-specific behavior**: Respect differences between dev/staging/production

Examples

**Example 1: Understanding Project Setup**

User: "How do I set up this project locally?"

Response:

1. Read CLAUDE.md to find development commands

2. Identify required environment variables

3. Provide step-by-step setup instructions

4. Warn about any security-critical configuration

**Example 2: Analyzing Security Architecture**

User: "Why can't I change the Claude model in my API request?"

Response:

1. Locate the API route implementation (e.g., `app/api/chat/route.ts`)

2. Explain the hardcoded parameter pattern

3. Reference the security rationale from CLAUDE.md

4. Explain this is intentional to prevent abuse and cost overruns

**Example 3: Deployment Guidance**

User: "How do I deploy this to production?"

Response:

1. Extract deployment commands from CLAUDE.md

2. List required environment variables

3. Provide step-by-step deployment process

4. Include post-deployment verification steps

Important Notes

**Always read CLAUDE.md first** before making suggestions about the codebase

**Respect security-by-design patterns** - they are intentional, not bugs

**Reference documentation directly** - use quotes and file:line references

**Understand the context** - different projects have different constraints

**Ask for clarification** if the user wants to modify security-critical code

When to Use This Skill

Use this skill whenever:

A user mentions working with a CLAUDE.md file

You need to understand a project's architecture and constraints

Someone asks about development, deployment, or security patterns

You're helping modify code and need to understand project-specific guidelines

A user wants to know "how things work" in their codebase

This skill is especially valuable for onboarding new developers to codebases that follow the CLAUDE.md documentation pattern.

Claude Code Project Analyzer

Claude Code Project Analyzer

What This Skill Does

Instructions

Step 1: Locate and Read Project Documentation

Check for CLAUDE.md file

Read the project documentation

Step 2: Analyze Project Structure

Step 3: Understand Development Workflow

Step 4: Identify Security Patterns

Step 5: Provide Context-Aware Guidance

Step 6: Reference Specific Code Locations

Step 7: Respect Project Constraints

Examples

Important Notes

When to Use This Skill

Reviews (0)