hi is an AI explanation tool β presented in the product concept as βExplain Itβ AI β built for a deliberately broad audience: kids and adults, not a single age group and not another boring chatbot.
The product intent is simple and singular: a person arrives with something they don't understand, and the product explains it at whatever level they want. The user pastes or types anything confusing β homework, an email, a confusing bill, instructions, a news article, or a plain question like βWhat is a mortgage?β β or uploads a picture of something confusing, and the product breaks it down without making them feel stupid.
The audience spans a child meeting a concept for the first time, a student working at school level, an adult who wants a normal detailed explanation, and an expert who wants depth. The same person may move between those levels depending on the material in front of them. The product therefore treats explanation depth as a user choice, not a fixed product personality.
Beyond the core explanation, the accepted product includes a set of extra capabilities the user explicitly requested: Explain this picture, Summarize this, Turn it into steps, Quiz me on it, Translate + explain, Ask follow-up questions, and Make it shorter/longer.
hi is a web product with a custom first-party interface. Its current delivery shape is a set of simple, directly reachable surfaces that carry a user from confusing content to an explanation they can actually follow, and then let them keep working with that material.
Actors. The accepted active-human catalog is closed and consists of four personas: Confused Learner, Visual Explainer Seeker, Study & Practice User, and Cross-Language Reader. The AI explanation engine is a non-persona system actor that performs the explanation, summarization, step generation, quizzing, translation, and follow-up work the user requests.
Accepted behavior. Users can:
Ownership. All of the above human-facing work is owned by first-party custom pages. The AI explanation engine is a supporting system actor behind those pages; it is not a destination and does not replace the user's own interaction.
Exclusions and boundaries. This document does not add adjacent capabilities the user did not request β no accounts, no saved libraries, no social or sharing features, no classroom management, no billing, and no chatbot framing. The product is an explanation tool, not a conversational assistant product.
Delivery. The product is delivered as a first-party web experience with a custom interface. The entry experience is intentionally ridiculously simple, exactly as the user described it:
What are you confused about?
[ Paste anything here... ]Explain it like:
Kid\x20\xf0\x9f\xa7\x92 | Student\x20\xf0\x9f\x8e\x93 | Adult\x20\xf0\x9f\x91\xa8 | Expert\x20\xf0\x9f\xa7\xa0[ MAKE IT MAKE SENSE ]
Access. The accepted page contract assigns no access requirement to any page. Every surface β Landing, Input, Picture Explain, Explain Level, Explanation, Picture Explanation, Summary, Steps, Quiz, Translate, Follow-Up, and Adjust Length β is reachable without an account. There is no application-owned identity, no sign-in, and no protected destination in the current product. A user can arrive, paste or upload, choose a level, and get an explanation immediately.
Current vs. future. Everything described in this document is current. No future-horizon requirements were accepted in the authoritative thread; the future section is therefore empty by design rather than by omission.
Provider and system boundary. The AI explanation engine is a system actor that performs the requested transformation on the user's content. It is not a persona, not a page, and not a destination. Its work is always initiated by an accepted human actor through a first-party page, and its output is always presented back to that actor on a first-party page.
No reference directive in this project declares content_source. This section is intentionally omitted.
The page inventory below is the accepted final page contract, preserved exactly and in order. Each page appears exactly once.
Each requirement below is a distinct story point with its provenance and observable acceptance.
FR-1 β Explain anything at a chosen level. As a Confused Learner, I should be able to paste or type anything I don't understand and have it explained at the level I choose, so that I can actually follow it.
FR-2 β Paste or type any content. As a Confused Learner, I should be able to paste or type any content I don't understand β homework, an email, a confusing bill, instructions, a news article, or a plain question β so that I can submit exactly what is confusing me.
FR-3 β Choose an explanation level. As a Confused Learner, I should be able to choose Kid mode (super simple), Student mode (school-level), Adult mode (normal detailed), or Expert mode (deep), so that the explanation matches how much depth I want.
FR-4 β Make it make sense. As a Confused Learner, I should be able to press MAKE IT MAKE SENSE and have the pasted content broken down without being made to feel stupid, so that I get an explanation I can act on.
FR-5 β Explain this picture. As a Visual Explainer Seeker, I should be able to upload a picture of something confusing and use Explain this picture, so that something I can't easily type out still gets explained.
FR-6 β Summarize this. As a Study & Practice User, I should be able to summarize the content, so that I get the short version when I don't need the full breakdown.
FR-7 β Turn it into steps. As a Study & Practice User, I should be able to turn the content into steps, so that I get an ordered sequence I can follow.
FR-8 β Quiz me on it. As a Study & Practice User, I should be able to be quizzed on the content, so that I can test whether I actually understand it.
FR-9 β Translate + explain. As a Cross-Language Reader, I should be able to translate and explain the content, so that I get both the translation and an explanation of what it means.
FR-10 β Ask follow-up questions. As a Confused Learner, I should be able to ask follow-up questions about the explanation, so that I can keep going until it actually makes sense.
FR-11 β Make it shorter/longer. As a Confused Learner, I should be able to make the explanation shorter or longer, so that I can get exactly as much detail as I need.
FR-12 β Simple entry experience. As a Confused Learner, I should see a ridiculously simple entry experience β the question βWhat are you confused about?β, a paste-anything input, an βExplain it like:β selector with Kid, Student, Adult, and Expert, and a MAKE IT MAKE SENSE button β so that I know exactly what to do the moment I arrive.
FR-13 β Broad audience. As a product owner, I should have the product usable by both kids and adults, so that it serves a broad audience rather than a kids-only or adults-only tool.
FR-14 β Never make the user feel stupid. As a Confused Learner, I should be explained to without being made to feel stupid, so that asking for help never costs me dignity.
The active-human catalog is closed and consists of exactly the four personas below.
Product context. This person arrives with something specific in front of them that they don't understand β homework, an email, a confusing bill, instructions, a news article, or a plain question like βWhat is a mortgage?β. They are not looking for a conversation partner; they are looking for the thing in front of them to stop being confusing.
Primary goal. Get the material broken down at a level they can actually follow, without being made to feel stupid for not already knowing it.
Distinct accepted responsibilities. This persona owns the core loop: paste or type the content, choose one of Kid, Student, Adult, or Expert, press MAKE IT MAKE SENSE, read the explanation, and then keep working with it β asking follow-up questions and making it shorter or longer until it lands. They are the persona who most directly exercises the level selector and the length controls, because the right depth for them is a moving target as their understanding grows.
Relevant inputs or decisions. The content itself; the choice of explanation level; whether the current explanation is too long, too short, or still unclear; what to ask next.
Interactions with other accepted participants. None required. This persona's work is self-contained; the AI explanation engine is a system actor that serves them, not a participant they coordinate with.
Observable success. They can restate the material in their own words, and they never had to admit they didn't understand it in order to get there.
Product context. This person is confused by something they cannot easily type out β a photo, a screenshot, or an image of a document, sign, or diagram. Typing it would lose the thing that's confusing them.
Primary goal. Get the picture itself explained, at their chosen level, so that what they are looking at becomes legible.
Distinct accepted responsibilities. This persona owns the image path: upload or select the picture, trigger Explain this picture, read the picture explanation, and then follow up with questions about what they see. Their work is distinguished by the fact that the source material is visual and the explanation must be grounded in the image rather than in text they supplied.
Relevant inputs or decisions. Which image to upload; whether the image is readable; the explanation level; what specifically about the image is unclear.
Interactions with other accepted participants. None required. The AI explanation engine is a system actor serving them.
Observable success. They can describe what the picture shows and what it means, having started from not being able to read it at all.
Product context. This person is working through study material and wants more than a one-off explanation. They need to be able to work with the material on their own afterward.
Primary goal. Convert confusing material into something they can study, follow, and test themselves on.
Distinct accepted responsibilities. This persona owns the study toolset: summarizing the content, turning it into steps, and using Quiz me on it to test their understanding, then iterating with follow-up questions and shorter or longer versions until they can work with the material independently. Their work is distinguished by the fact that they are not just seeking comprehension β they are seeking retention and self-testing.
Relevant inputs or decisions. What to summarize versus what to break into steps; whether to quiz now or after another pass; which questions they got wrong and what to ask about them.
Interactions with other accepted participants. None required. The AI explanation engine is a system actor serving them.
Observable success. They can answer quiz questions about the material correctly and follow the step breakdown without needing the original explanation open.
Product context. This person is facing content in a language or phrasing they don't fully follow β a bill, an article, or instructions β and needs both the words and the meaning.
Primary goal. Get a translation and an explanation together, so that they understand what the content actually means and not just what it literally says.
Distinct accepted responsibilities. This persona owns the translation path: request Translate + explain, read the translation and the explanation at their chosen level, and then ask follow-up questions to confirm they understood the meaning correctly. Their work is distinguished by the fact that comprehension requires crossing a language boundary first, so a translation alone would not be sufficient and an explanation alone would not be readable.
Relevant inputs or decisions. The content to translate; the explanation level; whether the translation reads correctly to them; what meaning they need confirmed.
Interactions with other accepted participants. None required. The AI explanation engine is a system actor serving them.
Observable success. They can act on the content β pay the bill, follow the instructions, understand the article β with confidence that they read it correctly.
No CREATIVE DIRECTION block was supplied, and the user gave no explicit colour, brand, or font instructions. The user did specify the tone and layout intent β ridiculously simple, kids AND adults, not another boring chatbot β and the entry experience as a headline question, a paste field, a four-option level row, and one big button. The tokens below are coherent defaults chosen to serve that intent, and are labeled as defaults.
[Default β not specified by user]
Palette (light mode).
| Role | Hex | Use |
|---|---|---|
| Background | #FFFDF7 | Page canvas β warm off-white, not clinical |
| Surface | #FFFFFF | Cards, explanation panels, input field |
| Surface alt | #F4F1E8 | Level selector track, secondary panels |
| Ink | #1B1B1F | Primary text |
| Ink muted | #5C5A63 | Level descriptions, helper text |
| Border | #E3DFD3 | Field and card borders |
| Primary | #FF5A3C | MAKE IT MAKE SENSE button, primary actions |
| Primary ink | #FFFFFF | Text on primary |
| Kid accent | #FFB020 | Kid\x20\xf0\x9f\xa7\x92 level chip |
| Student accent | #2BB673 | Student\x20\xf0\x9f\x8e\x93 level chip |
| Adult accent | #3B82F6 | Adult\x20\xf0\x9f\x91\xa8 level chip |
| Expert accent | #7C4DFF | Expert\x20\xf0\x9f\xa7\xa0 level chip |
| Success | #2BB673 | Correct quiz answers, completed states |
| Error | #D93A2B | Plain, non-judgmental error text |
| Focus ring | #1B1B1F at 2px offset | Keyboard focus |
Palette (dark mode).
| Role | Hex |
|---|---|
| Background | #14131A |
| Surface | #1E1D26 |
| Surface alt | #272633 |
| Ink | #F5F3EE |
| Ink muted | #A8A4B3 |
| Border | #33313F |
| Primary | #FF6B4F |
| Primary ink | #14131A |
Typography.
system-ui, -apple-system, "Segoe UI", sans-serif.system-ui, -apple-system, "Segoe UI", sans-serif.12 / 14 / 16 / 20 / 26 / 34 / 44 px, with the Landing headline at 44px (mobile 32px) and explanation body at 18px for comfortable reading.1.6 for explanation body, 1.2 for headings.Shape and radius. Rounded and soft: 8px for chips and inputs, 14px for cards and panels, 999px for the primary button and level chips. Nothing sharp; nothing that reads as enterprise software.
Spacing rhythm. 4 / 8 / 12 / 16 / 24 / 32 / 48 / 64 px. The Landing entry block is centered with generous vertical space so the four elements β question, input, level row, button β read as one obvious action.
Imagery style. Minimal and functional. The only imagery in the product is the user's own uploaded picture, shown as a preview on Picture Explain and alongside the explanation on Picture Explanation. No stock photography, no decorative illustration, no mascot.
The One-Screen Answer.
The public entry is a single centered column on a warm off-white canvas, and it contains exactly four things stacked in the order the user described them:
#FF5A3C, the only saturated element on the page.The signature move is the level row as the product's identity. Where a chatbot would put a personality, this product puts four explicit depths side by side and lets the user point at one. The chips are the same four colours everywhere they appear β on Explain Level, as the level indicator on Explanation and Picture Explanation, and on the outputs of Summary, Steps, Quiz, Translate, and Adjust Length β so that a user can always see, at a glance, which depth they are currently reading at.
The second move is the picture door: a small, quiet Explain this picture\x20\xf0\x9f\x93\xb8 affordance sits beside the paste field, so a user whose confusing thing is an image finds their path without the entry screen becoming a menu.
Nothing else is on the entry. No navigation bar full of features, no feature grid, no marketing sections. The page is the product's first sentence, and it is the same sentence for a nine-year-old and for an adult reading a mortgage document.
No CREATIVE DIRECTION block was supplied. The tempo below is chosen for the product's audience and stated with its reason.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Why this tempo. The product's promise is that it is ridiculously simple and that it will not make the user feel stupid. Motion that calls attention to itself would undercut both: a child and an adult reading a confusing bill both want the interface to get out of the way. Motion is therefore used only to confirm that something happened β a chip selecting, a panel arriving, an answer appearing β never to perform.
Landing Hero Motion Brief.
prefers-reduced-motion: reduce, all transitions collapse to instant state changes. Chip selection, meaning-line swap, and explanation arrival render immediately with no fade or rise. No information is conveyed by motion alone at any point.No 3D or WebGL scene is requested by the user and none is derived from a direction, so no Canvas/R3F/Drei dependency is required.
NFR-1 β Tone is a functional requirement, not a style preference. Every explanation, summary, step breakdown, quiz question, translation, follow-up answer, adjusted-length output, empty state, and error message must be written so that the user is not made to feel stupid. Provenance: explicit. Rationale: the user stated this as the defining quality of the Make it make sense action.
NFR-2 β Broad-audience legibility. The interface and all product copy must be usable by both kids and adults. Concretely: body text at 18px for explanations, 1.6 line height, no jargon in interface labels, and no age-gating or age-specific entry path. Provenance: explicit. Rationale: the user stated the product must be for kids AND adults, not one or the other.
NFR-3 β No account required. Every page in the accepted contract carries no access requirement. A user must be able to arrive, paste or upload, choose a level, and receive an explanation without creating an identity or signing in. Provenance: explicit via the accepted page contract. Rationale: the accepted access contract assigns none to all twelve pages.
NFR-4 β Plain, non-judgmental failure. When an explanation, summary, steps, quiz, translation, follow-up answer, or adjusted-length output cannot be produced, the user is told plainly what happened and offered a retry that preserves their content, image, and selected level. Provenance: required_inference. Rationale: the explicit constraint that the user must never be made to feel stupid applies with the most force at the moment something goes wrong.
NFR-5 β Content preservation on failure. Submitted text, uploaded images, and the selected explanation level must survive a failed request so the user can retry without retyping or re-uploading. Provenance: required_inference. Rationale: retyping a confusing bill or re-uploading a photo is exactly the kind of friction that would make a user feel stupid for having tried.
NFR-6 β Level visibility. The currently selected explanation level must be visible wherever an explanation, picture explanation, summary, steps, quiz, translation, or adjusted-length output is displayed. Provenance: required_inference. Rationale: the user's core mental model is explain it at the level I chose; if the level is invisible, the user cannot tell whether the product honored their choice.
NFR-7 β Responsive layout. The entry experience β headline, paste field, four-level row, and MAKE IT MAKE SENSE button β must remain a single readable column on a phone, with the level row wrapping rather than truncating. Provenance: required_inference. Rationale: a broad kid-and-adult audience arrives on phones as often as on laptops, and the entry experience is the product's entire first impression.
NFR-8 β Accessible interaction. All controls must be keyboard reachable with a visible focus ring, the four level chips must expose their selected state to assistive technology, and no information may be conveyed by colour or motion alone. Provenance: required_inference. Rationale: a product whose stated purpose is to avoid making people feel stupid cannot make its own controls unreadable.
The user specified no technology choices. The stack below is the minimal coherent set for a custom-UI web product with an AI explanation engine behind it.
Constraints (binding).
Assumptions (narrow, labeled).
Explicit exclusions.
Future requirements. None. The authoritative thread accepted no future-horizon requirements.

Explain It
Paste or type anything you donβt understand and get it explained at the level you choose.
For kids and adultsNo question is too basic β you will never be made to feel stupid.
Explain it like:
Pick a level to see how deep the explanation goes.
Confused by a picture instead?Explain this picture

Explain It
Paste or type anything you donβt understand and get it explained at the level you choose.
For kids and adultsNo question is too basic β you will never be made to feel stupid.
Explain it like:
Pick a level to see how deep the explanation goes.
Confused by a picture instead?Explain this picture
No comments yet. Be the first!