上傳整個 repo / 主要檔案、Gemini 給新人在 1 小時內理解 codebase 的 reading order
You are a senior engineer giving a new hire their first day onboard. I've uploaded the codebase. The new engineer has {{experience}} experience.
Produce a 1-hour reading plan:
## Stage 1: The 30,000-ft view (10 min)
Which 1-2 files give the "what does this project do" answer fastest? Why those?
## Stage 2: The data model (15 min)
Which files define the schema / types / domain model? What's the central object?
## Stage 3: The request lifecycle (20 min)
Follow one typical request from entry point to response. List files in order with 1-sentence "this is where X happens" annotation.
## Stage 4: Where the action is (15 min)
What 2-3 files contain the most domain-specific business logic that other engineers will mostly modify? Why those?
## Things to skip on day 1
3-5 folders that look intimidating but are auto-generated / vendor / tests / migrations — say "don't worry about these yet, come back week 2".
For every file mentioned: give the relative path, 1-sentence what it does, and "look for X" hint.把方括號 [ ] 內的變數換成你的內容,丟進 Gemini 2.5 Pro。
不用離開網站,直接看這組 prompt 跑出來長怎樣(AI 即時生成,扣 1 點)。
New hire onboard 是 engineering manager 永遠的痛。Gemini 能讀整個 repo 給出讀檔順序、比看 README 快 10 倍。
4 stage 讀檔計畫、每檔有「look for X」hint、加「不要看這些」防嚇跑
以上為此 Prompt 丟進 Gemini 2.5 Pro 後可得到的描述性成果,實際畫面會因填入的變數而有差異。
[tech_stack]技術棧(如:Next.js + TypeScript + Postgres / Django + Celery / Rails + Sidekiq)
[experience]年資(5+ years Python but new to TS / fresh grad / mid-level full-stack)
填下面的欄位,上方 prompt 會即時替換 [方括號] 內容。填好後按「複製組好的 prompt」直接丟進工具。
You are a senior engineer giving a new hire their first day onboard. I've uploaded the codebase. The new engineer has {{experience}} experience.
Produce a 1-hour reading plan:
## Stage 1: The 30,000-ft view (10 min)
Which 1-2 files give the "what does this project do" answer fastest? Why those?
## Stage 2: The data model (15 min)
Which files define the schema / types / domain model? What's the central object?
## Stage 3: The request lifecycle (20 min)
Follow one typical request from entry point to response. List files in order with 1-sentence "this is where X happens" annotation.
## Stage 4: Where the action is (15 min)
What 2-3 files contain the most domain-specific business logic that other engineers will mostly modify? Why those?
## Things to skip on day 1
3-5 folders that look intimidating but are auto-generated / vendor / tests / migrations — say "don't worry about these yet, come back week 2".
For every file mentioned: give the relative path, 1-sentence what it does, and "look for X" hint.這組 prompt 專為 Gemini 2.5 Pro 設計。把 prompt 內 2 個方括號 [變數] 換成你自己的內容,貼進 Gemini 2.5 Pro 執行即可。難度中等,照變數說明填好後即可上手。
完整 prompt 免費開放閱讀,不用註冊;登入後可一鍵複製、收藏與留言。
prompt 文字本身你可自由使用與修改。但 AI 生成物(圖/音樂/影片/文字)的商用授權,取決於你在 Gemini 2.5 Pro 使用的方案與其官方服務條款,請以該工具的授權規範為準。
Studio engineer 視角拆解 Suno 致命弱點(油炸 vocals、高頻 artifact)+ 4 步驟 DAW workflow + Suno Studio 修音 prompt
提案產生器 / 會議處理器 / 內容再利用 / 週五回顧 / 收工 reset — 試了 40 個只有這 5 個沒被丟掉、各省 30+ 分鐘 / 次。
適合:部落格、Medium、Notion 公開頁、Substack — 任何支援 iframe / HTML 嵌入的地方。對方點「看完整」會回到本站、是 prompt 庫的免費 backlink。
<iframe src="https://prompt.luvai.net/embed/gemini-codebase-onboard" width="100%" height="380" frameborder="0" style="border:1px solid #e0dcd0;border-radius:4px;" loading="lazy" title="PromptCraft Embed"></iframe>
六個月在 Claude / GPT-4 / Gemini 上用人工 rater A/B 測 200+ prompt 後寫的。包含 persona+constraint stacking / anti-example / role reversal QA / cognitive scaffold / emotional priming / uncertainty CoT / steelman first。
一年的 role-play system prompt + 14-step framework 後總結:真正改變品質的是 5 個單行 prompt。沒有 role、沒有 markdown、沒有「you are an expert」。