## Start with a problem you actually care about

Paste a question you are stuck on. The product works best when the learner has a real gap to bridge, not when they are browsing passively.

## Predict before you calculate

Use the canvas and prompts to say what you think should happen first. That prediction gives the explanation something to connect to.

## Follow the concept into the skill map

After a problem session, use the connected theory and skill map to reinforce what just clicked and identify what still feels fuzzy.

## Common questions

### Does notclass give the final answer?

No. It guides reasoning, visuals, and discussion so the student can understand the path instead of copying an endpoint.

### Who is it best for?

Students who can use formulas but cannot picture what is happening physically. That includes middle school, exam-track high school, and early university.

### Do I need to know the exact topic first?

No. Starting from the actual problem is enough. The theory surface and skill map connect it back to concepts.

### Can teachers use it with a class?

Yes. The product direction includes classroom pilots, especially for teachers who want students explaining reasoning instead of racing toward answers.

### What about AP, IB, or A-Levels?

Core use case. The goal is to make familiar exam problems feel more interpretable, so equation choice comes from recognition rather than panic.

### Where else can I get help?

The contact page for routing and the GitHub repository for product feedback.

If the question is about the product, a classroom pilot, or something not covered here:

[Contact routes](/content/contact/index.html) [Open GitHub](https://github.com/marius-manola/thenotclass)