How to learn with Kenji Sato

Kenji treats old hardware as a doorway into design decisions rather than a shelf of trivia. He is patient with technical vocabulary, enthusiastic about elegant constraints, and playful when learners test how an arcade or home-computer system actually worked.

Before lesson one

Plan a focused first session

Specific evidence gives Kenji a better starting point than a broad request to teach the whole subject. Use this four-part setup.

1. Arrive with evidence

   Bring a code sample, error, command, diagram, dataset, requirement, or system behavior. A real sample gives Kenji something concrete to diagnose.

2. Define one result

   Aim for one working technical artifact plus a clear explanation of why it behaves that way. Put that result in the Plan tab before expanding the lesson.

3. Attempt before the model

   Show what you currently think or can do. Ask for a hint or question before requesting the completed answer.

4. Leave with retrieval

   Explain the lesson back, save the hardest point as a review card, and schedule the smallest useful follow-up.

Choose the right lesson mode

Repeatable value

Use Kenji's lesson rhythm

A good session should produce something you can attempt, inspect, and revisit. This profile is designed around the following rhythm.

Start

Name a machine, game mechanic, chip, display, controller, or technical mystery. Kenji will establish what the system could do, what it could not do, and why the design still worked.

Work

Map the hardware, identify a constraint, inspect the player feedback loop, compare another system, and turn the finding into a diagram or tiny original design exercise.

Continue

Block diagrams, pixel studies, mechanic notebooks, timeline cards, interface comparisons, and preservation inventories.

Collaborative classroom

Use each classroom tool with a purpose

The whiteboard opens as the main lesson surface. Workspaces are shared deliberately: use Show tutor or Update tutor after changing the board, Notebook, Document, Code Lab, or SVG Studio so Kenji sees the current version.

Ready to use

Prompts that fit this tutor

These prompts use Kenji Sato's actual subjects, lesson format, and adaptive classroom lab. Replace the topic with your own material when needed.

1. Name a machine, game mechanic, chip, display, controller, or technical mystery. Kenji will establish what the system could do, what it could not do, and why the design still worked.

2. I want to improve 1980s Computing and Home Technology. Use Hardware maps, system comparisons, arcade-design breakdowns, pixel constraints, game-loop analysis, computing timelines, troubleshooting thought experiments, and preservation plans. Check what I can already do, let me attempt something, and give one correction at a time.

3. Open Code Lab for 1980s Arcade and Video Games. Keep the task small, make me explain my choices, and finish with three review cards and one next-session goal.

Progress evidence

Know whether the lessons are working

Do not measure progress only by how clear the explanation felt. Look for changes in what you can retrieve, decide, produce, or explain without support.

• Predicts behavior before running the example
• Finds the failing boundary with fewer hints
• Explains tradeoffs instead of naming tools only
• Builds a nearby variation without copying the model

Responsible use

Use Kenji as a tutor, not an authority

Supports history, design analysis, emulation concepts, and preservation literacy; it does not distribute copyrighted ROMs, bypass copy protection, provide pirated software, or guide unsafe repair of mains-powered vintage hardware.

Kenji Sato is a fictional AI tutor profile for 1980s computing, arcade, video-game design, and technology-history education.