edtech-patternslisted

# EdTech Platform Patterns > Auto-fires on every file. Sister skills: `ferpa-coppa-compliance` > (regulation), `wcag-accessibility` (the learner is the user), > `interaction-design` (learning experience design), > `gdpr-ccpa-compliance` (when learners are EU/CA minors), > `prompt-engineering` + `rag-design` (when AI tutors are involved). ## Purpose Engineers building learning platforms (LMSs, MOOCs, K-12 tools, corporate training, adaptive tutors, assessment engines, credentialing systems) routinely re-invent interoperability, ship inaccessible-to-learners content, mis-model assessment, or import learning-analytics dashboards that quietly profile minors without parental knowledge. The cost of getting it wrong is high: a single integration break (Canvas → publisher → SIS) can take an entire district offline at exam time; an inaccessible assessment locks blind students out of their education; a biased proctoring system targets disabled or non-white learners disproportionately and lands the vendor in DOJ + OCR complaints. This skill exists to make the standards-cited, accessibility- first, ethics-aware path the default — and to name the anti-patterns that turn well-intentioned edtech into discriminatory infrastructure. **Not legal advice; not pedagogical advice for any specific learner.** Pair with district / institution / accreditor counsel on Section 504, IDEA, OCR + DOJ Title II/III obligations, and with learning scientists on assessment validity. ## Standards Cited **