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.
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…
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.
Edit ClassroomIO videos (talking heads, team discussions, product demos, screen recordings, tutorials, webinars) into branded, professional cuts for YouTube, Shorts, Reels, LinkedIn and X using the ClassroomIO design system. Covers pause trimming, noise…
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…
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…
ClassroomIO's design system. Use for any ClassroomIO UI, marketing page, launch image, social post, deck or thumbnail, and before choosing a colour, type size, radius or component. Covers tokens, app and marketing components, voice, and brand-asset rules.
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…