← Back to library

Set up a teacher workspace that remembers the class

u/icygnum set up a workspace in Claude Code for an overworked teacher friend that stores the syllabus, marking approach and class size permanently, so each session starts informed. Drafts follow the teacher's own writing examples instead of generic school prose, cutting repeated setup.

  • OutcomeGive an AI workspace the course outline, how you mark and the class profile once, so every rubric, parent email, comment and lesson plan comes out consistent.
  • SetupUnder an hour
  • LevelStarter
  • Creditu/icygnum on r/ClaudeCode
View original
Works with
Claude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You are a teacher writing the same documents every term
  • You want consistent tone in comments
  • You keep re-explaining your class to a chatbot

Not for: Storing student names and grades in a shared or cloud folder you do not control; Final grades without your review

What do you need, and what do you get?

You need

  • Curriculum outline
  • Grading style notes
  • Class profile without names
  • School policies

You get

  • Lesson plans
  • Report comment drafts
  • Parent email drafts
  • Rubrics

How does it work, step by step?

  1. Write the profileRecord curriculum, year group, class size and grading style in one file.
  2. Keep names outUse initials or numbers instead of student names.
  3. Add templatesSave examples of good comments and emails you have written.
  4. Ask by taskRequest a lesson plan, comments or a rubric; it uses the saved profile.
  5. Review everythingEdit drafts before they reach students or parents.

The prompt

Our own prompt, inspired by u/icygnum on r/ClaudeCode and written to work in Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
Class profile: {profile}. Grading style: {style}. Example comments I have written: {examples}.
Task: {task}.
Use my tone and the curriculum in the profile. Use student initials only. Mark anything you are unsure about for me to check.

Inspired by u/icygnum on r/ClaudeCode: Built This for Teachers. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Comments can sound generic; feed it your own past examples.
  • School data rules may forbid sharing student information with AI tools.

Our take

Persistent context is the whole idea, and it is a big one for teachers who repeat the same background in every chat. A single profile file plus examples of their own writing makes drafts sound like them. Keep student names and grades out of the cloud when policy forbids it. Write the profile once: curriculum, year group, class size and grading style. Add examples of comments and emails the teacher has actually written, because without them drafts sound generic. Use initials or numbers instead of student names, and check school data rules before putting any student information into an AI tool. Ask by task, such as a lesson plan, report comments or a rubric, and edit every draft before it reaches students or parents. Final grades always stay with the teacher. Update the profile at the start of each term, since a new class or syllabus changes what good drafts look like, and keep the folder somewhere the school is comfortable with.

Where the time goes back: Every new task starts from what the AI already knows about the class instead of a blank prompt.

FAQ

Do I need to code?
No; the poster built it so teachers can use it without programming.
Can it grade?
It can draft feedback against your rubric; final grades stay yours.

Source and credit

Inspired by u/icygnum on r/ClaudeCode. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Built This for Teachers
Creator
u/icygnum on r/ClaudeCode
Published on
Reddit
Original date
Mar 28, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Check saved agent skills hold up on a messier second run

Have your lead agent list every private skill it can reach, check each one for a clear purpose, required inputs, decision rules, a way to verify results, a defined output, approval points, failure handling and protection against duplicate actions, then draft improved instructions and a tougher test for your approval.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminSkill✓ AI dry run

Document a process as an SOP, flowchart and RACI

A process that lived in someone's head, written down as an SOP with a flowchart, a RACI table and the exceptions.

Credit: Anthropic

Under an hour
Operations & AdminWorkflow✓ AI dry run

Fill PDF forms from your own documents with an agent

Upload a fillable PDF and the documents that hold the answers; the agent stages a value for each field, shows you the pending edits and saves the filled form.

Credit: Jerry Liu (@jerryjliu0)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Keep a shared team wiki that your agents maintain

Give agents a markdown-and-git wiki they read and write, with drafts reviewed before they become team knowledge.

Credit: najmuzzaman on Hacker News

An afternoon+