give me an overview of this codebase: architecture, key directories, and how the pieces connect

explain what {path} does and how data flows through it. write it up as {format}

where do we {behavior}?

what would break if I deleted {target}?

look through the commit history of {path} and summarize how it evolved and why

which files would I need to touch to {change}?

I am a {role}. walk me through what happens when a user {action}, from the UI down to the result

plan how to refactor the {target} to {goal}. list the files you would change, but don't edit anything yet

I want to build {feature}. interview me about implementation, UX, edge cases, and tradeoffs until we have covered everything, then write the spec to SPEC.md

read {input} and write up the action items, then create a {tracker} ticket for each with acceptance criteria

list the error states, empty states, and edge cases for {feature} 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 {example} is implemented to understand the pattern, then build {new} the same way

find {scope} without {format} comments and add them, matching the style already used in the file

add a {endpoint} endpoint that returns {payload}

create a {tool} using HTML, CSS, and vanilla JavaScript, then open it in my browser

read issue #{issue}, implement the fix, and run the tests

find every place we say "{copy}" or a close variant, show me each one in context, then update them all to "{new}". leave tests and the changelog alone

read the {examples} in {folder} to learn the structure and voice, then draft a new one for {topic}

write tests for {path}, run them, and fix any failures

write tests for {feature} first, then implement it until they pass

read {report} and add tests for the lowest-covered files until each is above {target}%

migrate everything from {from} to {to}: identify every place that needs to change, then make the changes

port {source} to {target}, keeping the same {keep}

optimize {target} to bring {metric} from {current} down to under {goal}

the {element} extends {amount} beyond the {container} on {viewport}. fix it.

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

review PR #{pr} 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 {path} for security issues and report what it finds

that is not right: {feedback}. try a different approach

that is too much. keep only the changes to {scope} and undo your other edits

you keep {mistake}. 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 {tracker} ticket about {topic} and open a PR that implements it

compare {from} to {to} and draft release notes grouped by feature, fix, and breaking change

write a GitHub Actions workflow that {steps} on every push to {branch}

the {test} test is failing, find out why and fix it

users are seeing {symptom} on {where}. investigate and tell me what is going on

here is a build error. fix the root cause and verify the build succeeds

{symptom}. check the logs, recent deploys, and config changes, then tell me the most likely cause

here is a screenshot of {console}. walk me through why {resource} is failing and give me the exact commands to fix it

show me all {events} for {scope} over {timeframe}. write the query, run it, and tell me what stands out

read {file}, summarize the key patterns, and write the results to {output}

read {file}, find the underperforming {items}, and generate {n} new variations that stay under {limit} characters

create a /{name} skill for this project that {steps}

write a hook that {action} after every {event}

set up the {server} MCP server so you can read my {data} directly

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

add rate limiting to the public API and make sure existing tests still pass

write the migration, run it against the dev database, and confirm the schema matches

add a settings page that follows the same layout as the profile page

get the bundle size under 200KB and show me what you removed

why is the build failing? @build.log

explain how the payment retry logic works as an HTML page with a diagram, then open it in my browser