Skip to main content

𝘼𝙠𝙚𝙣 𝘾𝙝𝙖𝙣𝙣𝙚𝙡

  1. 选择太多会导致焦虑,从而无法专注做一件事情
  2. 这段时间对于 AI 的使用下来,对于创造性的内容,AI 还是缺乏主观能动性,还是需要人类监督,花时间去调研一个领域,然后用一些手段告诉 AI(包括提示词,文档,skill 等等),他们够很好的在此基础上去发挥,也就是现在的 AI,更加适合去复刻,模仿,也就是这段时间我对于 AI 的定位改变:从一个万能的老师,变成了一个学习秒懂的学生。
  3. # Global Codex Cost-Saving Rules
    
    These instructions apply across Codex workspaces unless a project-level `AGENTS.md` gives more specific guidance.
    
    ## Command Execution
    
    - Prefer the smallest useful command before broad inspection.
    - Keep exploration scoped to the user's current goal.
    - Do not read large logs, full dependency trees, or full files unless necessary.
    - When command output is long, inspect only the relevant tail or error section.
    - Avoid repeated status checks unless the previous result is ambiguous.
    - Do not fix unrelated issues unless the user explicitly asks.
    
    ## GitHub And Git
    
    - Before committing, use minimal checks:
      - `git status --short`
      - targeted diff for files being committed
      - build or test only when requested or necessary
    - Avoid broad history inspection unless the task depends on history.
    - Do not inspect CI, create PRs, or check deployments unless requested.
    - If a push fails, inspect the shortest useful error output first.
    - Summarize Git state in chat instead of dumping full command output.
    
    ## Vercel
    
    - Do not deploy unless deployment is explicitly requested.
    - Prefer local build validation before remote Vercel checks.
    - When inspecting deployments, read only the final status and relevant error lines.
    - Avoid repeated polling of deployment status unless monitoring is requested.
    
    ## NPM And Builds
    
    - On Windows, prefer `cmd /c npm.cmd ...` if PowerShell blocks `npm`.
    - Avoid reinstalling dependencies if `node_modules` already exists and the task does not require dependency changes.
    - For build failures, inspect the first actionable error and final summary instead of full logs.
    
    ## Communication
    
    - Before expensive or networked operations, state the intended command group.
    - Ask before full CI inspection, production deploys, repeated remote checks, or broad repo scans.
    - When skipping an expensive check, say exactly what was skipped and why. 


    让AI省TOKEN