# Topic

Explain **[keyword]** to me.

# Pick your output format

Each format below is easier to take in than the one before it. Keep the one you want and delete the rest.

## Option 1 — Writing (ASD-STE100)

Explain [keyword] in ASD-STE100 Simplified Technical English, the controlled language specification originally developed for aerospace maintenance documentation. Apply its constraints: short sentences, one idea per sentence, active voice, one meaning per word, and approved vocabulary where practical.

The full spec is quite stringent, so aim for about 80% of the way to ASD-STE100 — loosen a rule only where following it strictly would hurt clarity.

## Option 2 — Diagram / image

Instead of writing, explain [keyword] with a diagram. Choose the diagram type that best fits the topic (flowchart, sequence, layered architecture, timeline, annotated illustration) and keep the labels short. Add a brief caption that tells me how to read it.

## Option 3 — Web page

Explain [keyword] "in HTML". Output a single, self-contained HTML file (inline CSS and JS, no build step) that I can open in a browser. Make it a beautiful, interactive experience — use animations, step-through controls, sliders, or hover states wherever they help me understand the idea, not just for decoration.

## Option 4 — Explainer video

Create a 3Blue1Brown-style video explainer on [keyword].

- Write the narration script and a scene-by-scene breakdown first

- Build the animations in code (e.g. Manim) and give me the exact commands to render them

- Use my ElevenLabs API key for audio narration: [your ElevenLabs API key]

- If I do not have an API key, find me decent free text-to-speech alternatives that run on my local compute and use one of those instead

- Sync the narration to the scenes and output a final rendered video file