diff --git a/.gitignore b/.gitignore
index 7b8da95..2e38ac9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,42 +1,65 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+```
+# Compiled and build artifacts
+*.pyc
+__pycache__/
+*.o
+*.obj
+dist/
+build/
+target/
 
-# dependencies
-/node_modules
-/.pnp
-.pnp.*
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/versions
+# Dependencies
+.venv/
+venv/
+node_modules/
+.mypy_cache/
+.pytest_cache/
+.gradle/
 
-# testing
-/coverage
+# Logs and temp files
+*.log
+*.tmp
+*.swp
 
-# next.js
-/.next/
-/out/
+# Environment
+.env
+.env.local
+*.env.*
 
-# production
-/build
+# Editors
+.vscode/
+.idea/
 
-# misc
+# System files
 .DS_Store
-*.pem
+Thumbs.db
 
-# debug
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-.pnpm-debug.log*
+# Coverage
+coverage/
+htmlcov/
+.coverage
 
-# env files (can opt-in for committing if needed)
-.env*
-!.env.example
-
-# vercel
-.vercel
-
-# typescript
-*.tsbuildinfo
-next-env.d.ts
+# Compressed files
+*.zip
+*.gz
+*.tar
+*.tgz
+*.bz2
+*.xz
+*.7z
+*.rar
+*.zst
+*.lz4
+*.lzh
+*.cab
+*.arj
+*.rpm
+*.deb
+*.Z
+*.lz
+*.lzo
+*.tar.gz
+*.tar.bz2
+*.tar.xz
+*.tar.zst
+*.tar.zst
\ No newline at end of file
diff --git a/lib/system-prompt.ts b/lib/system-prompt.ts
index d8b2a81..07dddf4 100644
--- a/lib/system-prompt.ts
+++ b/lib/system-prompt.ts
@@ -13,8 +13,9 @@ You are given **repository metadata**, a **root file tree** (depth 1), and the *
 - **Plain language.** Sounds like a real request ("Build me…", "I want…"), not an architecture doc.
 - **Outcome focused.** Describe what the app or library should *do* for a user using words a normal person would use.
 - **Honest scope.** Only claim features or stacks you infer from the README and tree you received. If the README was missing, empty, or uninformative, say so implicitly by keeping claims vague or limited to what the metadata suggests.
-- **Length:** about **120 to 200 words**, usually one short paragraph or a few tight sentences. Not a bullet list of file paths or dependencies.
+- **Length:** about **300 to 500 words**, allowing for more detail and context. Can be one substantial paragraph or several well-structured paragraphs. Not a bullet list of file paths or dependencies.
 - **Tone:** natural and conversational. Use contractions when they fit. No preamble ("Sure, here is…"), no meta ("As an AI…"), no filler.
+- **Depth:** Include relevant context about the project's purpose, key features, and expected behavior. Feel free to elaborate on user flows, important components, or integration points when the repository context supports it.
 
 ## What to avoid