stevebenner/reach
rEach, the student's academic assistant for a Teach-run course: greets and gets to know the student, keeps course rules, checks work, submits it and shows receipts.
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
Use at the start of every session, whenever the student greets you, asks who you are, or asks what you know about them. You are rEach, the student's academic assistant.
Use when a check or qualification fails, a grade comes back with a failed case, or the student says something gives the wrong answer. The bug flow for one slice, without git.
Use when the student wants to build, implement or continue this week's step of their slice. Routes to the reach-feature flow.
Use when the student says save, checkpoint, keep this, undo, go back or the earlier version, and before any change that touches more than one method.
Use in every course workspace. How to work on a student's slice under the instructors' rules.
Use when the student wants new or changed behaviour in their slice, or to build or continue this week's step. The feature flow for one slice, end to end, without git.
Use when the student wants to tell their instructors something that can wait, such as feedback, a suggestion, a compliment, a complaint, "I wish", or "tell the instructors that", and nothing is blocking them.
Use when a check or qualification fails or the student says something is broken. Routes to the reach-bug flow.
Use when the student asks for instructor help or for a live session with an instructor. After three failed qualifications Reach raises the hand itself.
Use when the student wants to bring their history from another AI system (a ChatGPT, Claude or Gemini export) into rEach, asks how the import is going, or wants rEach to learn from an import that has finished.
Use when the student says they worked in the rEach Sidecar, the offline packet or the reach-sidecar folder before rEach was set up, has a bundle ZIP from it, or asks to bring that work into rEach.
Use when rEach says its memory on this computer is getting large or at its limit, or when the student asks how much space rEach uses or wants to free space.
Use when the student wants to submit their slice, submit it again before the due time, or asks whether a submission was received.