# Project Name - Development Status
## Automated Development System with Anti-Compaction Architecture

**Project Status**: Active Development - Phase 1 Complete
**Automation Level**: 95% - Self-executing development pipeline
**Last Updated**: 2025-07-31 (Auto-generated)

## 🚀 QUICK START - Context Recovery

If you're starting fresh after prompt compaction:

```bash
# 1. Analyze current state (ALWAYS RUN FIRST)
npm run automation:analyze

# 2. Recover project context if needed
npm run automation:recover

# 3. Start the application to test
npm start

# 4. Run daily automation cycle
npm run automation:daily
```

## 🔄 Anti-Compaction System

**Context Preservation Engine**: Automatically preserves project state every 30 minutes
**Auto-Recovery System**: Reconstructs full project context from artifacts
**Daily Automation Cycle**: Runs comprehensive maintenance and progress tracking

### Critical Files for Context Recovery:
- `docs/state/current-state-summary.json` - Latest project state
- `docs/recovery/RECOVERY.md` - Step-by-step recovery instructions
- `scripts/automation/context-analysis.js` - Rapid context analysis
- `scripts/automation/auto-recovery.js` - Full context reconstruction

## 📊 Current Project Status

**Features**: Dynamic analysis pending
**Core Components**: Auto-detected based on project structure
**Test Framework**: Vitest configured
**Automation Scripts**: 4/4 operational

## Development Philosophy

**AUTOMATION-FIRST**: Every task should be automated and self-executing
**COMPACTION-RESISTANT**: All context must survive prompt compaction
**SELF-DOCUMENTING**: Code and decisions must be self-explanatory
**PROGRESSIVE**: Each cycle must advance the project measurably

## Tech Stack

**Testing:** vitest

## Project Structure Rules

false
false
false
## Code Quality Standards

### General Rules
- **File Limits:** Max 200 lines per file (excluding tests)
- **Function Limits:** Max 20 lines per function
- **Complexity:** Avoid deeply nested code (max 3 levels)
- **Naming:** Use descriptive names for variables and functions
- **Comments:** Write self-documenting code, comment only when necessary

### TypeScript/JavaScript

### Python
false
## Feature Implementation

### Priority Order
1. **Must-have features** (Core functionality)
false
2. **Should-have features** (Important enhancements)
true
3. **Nice-to-have features** (Future improvements)
false
## Testing Requirements

- **Unit Tests:** Cover all business logic functions
- **Integration Tests:** Test API endpoints and database operations
- **Component Tests:** Test React components with user interactions
- **E2E Tests:** Cover critical user journeys
- **Coverage Target:** Minimum 80% code coverage

## Development Workflow

### Before Starting Work
1. Review current implementation phase in `docs/implementation.md`
2. Check feature requirements in `docs/features.md`
3. Understand project structure in `docs/project-structure.md`

### During Development
1. Work on one feature at a time
2. Write tests alongside implementation
3. Follow established patterns and conventions
4. Keep commits small and focused

### Before Submitting
- Pre-submit hooks will automatically run quality checks

## Architecture Decisions

### State Management
- Use built-in state management (React Context, component state)
- Keep state simple and close to usage

### API Design

### Database Design

## Performance Guidelines

- **Frontend:** Lazy load components and routes
- **Images:** Optimize and use appropriate formats
- **Bundle Size:** Monitor and minimize JavaScript bundles
- **Database:** Use efficient queries and proper indexing
- **Caching:** Implement appropriate caching strategies

## Security Considerations

- Sanitize data before database operations
- Use environment variables for sensitive data
- Implement proper error handling (don't leak sensitive info)

## Deployment

**Target Platform:** 
- Use environment-specific configurations
- Implement proper health checks
- Set up monitoring and logging
- Use CI/CD for automated deployments

## Resources

- Main documentation: `docs/`
- Implementation guides: `PRPs/`
- Development commands: `.claude/commands/`

## Timeline

**Project Timeline:** enterprise
**Team Size:** solo

Focus on delivering core functionality first, then iterate on enhancements based on user feedback and business needs.