Write, revise, split, or audit customer-facing ClassroomIO Help Center guides under apps/help/content/help. Use for task guides, troubleshooting answers, concept/reference pages, student guides, and their media or internal-link plans. Do not use for developer…
Design and review ClassroomIO public APIs for security, authorization, API contract quality, MCP/API-key behavior, and dashboard feature parity. Use when adding or reviewing API routes, public APIs, automation endpoints, or MCP tools.
End-to-end feature delivery — implement a feature, verify builds/tests pass, open a fully-filled draft PR, then automatically push every feedback round and review iteration to the same PR. Use when the user asks to implement or build a feature, fix-and-ship a…
Stage changed files and create a commit following the repo's translation, formatting, and git workflow rules. Use when the user asks to stage, commit, or both.
Mandatory code-writing rules for this repo, led by the comment policy: default to no comments, document functions with JSDoc only when the signature isn't enough, and never explain a design choice inline (refactor instead). Read this before writing or editing…
Capture, frame, and place screenshots for ClassroomIO Help Center articles under apps/help/content/help. Use for any request to take, capture, retake, or fix screenshots for a help guide, including a pasted shot list with filenames and sizes, and when a…
Write ClassroomIO's weekly customer changelog from the previous week's shipped work. Produce a concise customer email, a separate changelog-site article and a step-by-step demo walkthrough backed by seeded demo data, capture framed PNG screenshots, and draft…
Write every pull request and issue reference as a clickable link rather than a bare number. Use whenever a reply, PR description, issue body, comment or report mentions a PR or issue in classroomio/classroomio.