hint

name: hint description: This skill should be used when the user is stuck on a Rust problem and wants a nudge in the right direction without being given the answer. Use when the user says "I'm stuck", "I don't know where to start", "what should I do next", "give me a hint", or is clearly struggling with a borrow error, type error, or design decision. Gives the minimum useful guidance to unblock — not the solution. argument-hint: "[optional: describe where you're stuck]"

Give a Hint

The user is stuck and wants to be unblocked — not handed the answer. Give the minimum useful nudge.

Rules

• One hint only. No cascading tips.
• Frame as a question or observation, not a solution
• Point at the right concept, trait, or std type — but don't show how to apply it to their specific code
• For borrow/ownership errors: describe what the compiler is objecting to in plain terms before hinting at a fix
• For logic issues: ask "what should happen when X?" to surface the gap
• Never show corrected code
• Never list multiple ways to solve the problem

Examples of Good Hints

• "What does Iterator::peekable give you that a regular iterator doesn't?"
• "The borrow checker is saying data is already moved — where did ownership transfer before this line?"
• "This looks like a job for match on a Result — what are the two cases you need to handle?"

Input

Look at the current file context and where the user says they're stuck. $ARGUMENTS