# Byte-compiled / optimized / DLL files
__pycache__/
*.py[codz]
*$py.class

# C extensions
*.so
  
# Distribution / packaging
.Python
build/
data/*
!data/english_words.txt
develop-eggs/
dist/
downloads/
eggs/
.eggs/
!/vendor/
!/vendor/mcp-playwright-shim/
!/vendor/mcp-playwright-shim/dist/
!/vendor/mcp-playwright-shim/dist/index.js
lib/
!frontend/lib/
!frontend/lib/**
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST

# PyInstaller
#  Usually these files are written by a python script from a template
#  before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec

# Installer logs
pip-log.txt
pip-delete-this-directory.txt

# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py.cover
.hypothesis/
.pytest_cache/
cover/

# Translations
*.mo
*.pot

# Django stuff:
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal

# Flask stuff:
instance/
.webassets-cache

# Scrapy stuff:
.scrapy

# Sphinx documentation
docs/_build/

# PyBuilder
.pybuilder/
target/

# Jupyter Notebook
.ipynb_checkpoints

# IPython
profile_default/
ipython_config.py

# pyenv
#   For a library or package, you might want to ignore these files since the code is
#   intended to run in multiple environments; otherwise, check them in:
# .python-version

# pipenv
#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
#   However, in case of collaboration, if having platform-specific dependencies or dependencies
#   having no cross-platform support, pipenv may install dependencies that don't work, or not
#   install all needed dependencies.
#Pipfile.lock

# UV
#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
#   This is especially recommended for binary packages to ensure reproducibility, and is more
#   commonly ignored for libraries.
#uv.lock

# poetry
#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
#   This is especially recommended for binary packages to ensure reproducibility, and is more
#   commonly ignored for libraries.
#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
#poetry.lock
#poetry.toml

# pdm
#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
#pdm.lock
#pdm.toml
.pdm-python
.pdm-build/

# pixi
#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
#pixi.lock
#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
#   in the .venv directory. It is recommended not to include this directory in version control.
.pixi

# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
__pypackages__/

# Celery stuff
celerybeat-schedule
celerybeat.pid

# SageMath parsed files
*.sage.py

# Environments
.env
.envrc
.venv
env/
venv/
ENV/
env.bak/
venv.bak/

# Spyder project settings
.spyderproject
.spyproject

# Rope project settings
.ropeproject

# mkdocs documentation
/site

# mypy
.mypy_cache/
.dmypy.json
dmypy.json

# Pyre type checker
.pyre/

# pytype static type analyzer
.pytype/

# Cython debug symbols
cython_debug/

# PyCharm
#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
#  and can be added to the global gitignore or merged into this file.  For a more nuclear
#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
#.idea/

# Abstra
# Abstra is an AI-powered process automation framework.
# Ignore directories containing user credentials, local state, and settings.
# Learn more at https://abstra.io/docs
.abstra/

# Visual Studio Code
#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
#  you could uncomment the following to ignore the entire vscode folder
# .vscode/

# Ruff stuff:
.ruff_cache/

# PyPI configuration file
.pypirc

# Google OAuth client secret files (never commit credentials)
*client_secret*.apps.googleusercontent.com.json
*client_secret*.json

# Cursor
#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
#  refer to https://docs.cursor.com/context/ignore-files
.cursorignore
.cursorindexingignore

# Marimo
marimo/_static/
marimo/_lsp/
__marimo__/
.vercel

# Temporary files and large assets
temp/
.env*.local

# HubSpot config file
hubspot.config.yml

# HubSpot downloaded project files
hubspot-dev-projects/

# Supabase CLI local state. config.toml is the exception — it is the port map for
# the local stack (`supabase start`), holds no secrets, and has to be shared or
# everyone picks different ports and local_settings.example.py stops being true.
supabase/*
!supabase/config.toml

# Claude Code scheduled task lock files
.claude/*.lock

# Claude Code worktrees live here (`EnterWorktree`, or `git worktree add
# .claude/worktrees/<name>`). Each one is a full checkout nested inside this
# repo, so it must stay untracked. .dockerignore and .vercelignore already drop
# `.claude`, which keeps the DO image and Vercel uploads clear of them.
.claude/worktrees/

# Flask session-signing key files (auto-generated by app.py at startup)
frontend/.secret_key

# Chrome Web Store submission zips (contents are already tracked)
chrome-extension/distribution/

# clerk configuration (can include secrets)
/.clerk/

# dev:up — this checkout's pidfile and server logs
/.dev/

archived.hubspot.config.yml
hubspot.config.yml

# --- YouSpot workspace (bun: apps/youspot-studio, packages/, plugins/, scripts/) ---
# No trailing slash: a `node_modules` symlink is not a directory to git, so
# `node_modules/` would let one slip through and get committed.
node_modules
.next/
.turbo/
out/
*.tsbuildinfo
next-env.d.ts
# Review artifacts from `bun run --cwd apps/youspot-studio shoot:flows`.
apps/youspot-studio/screens/
.env.*
!.env.example

# Python rules above (lib/, dist/, build/) must not swallow workspace sources.
!apps/youspot-studio/**/lib/
!apps/youspot-studio/**/lib/**
!packages/**/lib/
!packages/**/lib/**
!scripts/**/lib/
!scripts/**/lib/**

# plugins/ is a published artifact, not build output; a plugin that ships a
# built MCP server keeps its dist/ tracked or the installed plugin cannot start.
!plugins/**/dist/
!plugins/**/dist/**

# team/<handle>/scratch/ is each person's private drafting space. PROFILE.md next
# to it is committed on purpose — the shared half is context, this half is not.
team/*/scratch/
# Agent skills installed by `skills add`. skills-lock.json is committed and
# these are not, for the same reason package.json is committed and
# node_modules is not: the lockfile says what to install, the install is a
# local artifact.
#
# Both entries have to go together. .claude/skills/trees is a symlink into
# .agents, so ignoring only one of them leaves a symlink pointing at nothing
# for anyone who clones — a dangling symlink in this repo has already broken
# an install once. No trailing slash on the symlink: a trailing slash matches
# directories only, and it would slip through.
.agents/
.claude/skills/trees

.DS_Store
frontend/.yarnrc.yml
frontend/yarn.lock
poetry.lock
uv.lock

# Slack CLI project state: app ids per workspace and local dev apps
slack/.slack/apps.json
slack/.slack/apps.dev.json
slack/.slack/cache/
