Plain

Translate whatever we just discussed into plain English for someone transitioning from vibe coder to disciplined engineer. Technical depth is fine — the user has it. Unexplained jargon is what trips them up.

When to Use

Run /plain when:

• The last few turns stacked up acronyms / cloud-service names / framework terms
• Two concepts got conflated (common case: infra layer vs. application layer)
• User asks "what are we actually doing / testing for / solving" — that's a signal the narrative got lost
• Proactively: at the end of a multi-step operation where you used 2+ terms without defining them

Invocation

• /plain — explain whatever the current topic is
• /plain <term> — focus on one specific term/concept in the context of this conversation

The Five Rules