Vibecode Gamma
track this build5 phases, 16 steps, beginner friendly0%KINDA · weekend project
An AI slide generator is buildable, but Gamma's strength is layouts, editing model, exports, hosting, analytics, and shareable deck/site UX.
the project pack5 files · written for this build, step by step
You are building a lean indie version of Gamma. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Gamma · indie build Build a local AI-assisted slide-card editor with printable decks. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Gamma acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. - [ ] **Ollama with an explicitly local model** · No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Why: Generation requires a running model; ordinary editing remains usable while it is unavailable. - Get it: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. - Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration If one of those is essential to you, that is the reason to keep paying for Gamma, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Gamma The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a local AI-assisted slide-card editor with printable decks as a bounded replacement for Gamma. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - decks(id,title,theme_json) - slides(id,deck_id,position,layout,title,body_json,notes,revision) - generations(id,deck_id,slide_id,input_hash,model,status) - assets(id,deck_id,path,credit) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: A five-slide deck with title, bullets, two-column, quote and image layouts. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Gamma acceptance sample: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start outline before generation until these checks pass. ### Phase 2 · Outline before generation Build: Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A plausible model fact is not verified evidence; supplied facts remain the source of truth. Done when: Malformed model JSON produces an editable error with no partial saved deck. Changing the outline order preserves each slide id. Do not build yet: Do not start slide revision until these checks pass. ### Phase 3 · Slide revision Build: Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Model-generated HTML must not execute inside the editor. Done when: Regenerating slide three leaves the other four unchanged. A stale regeneration cannot replace a newer manual edit. Do not build yet: Do not start readable export until these checks pass. ### Phase 4 · Readable export Build: Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. Done when: The five-slide fixture prints to exactly five readable pages. The HTML deck opens offline with all supplied assets. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Gamma replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor: retain the paid product if this capability is essential; it is outside this bounded build. - responsive card model: retain the paid product if this capability is essential; it is outside this bounded build. - exports: retain the paid product if this capability is essential; it is outside this bounded build. - analytics: retain the paid product if this capability is essential; it is outside this bounded build. - custom domains: retain the paid product if this capability is essential; it is outside this bounded build. - template quality: retain the paid product if this capability is essential; it is outside this bounded build. - collaboration: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Gamma indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - A plausible model fact is not verified evidence; supplied facts remain the source of truth. - Model-generated HTML must not execute inside the editor. - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Gamma Build a local AI-assisted slide-card editor with printable decks. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Outline before generation Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. ### Steps 1. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Files: `features/outline_before_generation.py`, `templates/outline_before_generation.html` 2. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Files: `features/outline_before_generation.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_outline_before_generation.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Changing the outline order preserves each slide id. ### Watch out - A plausible model fact is not verified evidence; supplied facts remain the source of truth. ## Phase 3 · Slide revision Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. ### Steps 1. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Files: `features/slide_revision.py`, `templates/slide_revision.html` 2. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Files: `features/slide_revision.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_slide_revision.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Regenerating slide three leaves the other four unchanged. - [ ] A stale regeneration cannot replace a newer manual edit. ### Watch out - Model-generated HTML must not execute inside the editor. ## Phase 4 · Readable export Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. ### Steps 1. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Files: `features/readable_export.py`, `templates/readable_export.html` 2. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Files: `features/readable_export.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_readable_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] The HTML deck opens offline with all supplied assets. ### Watch out - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. ## Phase 5 · Portable delivery and clean-start proof Finish the Gamma replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration ## After v1, if you want it - Extend readable export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/gamma # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
You are building a lean indie version of Gamma. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Gamma · indie build Build a local AI-assisted slide-card editor with printable decks. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Gamma acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. - [ ] **Ollama with an explicitly local model** · No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Why: Generation requires a running model; ordinary editing remains usable while it is unavailable. - Get it: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. - Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration If one of those is essential to you, that is the reason to keep paying for Gamma, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Gamma The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a local AI-assisted slide-card editor with printable decks as a bounded replacement for Gamma. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - decks(id,title,theme_json) - slides(id,deck_id,position,layout,title,body_json,notes,revision) - generations(id,deck_id,slide_id,input_hash,model,status) - assets(id,deck_id,path,credit) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: A five-slide deck with title, bullets, two-column, quote and image layouts. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Gamma acceptance sample: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start outline before generation until these checks pass. ### Phase 2 · Outline before generation Build: Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A plausible model fact is not verified evidence; supplied facts remain the source of truth. Done when: Malformed model JSON produces an editable error with no partial saved deck. Changing the outline order preserves each slide id. Do not build yet: Do not start slide revision until these checks pass. ### Phase 3 · Slide revision Build: Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Model-generated HTML must not execute inside the editor. Done when: Regenerating slide three leaves the other four unchanged. A stale regeneration cannot replace a newer manual edit. Do not build yet: Do not start readable export until these checks pass. ### Phase 4 · Readable export Build: Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. Done when: The five-slide fixture prints to exactly five readable pages. The HTML deck opens offline with all supplied assets. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Gamma replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor: retain the paid product if this capability is essential; it is outside this bounded build. - responsive card model: retain the paid product if this capability is essential; it is outside this bounded build. - exports: retain the paid product if this capability is essential; it is outside this bounded build. - analytics: retain the paid product if this capability is essential; it is outside this bounded build. - custom domains: retain the paid product if this capability is essential; it is outside this bounded build. - template quality: retain the paid product if this capability is essential; it is outside this bounded build. - collaboration: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Gamma indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - A plausible model fact is not verified evidence; supplied facts remain the source of truth. - Model-generated HTML must not execute inside the editor. - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Gamma Build a local AI-assisted slide-card editor with printable decks. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Outline before generation Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. ### Steps 1. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Files: `features/outline_before_generation.py`, `templates/outline_before_generation.html` 2. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Files: `features/outline_before_generation.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_outline_before_generation.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Changing the outline order preserves each slide id. ### Watch out - A plausible model fact is not verified evidence; supplied facts remain the source of truth. ## Phase 3 · Slide revision Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. ### Steps 1. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Files: `features/slide_revision.py`, `templates/slide_revision.html` 2. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Files: `features/slide_revision.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_slide_revision.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Regenerating slide three leaves the other four unchanged. - [ ] A stale regeneration cannot replace a newer manual edit. ### Watch out - Model-generated HTML must not execute inside the editor. ## Phase 4 · Readable export Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. ### Steps 1. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Files: `features/readable_export.py`, `templates/readable_export.html` 2. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Files: `features/readable_export.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_readable_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] The HTML deck opens offline with all supplied assets. ### Watch out - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. ## Phase 5 · Portable delivery and clean-start proof Finish the Gamma replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration ## After v1, if you want it - Extend readable export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/gamma # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
You are building a production product version of Gamma. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Gamma · product brief ## Problem An AI slide generator is buildable, but Gamma's strength is layouts, editing model, exports, hosting, analytics, and shareable deck/site UX. ## Product outcome An operated version of a local AI-assisted slide-card editor with printable decks, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - LLM API - slide renderer - template system - export pipeline - hosted app - optional image API ## Explicit non-goals for v1 - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration ## Success criteria - Malformed model JSON produces an editable error with no partial saved deck. - Regenerating slide three leaves the other four unchanged. - The five-slide fixture prints to exactly five readable pages. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs. ===== BRIEF.md ===== # Build brief · Gamma The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a local AI-assisted slide-card editor with printable decks as a bounded replacement for Gamma. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - decks(id,title,theme_json) - slides(id,deck_id,position,layout,title,body_json,notes,revision) - generations(id,deck_id,slide_id,input_hash,model,status) - assets(id,deck_id,path,credit) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: A five-slide deck with title, bullets, two-column, quote and image layouts. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Gamma acceptance sample: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start outline before generation until these checks pass. ### Phase 2 · Outline before generation Build: Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A plausible model fact is not verified evidence; supplied facts remain the source of truth. Done when: Malformed model JSON produces an editable error with no partial saved deck. Changing the outline order preserves each slide id. Do not build yet: Do not start slide revision until these checks pass. ### Phase 3 · Slide revision Build: Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Model-generated HTML must not execute inside the editor. Done when: Regenerating slide three leaves the other four unchanged. A stale regeneration cannot replace a newer manual edit. Do not build yet: Do not start readable export until these checks pass. ### Phase 4 · Readable export Build: Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. Done when: The five-slide fixture prints to exactly five readable pages. The HTML deck opens offline with all supplied assets. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Gamma replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor: retain the paid product if this capability is essential; it is outside this bounded build. - responsive card model: retain the paid product if this capability is essential; it is outside this bounded build. - exports: retain the paid product if this capability is essential; it is outside this bounded build. - analytics: retain the paid product if this capability is essential; it is outside this bounded build. - custom domains: retain the paid product if this capability is essential; it is outside this bounded build. - template quality: retain the paid product if this capability is essential; it is outside this bounded build. - collaboration: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested. ===== ARCHITECTURE.md ===== # Architecture · Gamma ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Outline before generation | Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. | Keep the acceptance contract: Malformed model JSON produces an editable error with no partial saved deck. Replace only this module after replaying its fixture; preserve ids and existing records. | | Slide revision | Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. | Keep the acceptance contract: Regenerating slide three leaves the other four unchanged. Replace only this module after replaying its fixture; preserve ids and existing records. | | Readable export | Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. | Keep the acceptance contract: The five-slide fixture prints to exactly five readable pages. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. - `OLLAMA_URL` · required · Keep the inference service bound to loopback; the backend calls it, never the public browser. - `LOCAL_MODEL` · required · Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it. ===== AGENTS.md ===== # Agent instructions · Gamma product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - A plausible model fact is not verified evidence; supplied facts remain the source of truth. - Model-generated HTML must not execute inside the editor. - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== MILESTONES.md ===== # Delivery milestones · Gamma Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Outline before generation Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. ### Steps 1. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Files: `features/outline_before_generation.py`, `templates/outline_before_generation.html` 2. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Files: `features/outline_before_generation.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_outline_before_generation.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Changing the outline order preserves each slide id. ### Watch out - A plausible model fact is not verified evidence; supplied facts remain the source of truth. ## M3 · Slide revision Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. ### Steps 1. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Files: `features/slide_revision.py`, `templates/slide_revision.html` 2. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Files: `features/slide_revision.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_slide_revision.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Regenerating slide three leaves the other four unchanged. - [ ] A stale regeneration cannot replace a newer manual edit. ### Watch out - Model-generated HTML must not execute inside the editor. ## M4 · Readable export Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. ### Steps 1. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Files: `features/readable_export.py`, `templates/readable_export.html` 2. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Files: `features/readable_export.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_readable_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] The HTML deck opens offline with all supplied assets. ### Watch out - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. ## M5 · Portable delivery and clean-start proof Finish the Gamma replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== OPERATIONS.md ===== # Operations · Gamma ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Outline before generation, Slide revision, Readable export. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Regenerating slide three leaves the other four unchanged. - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Gamma capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/gamma # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
README.md
# Gamma · indie build Build a local AI-assisted slide-card editor with printable decks. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Gamma acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. - [ ] **Ollama with an explicitly local model** · No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Why: Generation requires a running model; ordinary editing remains usable while it is unavailable. - Get it: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. - Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration If one of those is essential to you, that is the reason to keep paying for Gamma, and the README should say so rather than pretend.
BRIEF.md
# Build brief · Gamma The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a local AI-assisted slide-card editor with printable decks as a bounded replacement for Gamma. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - decks(id,title,theme_json) - slides(id,deck_id,position,layout,title,body_json,notes,revision) - generations(id,deck_id,slide_id,input_hash,model,status) - assets(id,deck_id,path,credit) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: A five-slide deck with title, bullets, two-column, quote and image layouts. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Gamma acceptance sample: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start outline before generation until these checks pass. ### Phase 2 · Outline before generation Build: Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A plausible model fact is not verified evidence; supplied facts remain the source of truth. Done when: Malformed model JSON produces an editable error with no partial saved deck. Changing the outline order preserves each slide id. Do not build yet: Do not start slide revision until these checks pass. ### Phase 3 · Slide revision Build: Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Model-generated HTML must not execute inside the editor. Done when: Regenerating slide three leaves the other four unchanged. A stale regeneration cannot replace a newer manual edit. Do not build yet: Do not start readable export until these checks pass. ### Phase 4 · Readable export Build: Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. Done when: The five-slide fixture prints to exactly five readable pages. The HTML deck opens offline with all supplied assets. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Gamma replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor: retain the paid product if this capability is essential; it is outside this bounded build. - responsive card model: retain the paid product if this capability is essential; it is outside this bounded build. - exports: retain the paid product if this capability is essential; it is outside this bounded build. - analytics: retain the paid product if this capability is essential; it is outside this bounded build. - custom domains: retain the paid product if this capability is essential; it is outside this bounded build. - template quality: retain the paid product if this capability is essential; it is outside this bounded build. - collaboration: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested.
AGENTS.md
# Agent instructions · Gamma indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - A plausible model fact is not verified evidence; supplied facts remain the source of truth. - Model-generated HTML must not execute inside the editor. - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · Gamma Build a local AI-assisted slide-card editor with printable decks. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Outline before generation Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. ### Steps 1. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Files: `features/outline_before_generation.py`, `templates/outline_before_generation.html` 2. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Files: `features/outline_before_generation.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_outline_before_generation.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Changing the outline order preserves each slide id. ### Watch out - A plausible model fact is not verified evidence; supplied facts remain the source of truth. ## Phase 3 · Slide revision Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. ### Steps 1. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Files: `features/slide_revision.py`, `templates/slide_revision.html` 2. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Files: `features/slide_revision.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_slide_revision.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Regenerating slide three leaves the other four unchanged. - [ ] A stale regeneration cannot replace a newer manual edit. ### Watch out - Model-generated HTML must not execute inside the editor. ## Phase 4 · Readable export Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. ### Steps 1. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Files: `features/readable_export.py`, `templates/readable_export.html` 2. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Files: `features/readable_export.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_readable_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] The HTML deck opens offline with all supplied assets. ### Watch out - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. ## Phase 5 · Portable delivery and clean-start proof Finish the Gamma replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration ## After v1, if you want it - Extend readable export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/gamma # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
PRODUCT.md
# Gamma · product brief ## Problem An AI slide generator is buildable, but Gamma's strength is layouts, editing model, exports, hosting, analytics, and shareable deck/site UX. ## Product outcome An operated version of a local AI-assisted slide-card editor with printable decks, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - LLM API - slide renderer - template system - export pipeline - hosted app - optional image API ## Explicit non-goals for v1 - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor - responsive card model - exports - analytics - custom domains - template quality - collaboration ## Success criteria - Malformed model JSON produces an editable error with no partial saved deck. - Regenerating slide three leaves the other four unchanged. - The five-slide fixture prints to exactly five readable pages. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs.
BRIEF.md
# Build brief · Gamma The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a local AI-assisted slide-card editor with printable decks as a bounded replacement for Gamma. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - decks(id,title,theme_json) - slides(id,deck_id,position,layout,title,body_json,notes,revision) - generations(id,deck_id,slide_id,input_hash,model,status) - assets(id,deck_id,path,credit) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: A five-slide deck with title, bullets, two-column, quote and image layouts. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Gamma acceptance sample: Create synthetic sample data before implementation: A five-slide deck with title, bullets, two-column, quote and image layouts. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a local AI-assisted slide-card editor with printable decks. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start outline before generation until these checks pass. ### Phase 2 · Outline before generation Build: Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. - Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A plausible model fact is not verified evidence; supplied facts remain the source of truth. Done when: Malformed model JSON produces an editable error with no partial saved deck. Changing the outline order preserves each slide id. Do not build yet: Do not start slide revision until these checks pass. ### Phase 3 · Slide revision Build: Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. - Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Model-generated HTML must not execute inside the editor. Done when: Regenerating slide three leaves the other four unchanged. A stale regeneration cannot replace a newer manual edit. Do not build yet: Do not start readable export until these checks pass. ### Phase 4 · Readable export Build: Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. - Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. - Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. Done when: The five-slide fixture prints to exactly five readable pages. The HTML deck opens offline with all supplied assets. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Gamma replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - This is a local AI-assisted slide-card editor with printable decks; full Gamma feature parity, vendor hosting and support are not included. - polished editor: retain the paid product if this capability is essential; it is outside this bounded build. - responsive card model: retain the paid product if this capability is essential; it is outside this bounded build. - exports: retain the paid product if this capability is essential; it is outside this bounded build. - analytics: retain the paid product if this capability is essential; it is outside this bounded build. - custom domains: retain the paid product if this capability is essential; it is outside this bounded build. - template quality: retain the paid product if this capability is essential; it is outside this bounded build. - collaboration: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested.
ARCHITECTURE.md
# Architecture · Gamma ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Outline before generation | Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. | Keep the acceptance contract: Malformed model JSON produces an editable error with no partial saved deck. Replace only this module after replaying its fixture; preserve ids and existing records. | | Slide revision | Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. | Keep the acceptance contract: Regenerating slide three leaves the other four unchanged. Replace only this module after replaying its fixture; preserve ids and existing records. | | Readable export | Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. | Keep the acceptance contract: The five-slide fixture prints to exactly five readable pages. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. - `OLLAMA_URL` · required · Keep the inference service bound to loopback; the backend calls it, never the public browser. - `LOCAL_MODEL` · required · Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it.
AGENTS.md
# Agent instructions · Gamma product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - A plausible model fact is not verified evidence; supplied facts remain the source of truth. - Model-generated HTML must not execute inside the editor. - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
MILESTONES.md
# Delivery milestones · Gamma Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a local AI-assisted slide-card editor with printable decks, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: decks(id,title,theme_json); slides(id,deck_id,position,layout,title,body_json,notes,revision); generations(id,deck_id,slide_id,input_hash,model,status); assets(id,deck_id,path,credit). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: A five-slide deck with title, bullets, two-column, quote and image layouts. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Outline before generation Outline before generation for Gamma: Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. ### Steps 1. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Collect topic, audience, desired takeaway and supplied facts; ask the local model for a bounded outline and validate its JSON. Files: `features/outline_before_generation.py`, `templates/outline_before_generation.html` 2. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Let the user edit and approve the outline before generating individual slides with stable ids and one of five layouts. Files: `features/outline_before_generation.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Malformed model JSON produces an editable error with no partial saved deck. Then check: Changing the outline order preserves each slide id. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_outline_before_generation.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Changing the outline order preserves each slide id. ### Watch out - A plausible model fact is not verified evidence; supplied facts remain the source of truth. ## M3 · Slide revision Slide revision for Gamma: Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. ### Steps 1. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Render editable slide cards and notes with a shared theme; escape all model strings and allow only owned local images. Files: `features/slide_revision.py`, `templates/slide_revision.html` 2. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Regenerate one selected slide against its revision and show a diff before acceptance; preserve the rest of the deck. Files: `features/slide_revision.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: Regenerating slide three leaves the other four unchanged. Then check: A stale regeneration cannot replace a newer manual edit. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_slide_revision.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Regenerating slide three leaves the other four unchanged. - [ ] A stale regeneration cannot replace a newer manual edit. ### Watch out - Model-generated HTML must not execute inside the editor. ## M4 · Readable export Readable export for Gamma: Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. ### Steps 1. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Create standalone HTML with print page breaks, speaker notes in a separate export and CSS for the five layouts. Files: `features/readable_export.py`, `templates/readable_export.html` 2. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Provide browser Print to PDF instructions and check long headings and overflowing bullets at export size. Files: `features/readable_export.py` 3. Exercise the acceptance fixture Use A five-slide deck with title, bullets, two-column, quote and image layouts. Check: The five-slide fixture prints to exactly five readable pages. Then check: The HTML deck opens offline with all supplied assets. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_readable_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] The HTML deck opens offline with all supplied assets. ### Watch out - Editable PPTX, automatic image generation and hosted sharing are explicitly excluded from this first version. ## M5 · Portable delivery and clean-start proof Finish the Gamma replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Outline before generation; Slide revision; Readable export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a local AI-assisted slide-card editor with printable decks operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
OPERATIONS.md
# Operations · Gamma ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for gamma. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A five-slide deck with title, bullets, two-column, quote and image layouts. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Outline before generation, Slide revision, Readable export. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] Malformed model JSON produces an editable error with no partial saved deck. - [ ] Regenerating slide three leaves the other four unchanged. - [ ] The five-slide fixture prints to exactly five readable pages. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Gamma capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/gamma # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
$ choose a build depth, inspect the files, then open the complete pack in your agent
They pay because the output looks acceptable without wrestling with PowerPoint.
xpolished editor
xresponsive card model
xexports
xanalytics
xcustom domains
xtemplate quality
xcollaboration
share on X ↗"I just replaced Gamma ($9/mo) with one prompt"
Gamma pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | 400 starting AI credits with no monthly refresh; 10 slides/prompt; 50,000 input tokens; 2,000-credit balance cap; +200 credits/referral. |
| plus | — | $9/user | 1,000 credits/month; 75 slides/prompt; 100,000 input tokens. |
| pro | — | $18/user | 4,000 credits/month; 75 slides/prompt; up to 10 custom domains; API access. |
| ultra | custom | — | 20,000 credits/month; 75 slides/prompt; up to 100 custom domains. |
| team | — | $20/user | 6,000 credits/seat/month; 75 slides/prompt; up to 10 custom domains; 2-seat minimum. |
| business | — | $40/user | 10,000 credits/seat/month; up to 100 custom domains; 10-seat minimum. |
| enterprise | custom | — | Annual agreement; flexible team size and custom organization-wide credits. |
free tier400 one-time starting AI credits; no automatic refresh; 10 slides/prompt; 50,000 input tokens; balance capped at 2,000 credits; +200 credits per referral
billingPlus and Pro offer monthly + annual; annual is advertised as 28% cheaper; Ultra is monthly-only; Team and Business are annual-only; Enterprise uses an annual agreement
hidden costs1,500 extra credits cost $6; multi-user auto-recharge charges separately for each user who triggers it; credits are not pooled; unused paid credits expire after the subscription ends; Team requires 2 seats and Business 10
verified 2026-08-13 · source ↗
Vibecode Gamma
Kinda. The core of Gamma is buildable in a weekend with the prompt on this page, but there are real gaps: polished editor, responsive card model. Read the honest list above before committing.
How much does Gamma cost?
Gamma costs about $9/month (Plus, checked 2026-08-13), which is $108 per year.
What do I lose by replacing Gamma?
Honestly: polished editor; responsive card model; exports; analytics; custom domains; template quality; collaboration. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Gamma?
Yes: Slidev (Open-source Markdown/HTML slide deck generator; good foundation for a developer-oriented c). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.