give me an overview of this codebase: architecture, key directories, and how the pieces connect给我概述一下这个代码库：架构、关键目录，以及各部分如何连接explain what src/scheduler/queue.ts does and how data flows through it. write it up as an HTML page with a diagram, then open it in my browser解释 src/scheduler/queue.ts 的作用以及数据如何流经它。以 包含图表的 HTML 页面，然后在浏览器中打开 形式输出where do we validate uploaded file types?我们在哪里 验证上传的文件类型？what would break if I deleted the retryWithBackoff helper?如果我删除 retryWithBackoff 辅助函数，哪些地方会出问题？look through the commit history of internal/auth/session.go and summarize how it evolved and why查看 internal/auth/session.go 的提交历史，总结其演变过程及原因which files would I need to touch to add a dark mode toggle to settings?我需要修改哪些文件才能 在设置中添加深色模式开关？I am a PM. walk me through what happens when a user clicks Export to PDF, from the UI down to the result我是一名 产品经理。请带我走查一下，当用户 点击导出为 PDF 时，从 UI 到结果的全过程是怎样的plan how to refactor the payment module to support multiple currencies. list the files you would change, but don't edit anything yet规划如何重构 支付模块 以实现 支持多种货币。列出要修改的文件，但暂时不要编辑任何内容I want to build per-workspace rate limits. interview me about implementation, UX, edge cases, and tradeoffs until we have covered everything, then write the spec to SPEC.md我想构建 每个工作区的速率限制。请就实现、UX、边缘情况和权衡对我进行访谈，直到我们覆盖所有内容，然后将规范写入 SPEC.mdread @meeting-notes.md and write up the action items, then create a Linear ticket for each with acceptance criteria阅读 @meeting-notes.md 并撰写行动项，然后为每个行动项创建一个 Linear 工单，并附上验收标准list the error states, empty states, and edge cases for the file upload flow that the design needs to cover列出 文件上传流程 需要覆盖的错误状态、空状态和边界情况here is a mockup. build a working prototype I can click through, matching the layout and states shown这是一个模型。构建一个我可以点击交互的可运行原型，匹配所示的布局和状态implement this design, then take a screenshot of the result, compare it to the original, and fix any differences实现此设计，然后截取结果截图，将其与原图对比，并修复任何差异look at how the GitHub webhook handler is implemented to understand the pattern, then build a Stripe webhook handler the same way查看 GitHub webhook 处理器 是如何实现的以理解其模式，然后以相同的方式构建 一个 Stripe webhook 处理器find the public functions in src/auth/ without JSDoc comments and add them, matching the style already used in the file查找 src/auth/ 中的公共函数 中缺少 JSDoc 注释的代码，并添加注释，匹配文件中已使用的风格add a /health endpoint that returns the app version and uptime添加一个返回 应用版本和正常运行时长 的 /health 端点create a drag-and-drop Kanban board with three columns using HTML, CSS, and vanilla JavaScript, then open it in my browser使用 HTML、CSS 和原生 JavaScript 创建一个 带有三列的拖放式看板，然后在浏览器中打开它read issue #312, implement the fix, and run the tests阅读 issue #312，实现修复，并运行测试find every place we say "Sign up free" or a close variant, show me each one in context, then update them all to "Start free trial". leave tests and the changelog alone找出所有说“免费注册”或相似措辞的地方，在上下文中显示每个，然后把它们全部更新为“开始免费试用”。测试和变更日志不要动read the privacy impact assessments in legal/pia/ to learn the structure and voice, then draft a new one for the new analytics integration阅读 legal/pia/ 里的 隐私影响评估 来学习结构和语调，然后为 新的分析集成 起草一份新的write tests for app/parsers/feed.py, run them, and fix any failures为 app/parsers/feed.py 编写测试，运行它们，并修复任何失败write tests for the password reset flow first, then implement it until they pass先为 密码重置流程 编写测试，然后实现它直到测试通过read coverage/coverage-summary.json and add tests for the lowest-covered files until each is above 80%读取 coverage/coverage-summary.json，为覆盖率最低的文件添加测试，直至每个文件高于 80%migrate everything from the old logging API to the structured logger: identify every place that needs to change, then make the changes把所有从 旧的日志 API 迁移到 结构化日志记录器：先找出每一处需要变更的地方，然后做出变更port this Python module to Rust, keeping the same public API and test behavior将 这个 Python 模块 移植到 Rust，保持相同的 公共 API 和测试行为optimize the search query to bring p95 latency from 2s down to under 500ms优化 搜索查询，让 p95 延迟 从 2秒 降至 500毫秒 以下the login button extends 20px beyond the card border on mobile. fix it.登录按钮 在 移动端 上超出了 卡片边框 20px，修复它。review my uncommitted changes and flag anything that looks risky before I commit在提交前，检查我未提交的更改，并将任何看起来有风险的地方标记出来review PR #247 and summarize what changed, then list any concerns审查 PR #247，总结变更内容，然后列出所有问题here is my Terraform plan output. what is this going to do, and is anything here going to cause problems?这是我的 Terraform plan 输出。这将会执行什么操作？其中是否存在会导致问题的内容？use a subagent to review src/api/ for security issues and report what it finds使用一个子代理审查 src/api/ 中的安全问题，并报告发现的问题review launch-post.md for unsupported claims, missing attributions, and brand-guideline issues and list anything I should fix before it goes to legal审查 launch-post.md 中是否存在 无根据的声明、缺失的署名以及品牌指南问题，并列出在发送给 法务 之前我应该修复的所有内容that is not right: the function signature needs to stay backward-compatible. try a different approach那不正确：函数签名需要保持向后兼容。尝试一种不同的方法that is too much. keep only the changes to the validation logic in src/forms/ and undo your other edits这范围太大了。仅保留对 src/forms/ 中的校验逻辑 所做的更改，并撤销你的其他编辑you keep using default exports when this project uses named exports. add a rule to CLAUDE.md so this stops happening你总是 在本项目使用命名导出时却使用了默认导出。在 CLAUDE.md 中添加一条规则，以避免这种情况再次发生resolve the merge conflicts in this branch and explain what you kept from each side解决此分支中的合并冲突，并说明你保留了各方的哪些内容commit these changes with a message that summarizes what I did提交这些更改，并用一条概括我所做操作的信息作为提交信息find the Linear ticket about the login timeout and open a PR that implements it找到关于 登录超时 的 Linear 工单，并打开一个实现它的 PRcompare v2.3.0 to v2.4.0 and draft release notes grouped by feature, fix, and breaking change比较 v2.3.0 到 v2.4.0，并起草按功能、修复和破坏性更改分组的发布说明write a GitHub Actions workflow that runs the tests and deploys to staging on every push to main编写一个 GitHub Actions 工作流，在每次推送到 main 时 运行测试并部署到预发布环境the UserAuth test is failing, find out why and fix itUserAuth 测试失败了，找出原因并修复它users are seeing 500 errors on /api/settings. investigate and tell me what is going on用户在 /api/settings 上看到了 500 错误。请调查并告诉我发生了什么here is a build error. fix the root cause and verify the build succeeds这里有一个构建错误。修复根本原因并验证构建成功the checkout endpoint started returning 500s an hour ago. check the logs, recent deploys, and config changes, then tell me the most likely cause结账端点一小时前开始返回 500 错误。检查日志、最近的部署和配置更改，然后告诉我最可能的原因here is a screenshot of the GCP Kubernetes dashboard. walk me through why this pod is failing and give me the exact commands to fix it这是 GCP Kubernetes 仪表板 的截图。请带我了解为什么 这个 Pod 失败，并给我修复它的确切命令show me all failed logins for the auth service over the past 24 hours. write the query, run it, and tell me what stands out显示 失败的登录尝试 在 auth 服务 上的所有记录，时间范围为 过去 24 小时。写出查询语句，运行它，然后告诉我有什么突出之处read @reports/q1-signups.csv, summarize the key patterns, and write the results to an HTML page with charts, then open it in my browser读取 @reports/q1-signups.csv，总结关键模式，并将结果写入 一个带图表的 HTML 页面，然后在浏览器中打开它read @ads-performance.csv, find the underperforming headlines, and generate 20 new variations that stay under 90 characters读取 @ads-performance.csv，找出表现不佳的 标题，并生成 20 个新的变体，每个不超过 90 个字符create a /ship skill for this project that runs the linter and tests, then drafts a commit message为此项目创建一个 /ship 技能，该技能会 运行 linter 和测试，然后草拟提交信息write a hook that runs prettier after every edit to a .ts or .tsx file编写一个钩子，在每次 编辑 .ts 或 .tsx 文件 后 运行 prettierset up the Sentry MCP server so you can read my error reports directly设置 Sentry MCP 服务器，以便你直接读取我的 错误报告summarize what we did this session and suggest what to add to CLAUDE.md总结我们这次会话做了什么，并建议将哪些内容添加到 CLAUDE.md 中