userType: external

gitBranch: main

slug: modular-singing-mitten

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 user's recent messages:
1. "show me dev.md in note pad"
2. "show me in terminal"
3. "can you show me claude.md?"

The user has been exploring the documentation files for this project. They wanted to see DEV.md, then CLAUDE.md. These are the main instruction files.

Looking at CLAUDE.md, it references other files:
- docs/LESSONS.md
- docs/SYSTEM-INTEL.md
- COO.md
- DEV.md (already shown)

The user seems to be exploring the documentation structure. They might want to see another related file like COO.md, LESSONS.md, or SYSTEM-INTEL.md.

However, I should consider - what would the USER naturally type next? They're just exploring files. The most logical next files to look at would be:
- COO.md (the other role's details)
- docs/LESSONS.md (mentioned as important)

But actually, the user might just be getting familiar with the system. They could also be done exploring.

Given the pattern of "show me X" followed by "show me Y", they might naturally want to see another file. The CLAUDE.md mentions docs/LESSONS.md as "where gotchas live" and it's mentioned in both protocols.

Most natural next request would probably be to see another doc file. "show me lessons.md" or "show me COO.md" seem likely.

Actually, the suggestion should match their style - they've been casual: "show me claude.md?" with lowercase, question mark optional.

I think "show me lessons.md" or "show me coo.md" would be natural follow-ups. LESSONS.md is mentioned as important to read first, so that might be most relevant.

Or they could be done exploring. Let me not suggest anything if it's not obvious.

Actually, they were exploring the project documentation. The LESSONS.md is explicitly mentioned as something to "read first" for both roles. That seems like a natural next step.

service_tier: standard

type: assistant


type: text

text: show me lessons.md