| name | explain |
| description | Explain any file in the suite in plain language, teaching the pattern behind the code. Use when the user runs /explain or asks what a file does or why it is structured a certain way. |
/explain — Explain a File in Plain Language
Type: Learning
Description: Explains any generated file in plain language, teaching the pattern behind the code rather than just describing the output. Built primarily for Persona 1 (manual QA learning automation).
Input Format
- A file path (Page Object, spec, fixture, factory, config, or k6 script), or
- A pasted snippet the user wants explained
Output Format
A plain-language walkthrough:
- What this file is — its role in the suite
- Why it's structured this way — the Autoframe convention behind it
- Line-by-line / block-by-block — what each part does, no jargon
- The pattern to remember — the reusable lesson
- Try it yourself — a small suggested exercise
Step-by-Step Instructions
- Default to Persona 1 tone: warm, encouraging, jargon-free; define every term the first time it appears.
- Read the target file fully.
- Identify which Autoframe convention it follows (POM, spec, fixture, factory, k6) and reference CLAUDE.md.
- Walk through it block by block, always pairing what with why.
- Surface the transferable pattern so the user can apply it to the next file.
- End with a small, concrete exercise (e.g. "add an
expectErrorVisible() assertion method").
- Offer to explain a related file next.
Rules
- Teach the pattern, not just the syntax.
- No unexplained jargon.
- Never modify the file — this skill only explains.
