Use the latest project plan in Drive and relevant decisions and updates from
the project's Slack channel to prepare a status update.

Make the opening more direct, keep the evidence, and move the recommendation
above the background section.

Explain how compound interest works for someone who has never invested.
Use one concrete example and define any financial terms you introduce.

Draft a friendly email declining this invitation because I will be traveling.
Keep it under 120 words and leave the door open for a future event.

Compare these two phone plans for one person who travels internationally twice
a year. Show the important differences in a table, then recommend one and explain
the tradeoff.

Plan five weekday dinners that take less than 30 minutes. Avoid peanuts, reuse
ingredients across meals, and finish with one consolidated shopping list.

Use the attached quarterly reports to create a leadership brief and a six-slide
presentation.

The audience is the executive team. Lead with the three decisions they need to
make, distinguish reported facts from your analysis, cite each number to its
source file, and check that the brief and slides agree before you finish.

Research three customer-support platforms for a 50-person company. Compare
pricing, security, integrations, and migration effort using current sources.
Deliver a recommendation memo with links, assumptions, and the questions we
should answer before signing a contract.

Create a launch plan for the attached product brief. Include the timeline,
owners, dependencies, risks, announcement draft, customer FAQ, and a checklist
for launch day. Flag any missing decisions before producing the final files.

Explain how the request flows through the selected code.
Include:
- a short summary of the responsibilities of each module involved
- what data is validated and where
- one or two "gotchas" to watch for when changing this

(验证追问) Summarize the request flow as a numbered list of steps. Then list the files involved.

codex

I need to understand the protocol used by this service. Read @foo.ts @schema.ts and explain the schema and request/response flow. Focus on required vs optional fields and backward compatibility rules.

codex

Bug: Clicking "Save" on the settings screen sometimes shows "Saved" but doesn't persist the change.
Repro:
1) Start the app: npm run dev
2) Go to /settings
3) Toggle "Enable alerts"
4) Click Save
5) Refresh the page: the toggle resets
Constraints:
- Do not change the API shape.
- Keep the fix minimal and add a regression test if feasible.
Start by reproducing the bug locally, then propose a patch and run checks.

(验证追问) After the fix, run lint + the smallest relevant test suite. Report the commands and results.

Find the bug causing "Saved" to show without persisting changes. After proposing the fix, tell me how to verify it in the UI.

(IDE，选中函数代码后) Write a unit test for this function. Follow conventions used in other tests.

(CLI，直接点名函数) Add a test for the invert_list function in @transform.ts. Cover the happy path plus edge cases.

codex

(拖入截图后) Create a new dashboard based on this image.
Constraints:
- Use react, vite, and tailwind. Write the code in typescript.
- Match spacing, typography, and layout as closely as possible.
Outputs:
- A new route/page that renders the UI
- Any small components needed
- README.md with instructions to run it locally

(验证追问) Start the dev server and tell me the local URL/route to view the prototype.

(IDE版，贴截图) Create a new settings page. Use the attached screenshot as the target UI.
Follow design and visual patterns from other files in this project.

codex
npm run dev

第一轮：Propose 2-3 styling improvements for the landing page.

第二轮（选定方向后细化到具体元素）：Go with option 2.
Change only the header:
- make the typography more editorial
- increase whitespace
- ensure it still looks good on mobile

第三轮（继续收敛）：Next iteration: reduce visual noise.
Keep the layout, but simplify colors and remove any redundant borders.

本地规划：
$plan
We need to refactor the auth subsystem to:
- split responsibilities (token parsing vs session loading vs permissions)
- reduce circular imports
- improve testability
Constraints:
- No user-visible behavior changes
- Keep public APIs stable
- Include a step-by-step migration plan

修订计划：
Revise the plan to:
- specify exactly which files move in each milestone
- include a rollback strategy

切到云端环境后：
Implement Milestone 1 from the plan.

/review

(定向聚焦) /review Focus on edge cases and security issues

@codex review

(定向聚焦) @codex review for security vulnerabilities and security concerns

Update the "advanced features" documentation to provide authentication troubleshooting guidance. Verify that all links are valid.