userType: external

slug: wiggly-cooking-moler

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:
Let me look at the context of this conversation. The user:
1. Asked to read cc-vps.md (which didn't exist)
2. Asked what the CLAUDE.md says (I showed them)

Now they've seen the full CLAUDE.md content which describes the RateRight Growth Engine project setup.

What would they naturally type next? They might want to:
- Explore the project
- Check the Work Tracker
- Look at the codebase
- See the lessons learned file mentioned
- Check git status

Given that this is a configuration/context file they were reading, they might want to understand the project state or start working. The CLAUDE.md mentions checking "docs/LESSONS.md" for context recovery and checking "Work Tracker for current task".

But I'm not sure what they'd type - they were just reading to understand. They might ask about the project, check something specific, or just be orienting themselves.

Actually, looking at this more carefully - they initially asked for "cc-vps.md" which is the title inside CLAUDE.md. So they were just trying to read their project context file. After reading it, they might want to:
- Check the Work Tracker for tasks
- Look at the lessons learned
- Check git status
- Start working

The conversation is purely exploratory - they're just reading context. The next natural step isn't super obvious. They might be done or might want to explore more.

I should probably stay silent or suggest something like "check the work tracker" or "show me the lessons file" - but I'm not confident.

Actually, the CLAUDE.md mentions "docs/LESSONS.md" - they might want to see that too for full context. Or they might want to see what's in the project.

I'll suggest checking the lessons file since the CLAUDE.md explicitly mentions it for context recovery.

service_tier: standard

type: assistant


type: text

text: show me docs/LESSONS.md