Marvin Nahmias & Javier Hauss · Alpura · Mexico City
Build enterprise Databricks apps in days. Not months.
Every layer constrains the one above it. AI generates code inside those constraints — it never defines the architecture.
"AI doesn't generate architecture — it generates code. Architecture has to be defined first, then enforced as constraints."
Two complementary layers. One keeps every generation on-rails. The other loads domain expertise only when needed.
Each skill is a focused context file deployed to your Databricks workspace. @mention any skill in Genie Code Agent Mode to load its expertise.
Four steps from repo to running Databricks app. Most apps go from spec to shipped in a single Genie Code session.
Requires Databricks CLI v0.200+ and a configured profile. Everything else is a single shell script.
databricks auth login.mexmarv/ai-genie-factory from GitHub and navigate to the root.# 1. Authenticate (one-time) databricks auth login # 2. Clone git clone https://github.com/mexmarv/ai-genie-factory cd ai-genie-factory # 3a. Deploy to your personal .assistant folder ./deploy.sh # 3b. Deploy workspace-wide (admin required) ./deploy.sh --workspace # 3c. Use a specific CLI profile ./deploy.sh --profile my-profile # 4. Rebuild AGENTS.md after editing modules python build_agents.py
deploy.sh uses --format RAW to upload .md files — import-dir only handles notebooks.
Two APP.md specs included. Start with NYC Taxi Explorer to verify the factory works before building on your own data.