userType: external

gitBranch: main

slug: imperative-plotting-planet

type: user

role: user

content:
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]

FIRST: Look at the user's recent messages and original request.

Your job is to predict what THEY would type - not what you think they should do.

THE TEST: Would they think "I was just about to type that"?

EXAMPLES:
User asked "fix the bug and run tests", bug is fixed → "run the tests"
After code written → "try it out"
Claude offers options → suggest the one the user would likely pick, based on conversation
Claude asks to continue → "yes" or "go ahead"
Task complete, obvious follow-up → "commit this" or "push it"
After error or misunderstanding → silence (let them assess/correct)

Be specific: "run the tests" beats "continue".

NEVER SUGGEST:
- Evaluative ("looks good", "thanks")
- Questions ("what about...?")
- Claude-voice ("Let me...", "I'll...", "Here's...")
- New ideas they didn't ask about
- Multiple sentences

Stay silent if the next step isn't obvious from what the user said.

Format: 2-8 words, match the user's style. Or nothing.

Reply with ONLY the suggestion, no quotes or explanation.


type: message

role: assistant

type: thinking

thinking:
Looking at the conversation:
1. User said "its not back" - referring to some service being down
2. I started the phone AI server
3. User clarified the cheatsheet was for me
4. I asked if anything else was down or if they're good to go

The user might:
- Confirm they're good to go
- Ask about something else
- Move on to actual work

Given they just clarified the cheatsheet and the service is now running, they might just confirm things are good or move on to actual development work. But it's not obvious what they'd type next - they might have a specific task in mind or might just be checking that things are working.

Actually, the most natural response might be "good to go" or "we're good" to confirm nothing else is needed. Or they might have a task they want to work on.

Let me think about their style - they're brief and informal ("its not back", "oh thats your cheat sheet").

The next step isn't super obvious. They might say "good" or they might have a task. I'll suggest a brief confirmation since that matches the flow.

service_tier: standard

type: assistant


type: text

text: good to go