An AI teaching assistant for your class. What we think we are building, what we would need from you, and where we are probably wrong.
Taylor Script if we are being formal. TS for short, which is also a programming language.
Scripty
Stan James · Vibeconferencing
The goal, as we understand it
A patient TA who is always there
A bot that joins a Google Meet, listens, talks, and works through code alongside your students.
Meet me at midnight, or whenever they are stuck
A standing weekly slot. Students drop in. Scripty is there whether or not you are.
She knows your class, not just programming in general
Your syllabus, your projects, your sequence, so she meets students where the course actually is.
She helps without simply handing over the answer
No spoilers at 2am. Where exactly that line sits is your call, and it is the most important thing you will tell us.
You get the readout without sitting through it
A written summary after every session, and the transcript if you want it. You never have to attend.
How it fits together
One link, no Ticketmaster queue
Our wildest dreams, a first pass
Six things we think we would need from you
1
A Gmail account for Scripty
Her own free account, not yours. Her calendar becomes the tour schedule.
2
A Claude subscription
She needs her own. We can cover it for a pilot, or you can own it.
3
What you have taught Taylor Script (from the vault)
You have done most of this already. We help lift it into the one file Scripty reads, and send a template for the gaps.
4
Your course materials (the back catalogue)
Syllabus, assignments, starter code. This becomes what she knows.
5
A practice session or two (soundcheck)
Someone plays a student and works a real assignment with Scripty, so we can see which tools she needs. We can run these, but your eye on her answers is worth a lot.
6
A recording decision (literally)
What gets kept, who can read it, and what students are told.
Items 1 and 2 take about ten minutes together. Item 3 mostly exists already, inside Taylor Script.
Where we are least confident
Tell us what we have backwards
Assumptions we made from the outside
Scheduled office hours, one shared room, rather than on demand or one to one
Mostly helping students work through code and projects
Office hours happen without you, rather than Scripty sitting beside you in a live class
A fixed weekly rhythm across a term with a start and an end
Blank space: what belongs here?
How do you actually teach this class, start to finish?
Where do students get stuck, over and over?
How much help is too much, in your words?
What has Taylor Script already learned that we must not lose?
What would you want from Scripty that is nowhere on our list?
We would rather get the shape right now than build fast and have to shake it off later.
