This repository is a meticulously curated knowledge base and toolkit for AI video prompt engineering. Its core is a structured data pipeline: raw knowledge from official vendor documentation and YouTube masterclasses is reverse-engineered into standardized methodologies (21+ SOPs) and a centralized prompt database (`prompts/data/all-prompts.json`). This data is then exposed through a cross-model benchmark (`prompts/data/cross-model-matrix.json`), zero-dependency web tools (Prompt Browser, Cross-Model Matrix), and executable Claude Code Skills (`skills/`). The architecture is data-centric. The primary value lies in the curated, structured data assets and the rigorous methodology used to create them. The application layer (web tools, skills) is a thin, well-crafted consumer of this data. The repository actively manages its primary risk—model version drift—through an automated monitoring system (`scripts/monitor_models.py`) that hashes external endpoints and files issues on change. While primarily a data_research project, it exhibits strong application characteristics through its interactive tools and AI skill integrations. It is a living knowledge base, actively maintained with a clear contribution workflow and a strong emphasis on data provenance and reproducibility. The `cross-model-matrix.json` is a standout asset, providing a controlled benchmark for comparing prompt styles across 11 major AI video models.
dembrandt is a production-grade design token extraction tool that analyzes live websites via headless Chromium (Playwright) and produces structured outputs including colors, typography, spacing, components, shadows, motion, and gradients. It supports multiple export formats: W3C DTCG tokens, Tailwind CSS v4 themes, DESIGN.md, self-contained HTML reports, PDF brand guides, and terminal display. Beyond extraction, it offers drift detection (comparing extractions over time with a 0–100 score), a GitHub Action for CI gates, and an MCP server for AI agent integration (Claude, Cursor). The architecture is modular with fault-isolated extractors, a pure-function drift engine, and a generic async job queue. While primarily an application, it includes an optional ONNX ML model for brand primary color prediction and advanced color science (OKLab, CIEDE2000, gamut mapping), giving it a hybrid character. The codebase demonstrates strong engineering practices: extensive test coverage, CI/CD pipelines, lazy browser loading, and graceful degradation across all output formatters.
Atlantis is a self-hosted Go application that automates Terraform and OpenTofu workflows triggered by pull request events. It listens for webhooks from GitHub, GitLab, Bitbucket Cloud/Server, Azure DevOps, and Gitea, then executes Terraform commands (plan, apply, import, state rm, version) and reports results via PR comments and commit statuses. The system enforces approval, mergeability, and policy requirements, supports drift detection and remediation, and provides a web UI for lock management and streaming logs. The architecture is a monolithic server with modular components: HTTP controllers for webhook handling, command runners for orchestrating workflows, step runners for individual Terraform operations, VCS client abstractions for multi-provider support, and pluggable persistence (BoltDB embedded, optional Redis, S3 for plan storage). Configuration is layered via server-side YAML, repo-level atlantis.yaml, and CLI flags. Key entry points include main.go (CLI), cmd/server.go (server command), server/controllers/events/events_controller.go (webhook dispatcher), and server/events/command_runner.go (command orchestration). External dependencies include Terraform/OpenTofu binaries, Conftest for policy checks, VCS APIs, and optional Redis/S3. The codebase demonstrates strong engineering practices with extensive unit/integration/e2e tests, instrumentation for metrics, structured logging, and security-conscious design (webhook signature validation, path traversal prevention, shell injection mitigation). While the project is actively maintained, technical drift is medium due to large dependency surface, mock generation sprawl, and complex VCS integration parity.
StreamForge AI is a real-time data platform designed for ML/AI workloads, integrating CDC ingestion, stream processing, feature storage, and serving. The architecture comprises distinct layers: ingestion (Debezium/Kafka), processing (Flink), storage (MinIO/S3 with optional Iceberg), and serving (online/offline feature store). Key components include a control plane API/UI for pipeline management, a Feast/Tecton-compatible feature store, schema registry client, drift detector, lineage tracker, and prefetch engine for ML training optimization. The platform supports end-to-end pipelines from database changes to feature materialization and inference, with examples demonstrating ML training, real-time serving, and feature consumption. While the system demonstrates strong modularity and integration of industry-standard tools, its operational complexity and polyglot nature (Java/Python/JS) present maintenance challenges.
Digger (now OpenTaco) is an infrastructure-as-code orchestration platform that automates Terraform, OpenTofu, Terragrunt, and Pulumi workflows within existing CI/CD pipelines. The system provides PR-level automation (plan/apply comments), drift detection, policy-as-code via OPA, and an optional Terraform Enterprise-compatible state management and remote execution layer. It integrates with GitHub, GitLab, Bitbucket, Azure DevOps, and Buildkite through webhooks and CI backends. The architecture is a multi-service monorepo: a Go backend (Gin/GORM) handles webhooks, job scheduling, and a web UI; a separate CLI tool (cobra) runs directly in CI; a drift detection service with cron scheduling; a sandbox sidecar (TypeScript/Node) for remote execution; and the Taco service (Echo) that reimplements TFE APIs for state management, RBAC, and run execution. The UI is a React/TanStack Router app with WorkOS authentication. The codebase is actively maintained with frequent releases, extensive SQL migrations, Helm charts for Kubernetes deployment, and dual open-core and enterprise (ee/) feature sets.
Renate is a Python library for continual learning that provides implementations of various algorithms (Experience Replay, DER, Super-ER, etc.) to mitigate catastrophic forgetting when updating neural networks on sequential data. It features a modular architecture separating models, data handling, update strategies, memory buffers, and drift detection, enabling users to customize continual learning pipelines. The framework supports local execution and cloud deployment via Amazon SageMaker, includes hyperparameter optimization through Syne Tune, and offers benchmarking tools for evaluating continual learning methods across diverse datasets and scenarios. Key reusable components include a memory buffer system with reservoir and class-balancing strategies, Maximum Mean Discrepancy (MMD) based drift detectors for monitoring data distribution shifts, and a composable loss component system for constructing complex continual learning objectives. The library integrates with PyTorch Lightning for training and provides abstract base classes for models and data modules to facilitate extension. Although the project is explicitly archived and no longer maintained, the codebase demonstrates solid engineering practices with well-defined interfaces and decoupled components. It has been tested on vision and NLP benchmarks (CIFAR, CLEAR, DomainNet, Hugging Face datasets) and includes synthetic scenario generators for controlled experimentation. The archival status indicates that users should expect no further updates or security patches, but the core functionality remains usable for continual learning research and applications.