Claude Code 提示词库

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

where do we validate uploaded file types?

what would break if I deleted the retryWithBackoff helper?

look through the commit history of internal/auth/session.go and summarize how it evolved and why

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

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

read @meeting-notes.md and write up the action items, then create a Linear ticket for each with acceptance criteria

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

find the public functions in src/auth/ without JSDoc comments and add them, matching the style already used in the file

add a /health endpoint that returns the app version and uptime

create a drag-and-drop Kanban board with three columns using HTML, CSS, and vanilla JavaScript, then open it in my browser

read issue #312, implement the fix, and run the tests

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

write tests for app/parsers/feed.py, run them, and fix any failures

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%

migrate everything from the old logging API to the structured logger: identify every place that needs to change, then make the changes

port this Python module to Rust, keeping the same public API and test behavior

optimize the search query to bring p95 latency from 2s down to under 500ms

the login button extends 20px beyond the card border on mobile. fix it.

review my uncommitted changes and flag anything that looks risky before I commit

review PR #247 and summarize what changed, then list any concerns

here is my Terraform plan output. what is this going to do, and is anything here going to cause problems?

use a subagent to review src/api/ for security issues and report what it finds

review launch-post.md for unsupported claims, missing attributions, and brand-guideline issues and list anything I should fix before it goes to legal

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

you keep using default exports when this project uses named exports. add a rule to CLAUDE.md so this stops happening

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

compare v2.3.0 to v2.4.0 and draft release notes grouped by feature, fix, and breaking change

write a GitHub Actions workflow that runs the tests and deploys to staging on every push to main

the UserAuth test is failing, find out why and fix it

users are seeing 500 errors on /api/settings. investigate and tell me what is going on

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

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

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

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

read @ads-performance.csv, find the underperforming headlines, and generate 20 new variations that stay under 90 characters

create a /ship skill for this project that runs the linter and tests, then drafts a commit message

write a hook that runs prettier after every edit to a .ts or .tsx file

set up the Sentry MCP server so you can read my error reports directly

summarize what we did this session and suggest what to add to CLAUDE.md