Claude for writing student feedback, done properly.
The tested prompt, the codes that help, and the setup education pros run. Copy, adapt, ship.
Progress reports, parent emails, and IEP documentation require individualized, professional language. Writing the same quality of feedback for every student is exhausting.
Three reasons this actually lands.
The prompt, the codes, the fit. Each one on its own is a nice-to-have. Together, they change the workflow.
One tested prompt, copy-paste ready. Rules baked in, placeholders marked, tone locked down. No prompt-engineering trial runs, no back-and-forth.
Prefix with TONE:, PERSONA, L99 for compound effects. Each code is a documented technique, not a magic word.
Tuned for education workflows. Not a generic template, and not another "you are a helpful assistant" hack.
Without the pattern vs with it.
What the day looks like when you keep winging the prompt, and what it looks like when you stop.
Generic prompt. Claude writes something that could be about anyone, in any industry, from anywhere. Sounds like a template because it is one.
The CLSkills prompt with placeholders for your context. Claude writes it like a specialist who actually knows the work. Publishable after one edit pass.
You paste, Claude answers, you rewrite, you paste again. Ten minutes of back-and-forth per output. Three hours across a batch of five.
Prompt loaded once. You feed the specifics, Claude returns the finished output. Two minutes per, twenty across five. Same tone, same structure, every time.
Middle-of-the-road copy that reads AI-flavoured. Recipients notice. Response rates stay low. You end up rewriting most of it anyway.
Professional, individualized feedback that's specific and growth-oriented. Parents understand exactly where their child stands and what to do at home. Saves 2-3 minutes per student.
Copy this, replace the placeholders, ship.
Write feedback for [STUDENT'S FIRST NAME] in [SUBJECT].
Context: [PROGRESS REPORT / PARENT EMAIL / IEP UPDATE / REPORT CARD COMMENT]
Grade level: [GRADE]
Performance level: [BELOW / AT / ABOVE GRADE LEVEL]
Strengths: [LIST 2-3 SPECIFIC OBSERVATIONS]
Challenges: [LIST 1-2 AREAS OF CONCERN]
Effort/behavior: [DESCRIPTION]
Goals for next period: [WHAT TO WORK ON]
Rules:
- Use growth mindset language ("developing" not "failing")
- Be specific: "Sarah can multiply single-digit numbers accurately" not "Sarah is good at math"
- Mention specific work or moments you observed
- Include one suggestion for home support (if parent communication)
- Professional tone, warm but realistic
- Avoid superlatives unless truly earned
- Length: 100-150 words for report cards, 200-300 for parent emailsReplace the [BRACKETED] placeholders with your context.
Stack these prefixes for compound gains.
Prepend one or more of these to the prompt above. Each code is documented on its own page with before and after examples.
Every prompt, once.
The Cheat Sheet is every tested code, with a before and an after.
Nearby prompts for the same role.
Creating engaging lesson plans that meet standards, differentiate for multiple levels, and actually hold students' attention takes teachers …
CLAUDE FORGrading 30+ essays with meaningful feedback takes 15-20 hours. Most teachers resort to generic comments because individual feedback at scale…
CLAUDE FORGood assessments test understanding, not memorization. Most auto-generated quizzes are shallow — they test recall when you want to assess ap…
CLAUDE FOROne classroom, 30 students at 10 different levels. Teachers know they should differentiate but creating multiple versions of every activity …