EdCoach AI Documentation

Last Updated: September 17, 2025
Purpose: Single navigation hub for all EdCoach AI project information
Structure: Optimized for maximum maintainability with minimum overhead

---

🎯 Core Documentation (START HERE)

📖 CONTEXT.md - Master Context (Single Source of Truth)

Everything you need to know about EdCoach AI in one comprehensive file (650+ lines):

• 🎯 Project Foundation: Mission, continuous growth loop, current status (87% complete)
• 👥 User Context: Detailed personas (Sarah & Michael), transformation focus, competitive differentiation
• 🏗️ Technical Context: Complete architecture, data models, performance standards, security
• 🎨 Design Context: Typography system, color palette, component architecture, accessibility standards
• 🔄 Core Workflow: Detailed 5-phase continuous growth loop with entry points and outcomes
• 🚀 Strategic Priorities: P0/P1/P2 roadmap with problems, solutions, and impact assessment
• 🔒 Business Model: Revenue strategy, pricing tiers, go-to-market, competitive positioning
• 📊 Success Framework: KPIs, quality standards, maintenance guidelines

🎨 brand-guidelines.md - Brand Identity & Visual System

Complete brand system with logo strategy and implementation:

• 🎨 Logo System: Hybrid approach with 3 strategic variations (Primary/Storytelling/Innovation)
• 🎯 Brand Identity: Mission-driven personality and competitive positioning
• 📱 Mobile Optimization: iPad coaching and iPhone reflection workflows
• 🎨 Color Palette: Professional Growth Palette with semantic usage guidelines
• 📋 Implementation: Asset organization, usage guidelines, technical specifications

---

🤖 Agent Coordination System

👥 agents/README.md - 5-Agent Development Workflow

Overview of coordinated development process and quality standards.

Specialized Agent Instructions

• 🎯 Product Manager - Business strategy, user experience, backlog prioritization
• 🏗️ System Architect - Technical architecture, API contracts, system design
• ⚙️ Backend Engineer - Convex implementation, AI integration, data management
• 🎨 Frontend Engineer - Next.js/React implementation, UI development
• 🎨 UX Designer - User experience design, design system, accessibility

Note: All agent files are lightweight and reference the Master Context for comprehensive project information.

---

📁 Archive Documentation

Legacy Documentation (Historical Reference)

• 📊 archive/business/ - Detailed business analysis and marketing strategy
• 🔧 archive/technical/ - Technical deep-dive and implementation standards
• 🎨 archive/design/ - Design system specifications and component library

Note: This information has been consolidated into CONTEXT.md and brand-guidelines.md for easier maintenance. Archive remains for historical reference and detailed specifications.

---

🚀 Quick Start by Role

New to the Project?

1. Start with: CONTEXT.md - Read the entire file (15-20 minutes)
2. Brand system: brand-guidelines.md for visual identity
3. Role-specific: Check your agent file for detailed responsibilities
4. Development: See .cursorrules in project root for coding patterns

For Product Managers

• Primary: CONTEXT.md → Focus on User Context + Strategic Priorities + Business Model
• Secondary: agents/product-manager.md for methodology and frameworks

For System Architects

• Primary: CONTEXT.md → Focus on Technical Context + Performance Requirements
• Secondary: agents/system-architect.md for architecture patterns

For UX/UI Designers

• Primary: CONTEXT.md → Focus on Design Context + User Context
• Brand System: brand-guidelines.md for visual identity and logo usage
• Secondary: agents/ux-designer.md for design methodology

For Backend Engineers

• Primary: CONTEXT.md → Focus on Technical Context + Core Workflow
• Secondary: agents/backend-engineer.md for implementation patterns

For Frontend Engineers

• Primary: CONTEXT.md → Focus on Technical + Design Context
• Brand System: brand-guidelines.md for logo implementation
• Secondary: agents/frontend-engineer.md for React/Next.js patterns

---

🔍 Finding Information

Project Understanding

→ CONTEXT.md - Complete project context in single file

Visual Identity & Branding

→ brand-guidelines.md - Logo system, colors, implementation

Agent Coordination

→ agents/README.md - Development workflow and handoff patterns

Development Patterns

→ .cursorrules in project root - Quick reference for coding standards

Historical Context

→ archive/ - Legacy documentation for detailed historical reference

---

📝 Maintenance Excellence

Documentation Ownership

• CONTEXT.md: Product Manager (lead) + all senior roles
• brand-guidelines.md: UX Designer + Product Manager
• Agent files: Respective role owners
• This README: System Architect

Update Process

• Context Changes: Update CONTEXT.md (single source of truth)
• Brand Changes: Update brand-guidelines.md
• Process Changes: Update agents/README.md
• Role Changes: Update specific agent files

Quality Standards

• Single Source: No information duplication across files
• Clear Navigation: Every piece of information has a clear location
• Version Control: Track all changes with proper commit messages
• Review Cycle: Quarterly comprehensive review, monthly tactical updates

---

📊 Documentation Structure Benefits

Maximum Maintainability Achieved

• 2 Core Files: CONTEXT.md + brand-guidelines.md contain 95% of needed information
• 5 Agent Files: Lightweight, role-specific instructions that reference core files
• 1 Navigation Hub: This README provides clear entry points
• Archive System: Legacy docs preserved but not cluttering active workspace

Maintenance Overhead Reduction

Metric	Before	After	Improvement
Active Files	15+ files	8 files	47% reduction
Update Points	Multiple	2 master files	85% reduction
Navigation Complexity	High	Single hub	Clear path
Information Duplication	Significant	Zero	100% elimination

---

This documentation structure provides maximum maintainability with minimum overhead. All project context lives in clearly organized files with zero duplication and clear ownership.