A collection of AI applications for document processing, transcript analysis, and presentation generation.
Convert meeting transcripts into professional PowerPoint presentations with AI-generated visuals.
Features:
- Smart transcript analysis with GPT-4o-mini
- Automated slide generation
- DALL-E 3 image creation
- Performance timing metrics
Quick Start:
cd openai
pip install -r requirements.txt
streamlit run app.pyConvert meeting transcripts into professional PowerPoint presentations using collaborative AI agents for optimized cost and performance.
Features:
- Multi-agent AI workflow (Analyzer → Designer → Optimizer)
- 90% cost reduction vs image-based approaches
- Text-only slide generation for maximum efficiency
- GPT-4o-mini optimization with token control
- Professional business presentation output
Quick Start:
cd crewai
pip install -r requirements.txt
streamlit run app.py- Python 3.8+
- OpenAI API key
- Copy
.env.exampleto.env(if available) - Add your API keys:
OPENAI_API_KEY=your-api-key-hereSee ENV_GUIDE.md for detailed environment variable management across folders
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activatetranscript_to_powerpoint/
├── .env # Shared environment variables
├── .gitignore # Global ignore patterns
├── README.md # This file
├── openai/ # OpenAI-based transcript processor
│ ├── .env # App-specific environment (optional)
│ ├── app.py # Main Streamlit application
│ ├── requirements.txt # Dependencies
│ ├── ARCHITECTURE.md # Technical documentation
│ └── README.md # App-specific guide
├── crewai/ # CrewAI multi-agent transcript processor
│ ├── .env # App-specific environment (optional)
│ ├── app.py # Main Streamlit application
│ ├── requirements.txt # Dependencies
│ └── README.md # App-specific guide
└── [future apps]/ # Additional AI applications
-
Create App Directory:
mkdir new-app-name cd new-app-name -
App Structure:
new-app-name/ ├── .env # App-specific config (optional) ├── app.py # Main application ├── requirements.txt # Dependencies └── README.md # Documentation -
Environment Variables:
- Use root
.envfor shared variables (API keys) - Create app
.envonly for app-specific settings
- Use root
- Root
.env: Shared across all apps (API keys, global settings) - App
.env: App-specific overrides or additional variables - Load order: App
.envoverrides root.env
- Each app has its own
requirements.txt - Keep dependencies minimal and app-specific
- Document any special installation requirements
- Each app must have its own README.md
- Include quick start, features, and usage examples
- Technical details go in ARCHITECTURE.md (if complex)
- Create new apps in separate directories
- Follow the established structure
- Include proper documentation
- Test with sample data before committing
[Specify your license here]