Build and connect
Students work with the board, sensors, speaker, LED feedback, wiring, and enclosure so the hardware is visible and understandable.
Concept / early development
AI Buddy Starter Kit
A voice and motion AI learning kit designed so students can talk to a device, move it, program it, and see or hear it respond.
The goal is to create a classroom-friendly system that feels exciting to students while keeping the technology open enough to build, inspect, change, test, and understand. The first version is being shaped for local schools, STEM programs, robotics clubs, and guided home learning.
Core idea
Students learn AI by building something real.
The kit is intended to move students beyond simply using a finished AI tool. They identify the components, connect the system, observe what it recognizes, change the behavior, and discuss why the result still requires human judgment.
Program and test
Students change a command, gesture, response, or line of logic and immediately see how the system behaves differently.
Understand limitations
Lessons explain what the device recognized, what it missed, how mistakes happen, and why AI output should be tested rather than blindly trusted.
First learner path
Middle school is the strongest starting point.
The current planning direction centers on students around ages 10–14, with simpler guided activities for younger learners and deeper programming paths for older students.
Guided introduction
Preloaded responses, simple LED and sound reactions, component identification, and closely guided cause-and-effect activities.
Primary first target
Gesture recognition, voice commands, simple logic, enclosure assembly, behavior changes, and discussion of AI strengths and limits.
Advanced pathway
Python, data logging, model concepts, local and cloud AI comparisons, expanded sensors, ethics, privacy, and safety.
Final fit comes from schools
Grade level, lesson length, class size, curriculum alignment, accessibility, and classroom rules should be shaped with teachers before release.
Starter lesson sequence
A clear path from parts to understanding.
Identify the system: open or build the 3D-printed enclosure and locate the main board, voice sensor, motion sensor, speaker, and LED feedback.
Power it on: connect power and learn what the startup LED pattern communicates.
Talk to it: say a wake word or simple command and observe how the kit recognizes an approved phrase.
Move it: tilt or gesture with the device and watch the motion response trigger a sound, light, or programmed action.
Change it: modify a line of code or configuration and test how the response changes.
Discuss the result: identify what the system understood, what it did not understand, and why people remain responsible for interpreting and using the result.
Current prototype direction
Voice, motion, feedback, and an enclosure students can understand.
The hardware is still a working direction and may change after school feedback and prototype testing. The current candidate combines an Arduino UNO Q, Arduino Nicla Voice, a small built-in speaker, LED feedback, and a Vai-Nova-designed 3D-printed enclosure.
Nicla Voice
Acts as the voice and motion front end for wake words, limited commands, sound classification, and gesture sensing at the edge.
Arduino UNO Q
Provides the main lesson logic and coordination between the Linux/Python side, Arduino control, sensors, and outputs.
Speaker and LED feedback
Give students immediate, visible and audible confirmation without requiring a separate screen or shared earbuds.
3D-printed enclosure
Protects the system, supports Vai-Nova branding, and gives students a physical design they can inspect, assemble, and eventually modify.
Motion-only option
A separate movement module remains useful for a lower-complexity motion kit or a modular lesson where students physically add sensors.
Classroom audio choice
A built-in speaker is the preferred default. Wired quiet mode or Bluetooth can remain optional extensions where the school permits them.
Planned kit lanes
One learning idea, different levels of depth.
These are development directions rather than final products or published pricing.
Basic AI Motion Kit
Motion or gesture recognition, LED feedback, simple lessons, and a printed enclosure for introductory cause-and-effect learning.
AI Buddy Voice Kit
The primary prototype direction with voice commands, movement sensing, audio response, visible feedback, and student-modifiable logic.
Classroom Pack
Multiple kits supported by a teacher guide, worksheets, spare parts, repeatable activities, and classroom-use planning.
AI Lab Kit
A future high-school or robotics-club path using more capable local AI, cameras or expanded sensors, data logging, and advanced projects.
Responsible classroom design
Useful learning without unnecessary data exposure.
The design direction favors low-voltage classroom hardware, understandable local behavior, teacher control, repairable components, and no requirement to submit student personal information to a public AI service.
Privacy-aware by default
Voice and sensor activities should use limited approved commands and classroom data practices that are easy for teachers and families to understand.
Repairable and reusable
Replaceable parts, printed enclosures, and reusable electronics help preserve school value while teaching troubleshooting instead of disposal.
Clear safety boundaries
Microphones, Bluetooth, batteries, cloud connectivity, student accounts, and stored data should be reviewed against each school’s policies before deployment.
What we need from schools
The first pilot should be designed with educators, not handed to them afterward.
Learner group: which grade, class, club, or program would use the kit first?
Purchase model: would the school prefer shared classroom kits, individual student kits, a PTA-supported program, a grant, or a robotics-club package?
Teaching materials: what teacher guide, worksheets, lesson length, replacement parts, and support would make the kit realistic to use?
Classroom rules: what restrictions apply to microphones, speakers, Bluetooth, batteries, networks, cameras, or cloud-connected services?
Learning outcome: should the first pilot emphasize electronics, coding, AI concepts, teamwork, problem-solving, or responsible technology use?
Development path
Start with one working kit and one understandable lesson.
Confirm the first school’s learner group, classroom needs, technology policies, and preferred program structure.
Build and test one prototype using the current voice-and-motion hardware direction.
Create a small “Hello AI” lesson covering wake word, command, movement, LED response, and speaker feedback.
Design the first classroom enclosure with safe access to ports, clear part identification, and Vai-Nova branding.
Document the bill of materials, assembly steps, teacher instructions, student activities, and replacement-part plan after the prototype is proven.
Help shape a practical AI Buddy school pilot.
Schools, teachers, STEM programs, robotics clubs, PTAs, and community organizations can share the learner age, class size, learning goals, available time, technology policies, and preferred classroom model.