gitignorelisted

# .gitignore Builder Understand the codebase **first**, then write a correct, well-organized `.gitignore`. Do not paste a generic template blindly — base every entry on something actually present in this repo. ## Step 1 — Understand the codebase Inspect the repo to learn what it's made of. Look for: - **Languages & package managers:** `package.json` (Node), `requirements.txt` / `pyproject.toml` / `Pipfile` (Python), `go.mod` (Go), `Cargo.toml` (Rust), `pom.xml` / `build.gradle` (Java/Kotlin), `Gemfile` (Ruby), `composer.json` (PHP), `*.csproj` / `*.sln` (.NET), etc. - **Frameworks & build tools:** React/Next/Vue/Vite, Django/Flask, Rails, Spring, webpack/rollup, etc. — each has signature output dirs. - **Generated / dependency dirs already on disk:** `node_modules/`, `dist/`, `build/`, `.next/`, `target/`, `__pycache__/`, `venv/`, `.venv/`, `vendor/`, coverage output, compiled binaries. - **Secrets & local config:** `.env`, `.env.*`, `*.pem`, `*.key`, credential files, local DB files (`*.sqlite`, `*.db`). - **Editor / OS noise:** `.vscode/`, `.idea/`, `.DS_Store`, `Thumbs.db`, `*.swp`. - **Logs / caches / temp:** `*.log`, `.cache/`, `tmp/`, `coverage/`. Also: - **Read the existing `.gitignore`** (if any) so you don't add duplicates and you respect its structure/comments. - Run `git status --porcelain` and `git ls-files` to see what's actually tracked vs untracked — this reveals junk that's currently committed (e.g. a checked-in `node_modules/` or `.en